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.
Here is a practical way to decide.
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 a visitor's behaviour signals real intent or hesitation:
- Dwelling on pricing. Time on a pricing or plans page is one of the clearest buying signals you have.
- A second or third visit. Returning visitors are weighing a decision. A familiar, helpful hello lands differently than it does for a first-timer.
- Stuck at checkout. Idle time on a cart or checkout step often means a small doubt (shipping, sizing, a coupon), that a one-line answer can clear.
- High-intent pages. A demo request, a comparison page, or a key product feature is a fair place to offer a hand.
- Arrived from a campaign. If someone clicked a specific ad, a message that matches that intent feels relevant, not random.
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
Restraint is what separates helpful from annoying:
- An instant popup on the homepage. Let people get their bearings before you interrupt.
- Mid-scroll on mobile. A message that covers the content someone is reading is a fast way to lose them.
- Every single page. Fire a greeting everywhere and it stops meaning anything. Reserve it for pages where a reply actually changes the outcome.
- While they are already chatting. Never stack a new proactive message on an open conversation.
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.
Three adjustments that usually pay for themselves:
- Fire on fewer pages. If desktop has five triggers, mobile probably wants one or two, on your highest-intent pages only.
- Wait longer. Mobile visitors scroll faster and scan more, so early engagement means less than it does on desktop.
- Keep the message to one line. A long 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 session.
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, the message has to be worth it:
- Be specific. "Questions about the Business plan?" beats a generic "Hi, how can I help?"
- Be helpful, not pushy. Offer to answer a question or remove a blocker, don't open with a hard sell.
- Make one ask. A single, easy reply ("Want a hand?") gets more responses than a wall of text.
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.
Sensible defaults:
- One proactive message per session. If it did not land, a second will not either.
- Respect a dismissal across pages. Closing the widget on pricing should mean it stays closed when they move to the docs.
- Never interrupt an open conversation. If a chat is already running, every trigger should be suppressed automatically.
- Suppress for existing customers where you can. A logged-in user asking a support question does not need a sales greeting.
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.
Done well, proactive chat feels like a good shop assistant: present at the right moment, invisible the rest of the time.
Next: the website buying signals worth building triggers around, and how to set proactive messages up in Initio.