Proactive Chat Invitations: When and What to Say

The principle: interrupt intent, not attention

A proactive invitation is a judgment that this visitor, on this page, right now, likely has a question worth asking. That judgment is credible on a pricing page after forty-five seconds. It is not credible on the homepage after five. Every invitation spends a little of the visitor's patience — spend it where the intent is.

Where invitations earn their keep

Pricing pages — the visitor is comparing; objections are forming. "Any questions about the plans?"
Checkout and cart pages — hesitation here is money. "Questions about shipping or returns before you order?"
High-value product or listing pages — long dwell time signals real consideration.
Documentation dead-ends — a visitor bouncing between help articles is a visitor not finding the answer.

Conspicuously absent: the homepage, the blog, and "every page." Site-wide invitations are how chat widgets earn reflexive close-clicks.

Timing: later than you think

Fire the invitation after the visitor has demonstrably engaged — commonly 30 to 60 seconds of dwell time, or a repeat visit to the same page. An invitation that appears before the page is read is a pop-up; the same invitation after a minute of visible consideration is service.

Say something specific

"Hi! How can I help you today?" is furniture. The message should prove a human (or a well-configured trigger) noticed the context:

Pricing page: "Deciding between plans? Happy to give you a straight answer on which fits."
Checkout: "If anything about shipping or returns is unclear, ask here — real person, quick answer."
Docs: "Looks like you're digging. Want to just ask?"

Measure it or turn it off

An invitation earns its interruption when it starts conversations that go somewhere. Watch three numbers: how often the invitation is accepted, how many accepted chats become qualified conversations, and whether pages with invitations convert better than before. If acceptance is low and falling, the message or the timing is wrong — fix one variable at a time. And keep one control page with no invitation; it keeps you honest.

The rules that keep invitations welcome

A proactive invitation is an interruption you chose to make, so the burden of being useful is entirely on you. A handful of rules separate the invitation that gets a reply from the one that gets the widget closed for good.

One per visit. If it is declined or ignored, do not ask again on the next page. A second invitation reads as pestering.
Never during a form. Checkout, signup and payment pages are where an overlay does the most damage. Invite before the form or after it fails, never mid-entry.
Respect the dismissal. A closed invitation should stay closed for the session and be remembered on the next visit.
Only when someone can answer. An invitation that opens onto an empty queue is worse than no invitation.
Never on mobile mid-scroll. A small screen makes an overlay a genuine obstruction. Be more conservative there, or skip it.

Write the message for the page it appears on

The single biggest determinant of response rate is whether the message refers to what the visitor is actually doing. Generic greetings are ignored because they are visibly automated.

On a pricing page: Not sure which plan fits? Tell me your team size and I will point you at the right one.
On a long product page: Happy to check whether this fits your setup — what are you running it with?
On a returning-visitor session: Welcome back — want me to pick up where you left off?
After a failed payment: Looks like that payment did not go through. Want a hand?

Avoid How can I help you today? as an opener. It puts the work back on the visitor, who now has to formulate a question before they get anything. Offering something specific is both more useful and more obviously human.

Choose triggers by intent, not by time alone

A fixed delay is the crudest possible trigger, and on its own it fires on people who are merely reading. Combine signals so the invitation lands on genuine hesitation:

Page plus dwell. Time on page only counts on pages where time means indecision — pricing, comparison, configuration.
Repeat visit. A third visit to the same product page is a much stronger signal than a first.
Return to the same page. Coming back after wandering off usually means an unresolved question.
High-value context. A large cart, an enterprise plan view, or a long configuration justifies an interruption that a blog post does not.
Error and failure states. The best trigger of all — something visibly went wrong and help is unambiguously welcome.

Common mistakes

The most damaging is treating the invitation as a campaign channel — using it to push a promotion rather than to offer help. It converts worse and it teaches visitors to dismiss the widget on sight, which costs you the reactive chats too.

The second is firing sitewide because it is easy to configure. Blanket invitations produce a large number of impressions, a poor response rate, and a slow erosion of trust in the widget. The third is leaving them running unchanged for a year; page layouts and traffic mix drift, and a trigger that made sense at launch may now fire on a page that no longer needs it.

What to measure

Response rate per rule is the primary number: invitations shown against invitations that produced a reply. Evaluate every rule separately, because a single sitewide average hides the one rule doing all the work and the one doing all the harm.

Then look past the reply. Compare conversion for visitors who accepted an invitation against similar visitors who were never shown one, and watch the dismissal rate as a health signal — a rule with a high show count and a very high dismissal rate is actively annoying people. Any rule that cannot demonstrate a benefit should be turned off rather than reworded indefinitely.

Proactive Chat Invitations: When to Trigger, What to Say