All guides

Proactive

When to use proactive chat (and when to hold back)

Proactive chat can rescue a sale or annoy a visitor. The triggers worth firing, the moments to stay quiet, and how to write a message that earns the interruption.

5 min readThe Initio team

Most people will never click your chat bubble. They browse, form a quiet question, and leave. Proactive chat fixes that by starting the conversation for you, but only if you pick the right moment. Reach out at the wrong time and you become the pop-up everyone closes on reflex.

What is proactive chat?

Proactive chat is a message sent automatically to a website visitor based on their behaviour, rather than waiting for them to open the chat window. Triggers are typically time on a page, the specific page viewed, the number of previous visits, or the traffic source that brought them.

The distinction from standard live chat is who starts the conversation. Live chat answers the people who choose to ask; proactive chat reaches the much larger group who never would.

Good moments to reach out

The best triggers fire when behaviour shows intent or doubt. Time on a pricing or plans page is the clearest buying signal most sites have. A second or third visit means someone is weighing a decision, and a hello lands differently than it does for a first-timer. Idle time on a cart or checkout step usually hides one small doubt, such as shipping, sizing or a coupon, that a one-line answer clears. Demo and comparison pages are fair places to offer a hand, and so is a visit from a specific ad, as long as the message matches what the ad promised.

How long should you wait before firing?

There is no universal number, because the right delay depends entirely on what the page is for. The useful principle: wait long enough that the visitor has clearly engaged, but not so long that they have already given up and left.

As a starting point to tune from:

  • Pricing and plan pages: on the longer side. Give them time to actually read the tiers. Firing the moment they land reads as a sales ambush on the one page where trust matters most.
  • Documentation and technical pages: longer still. Someone reading integration docs is concentrating. Interrupt early and you break their focus for nothing.
  • Checkout and cart: shorter. Hesitation here is usually a specific, small doubt, and it goes stale fast. This is the one place where being quick genuinely helps.
  • Blog and content pages: usually never. Most readers are not buyers yet, and a greeting mid-article is pure friction.

Whatever you choose, treat the first numbers as a hypothesis rather than a setting. The reply rate per trigger will tell you within a couple of weeks whether you are early, late, or on time.

Moments to stay quiet

Don't pop up on the homepage the moment someone lands; let them get their bearings first. On a phone, never cover the paragraph someone is reading. Skip pages where a reply wouldn't change anything, because a greeting that fires everywhere stops meaning anything. And never stack a proactive message on a chat that's already open.

Mobile deserves stricter rules than desktop

A proactive message costs far more on a phone than on a laptop. The screen is smaller, so a chat panel covers a much larger share of what the visitor is reading, and dismissing it takes a deliberate tap rather than a glance.

On mobile, change three things. Fire on fewer pages: if desktop has five triggers, mobile probably wants one or two, on your highest-intent pages. Wait longer, since phone visitors scroll faster and early engagement means less. Keep the message to one line, because a greeting that pushes the content off-screen gets closed on reflex, and that dismissal teaches the visitor to ignore your widget for the rest of the visit.

If you only have the appetite to configure one set of rules, configure them for mobile and let desktop inherit. The reverse almost always over-fires. It is also worth checking how the widget looks and sits on a small screen before you turn any trigger on.

Make the message earn the interruption

When you do reach out, name the thing on the page. "Questions about the Business plan?" beats "Hi, how can I help?" every time. Offer to clear a doubt instead of opening with a pitch, and ask for one easy reply. "Want a hand?" gets answered; a paragraph doesn't.

Rewriting a weak message

The difference is usually specificity. A generic greeting asks the visitor to do the work of explaining themselves; a specific one shows you already understand where they are.

  • Weak: "Hi! How can I help you today?" Better: "Comparing Growth and Business? Happy to explain what changes at each tier."
  • Weak: "Let us know if you have questions." Better: "If you need SSO or SAML, I can point you to the right doc."
  • Weak: "Want to book a demo?" Better: "Want me to answer anything before you decide whether a demo is worth your time?"

Note what the stronger versions have in common. Each one names something concrete from the page the visitor is on, offers to remove a specific blocker, and can be answered with a single short reply. None of them asks for a commitment.

Frequency, suppression and the right to be ignored

The fastest way to poison a good trigger is to fire it repeatedly. A visitor who closed your message has given you an answer, and re-asking treats their decision as an obstacle.

Good defaults:

  • One proactive message per visit. If the first didn't land, a second won't either.
  • A dismissal holds across pages. Closing the widget on pricing should keep it closed on the docs.
  • No trigger fires while a chat is open.
  • Logged-in customers don't get sales greetings when you can tell who they are.

Restraint compounds. A visitor who has never been spammed by your widget is far more likely to open it themselves on the visit that actually matters.

Measure, then trim

A well-targeted proactive message will reliably out-perform a chat bubble most visitors never touch, but the only benchmark that matters is your own. Measure the reply rate per trigger, watch which ones start real conversations and which get dismissed, then switch off the ones that don't earn their place. A small set of well-timed messages will always beat a noisy one.

Next: the website buying signals worth building triggers around, and how to set proactive messages up in Initio.

Keep
reading.

Stay in the loop

New guides.
No noise.

An email when a new guide is out. Unsubscribe any time.

Stop reading.
Start chatting.

The free plan includes Alynx and needs no card.