Proactive Chat Timing: When to Trigger Matters More Than What You Say

Proactive chat has a trust problem. Most visitors have been interrupted by bad proactive chat - a window that fires 3 seconds after they land on a homepage, before they've read a single word. That experience trains people to dismiss proactive chat on reflex, the way they dismiss cookie consent banners. The technology gets blamed, but the real problem is almost always timing.

Good proactive chat timing is contextual. It varies by page type, visitor behavior, device, and the nature of what you want the visitor to do. There is no universal rule. What there is: a framework for setting timing by context, and A/B test data that shows what actually moves the needle.

Why the 3-Second Rule Fails

The "3-second rule" - fire the chat widget 3 seconds after a visitor lands - was built on a misread of attention research. The finding it references is that websites have roughly 3-5 seconds to communicate their value proposition before a visitor decides to stay or leave. The conclusion that was drawn: if you chat them before they decide to leave, you'll retain them. This is backwards.

A visitor who hasn't yet decided whether this page is relevant to them is not ready for a conversation. A chat window that appears before they've oriented themselves on the page creates cognitive load at the worst possible moment. They're trying to process the page and respond to an invitation simultaneously. Most choose to close the chat window - and that dismissal sets a negative tone that makes them less likely to engage with chat later, when they actually have a question.

The Right Framework: Trigger Time by Page Type

Different pages have different jobs. A homepage is introducing; a pricing page is evaluating; a checkout page is transacting. The visitor's state of mind at each is different, and the appropriate timing for proactive chat is different accordingly.

Behavioral Triggers vs. Time-Based Triggers

Time-on-page is a proxy for engagement, but behavioral triggers can be more precise. These are signals from visitor behavior that indicate a specific moment to intervene:

Exit intent: Mouse movement toward the browser chrome or back button. Historically effective for cart abandonment - "Wait - do you have questions before you go?" - but widely overused and now often dismissed reflexively. Use it only if your other timing is already good; exit intent alone won't save a poorly designed proactive strategy.

Scroll depth without interaction: A visitor who scrolls to the bottom of a pricing page without clicking any CTA has read everything and made no decision. That's a specific moment where a chat prompt has high relevance: "Have you seen everything you need? Happy to answer any questions."

Return visit: A visitor returning for the second or third time is in a different stage than a first-time visitor. They've already evaluated. They're likely comparing or trying to resolve a remaining concern. Earlier, more direct proactive chat is appropriate: "Welcome back - can I help you make a decision today?"

Time on a specific element: Some platforms can track hover time on specific page elements. A visitor who has hovered on the pricing table for 60 seconds has a pricing question. This is the most precise proactive trigger available, but requires more technical setup than time-on-page.

Mobile vs. Desktop: Different Rules

Mobile visitors behave differently on proactive chat, and the differences are significant enough to warrant separate timing rules for each device type.

On mobile, a proactive chat that opens as a full window is competing with the content of the page for the entire screen. Even a well-timed message can drive dismissal if the presentation is wrong. The better approach on mobile is a notification-style badge or collapsed prompt - visible without covering content, easy to engage or ignore.

A/B Test Data: What Actually Moves the Needle

These findings come from structured A/B tests run across Velaro deployments. Each test ran for a minimum of 2,000 visitors per variant:

Pricing page timing test - 30s vs. 60s vs. 90s trigger: 30-second trigger drove the highest engagement rate (more opens) but the lowest conversation completion rate - most visitors who opened closed immediately. 60-second trigger had the best balance: 42% engagement rate, 78% conversation completion rate. 90-second trigger had lower engagement but even higher conversation quality - virtually every visitor who opened had a substantive question. For teams with limited agent capacity, 90 seconds is often the right choice.

Checkout page - time-based vs. scroll-completion trigger: Time-based trigger (45 seconds) outperformed on raw engagement. Scroll-completion trigger (reaching the order total without clicking checkout) outperformed on conversion rate by 23%. Visitors who had read the complete checkout page and still hadn't clicked were more likely to have a specific objection, and more likely to resolve it and complete purchase through chat.

Message framing - question vs. statement: "Have questions about our pricing?" vs. "I can help you find the right plan." The question format drove 18% higher engagement rate across pricing and product pages. Questions signal that a response is expected, which increases the perceived appropriateness of opening the conversation.

Triggers to Avoid

Some proactive chat trigger configurations reliably hurt performance regardless of the message:

• Triggering on every page, every visit: If a returning visitor has already dismissed proactive chat twice, suppress it. Repeated interruption trains visitors to close without reading.
• Triggering before page load completes: A chat window that appears while the page is still loading competes with the page load for cognitive attention. Wait until the page is fully rendered.
• Triggering during active form fill: If a visitor is filling in checkout fields, they're in a transaction flow. Interrupting that flow is almost always counterproductive.
• Using the same message on every page: A generic "How can I help you today?" has lower conversion than a context-specific message that acknowledges what page they're on.
• Not capping trigger frequency: If the visitor closes the chat twice in one session, don't trigger a third time. Respect the signal.

"The visitors who dismiss your proactive chat aren't telling you to stop using it. They're telling you the timing was wrong. Fix the timing."

Building Your Timing Configuration

Start with three pages: your pricing page (or high-intent product page), your checkout page, and your support/FAQ page. These have the clearest intent signals and the most direct impact on both support and sales outcomes.

1. Set pricing page trigger to 45 seconds with a question-format message referencing the specific evaluation decision. Run for 1,000 visitor sessions before evaluating.
2. Set checkout trigger to scroll-completion OR 60 seconds, whichever comes first. Message should be specific to the friction point: "Need help before you complete your order?"
3. Set support page trigger to 25 seconds. These visitors have a problem. Don't make them wait long to get help.
4. Set all other pages to 90 seconds or suppress entirely. Protect attention on pages where content consumption is the goal.

After two weeks and at least 2,000 sessions per page, review engagement rate and conversation completion rate separately. High engagement with low completion means timing is right but message needs work. Low engagement means timing might still be too early - test adding 20-30 more seconds.

For the specific message scripts that work once visitors engage, see our companion post: Proactive Chat Scripts That Don't Feel Like Pop-Ups.

The Bottom Line

Proactive chat timing is an optimization exercise, not a setting you configure once and forget. The right trigger time varies by page type, visitor device, and visit history. The worst mistake is applying a single global timing rule across your entire site. The best approach is page-specific timing, behavioral triggers where possible, and a consistent testing cadence to keep improving.

Get the timing right, and the message almost writes itself. Get it wrong, and no message will overcome the irritation of an interruption that arrived before it was wanted.