Try it on your own data
Every report in this article is in the free plan. One snippet for web and apps, up to 10 sites.
Start freeProactive chat has a bad reputation because of how it is usually configured: a window pops up on the homepage after three seconds with "How can I help?" and the visitor closes it unread. The same feature, pointed at the right page with the right delay and a sentence that proves you know where the visitor is, behaves very differently. This guide covers the triggers, copy, limits and measurement that make the difference.
What you will learn
- Trigger on time spent on high-intent pages, not on arrival
- Write one specific sentence per page and invite each visitor once
- Judge invites by conversion against comparable visitors, not by conversations started
What changed · Nov 3, 2026
Rewritten with triggers, copy and frequency limits that match the product, measurement guidance and an FAQ.
Proactive chat best practices at a glanceWhy most invites failTriggers that match a real questionCopy that earns a replyFrequency limits that keep it politeStaff it, or say what happens nextMeasure conversion, not conversationsStart with one pageFAQ
Proactive chat best practices at a glance
New section
Proactive chat best practices come down to one idea: invite a visitor at the moment they have a question they have not typed yet, in words that prove you know where they are, and not again after they say no. A proactive chat invite is an interruption. On the homepage at three seconds nobody has a question; on the pricing page after a minute of comparing plans, many people do. The feature is the same; the moment decides whether it helps or annoys.
| Practice | Why it matters | How to apply it |
|---|---|---|
| Trigger on intent, not arrival | A question needs time to form | Target high-intent pages and wait for real dwell time |
| One page, one sentence | Generic lines are dismissed unread | Write copy that names the page or the decision |
| Invite once | Repeats feel like pop-up ads | Cap at one invite per visitor; respect a dismissal |
| Keep it small | Covering the page blocks the content the visitor came for | A small card near the chat bubble, easy to close |
| Only invite when someone can answer | An invite that leads to silence costs trust | Show invites when agents are online; say what happens offline |
| Judge by conversion | Conversations started is a vanity number | Compare invited and comparable non-invited visitors |
The rest of this guide takes each practice in turn, with the triggers, copy and measurement we use.
Why most invites fail
Section updated
The first failure is timing. "Hi there! How can I help?" three seconds after arrival interrupts someone who has not read a word yet, so they close it, and they learn to close the next one too.
The second is sameness. Every site says "How can I help?", so visitors have learned to dismiss it without reading. An invite that mentions the page ("Comparing Pro and Max? Ask about event limits here") gets read because it is obviously written for this moment.
The third is size. A chat window that slides over half a phone screen is an interstitial. Google's guidance for search is to prefer "banners that take up only a small fraction of the screen" over full-page overlays (Google Search Central). The same rule makes invites tolerable: a small card beside the bubble, not a window over the content.
Triggers that match a real question
New section
A good trigger is a signal that the visitor is stuck or deciding. These are the ones worth starting with:
| Trigger | Signal | Typical pages |
|---|---|---|
| Time on a decision page | Comparing options, reading the fine print | Pricing, plan comparison, shipping and returns |
| Time on a long how-to page | Trying something and possibly failing | Setup guides, integration docs |
| A specific step of a flow | Hesitating before committing | The second step of checkout, a quote form |
| Return to the same page | Unresolved question from an earlier visit | Pricing, product detail |
| Exit intent | About to leave | Desktop only: phones have no cursor to track |
Time on page is the most reliable trigger across devices, because it works the same on a phone and a laptop.
In TapCub an invite rule matches pages by every page, path contains, path prefix or a regular expression, then waits for a dwell time you set between 3 and 600 seconds. The invite text can be up to 300 characters and is shown in an online agent's name. If several rules match a page, only the highest-priority one fires, so rules never stack (proactive messages). Our pricing rule waits 45 seconds; that is a starting value to adjust from your own reply rates, not a benchmark.
TapCub also has two lighter tools: a teaser card that appears above the chat bubble about four seconds after arrival, once, and is not shown to visitors who already have a conversation; and a single line an agent can send to a live visitor, at most once per online window.
Invite rule · Pricing page
Active- Pagepath starts with
/pricing - Time on page≥
45 s - Priority
1 (highest)
Comparing Pro and VIP? Ask about event limits or data retention here — a real person replies.
- Only the highest-priority matching rule fires
- Each visitor invited once (default)
- Matching runs on the server; nothing stored in the browser
TapCub Support
Comparing Pro and VIP? Ask about event limits or data retention here — a real person replies.
Shown · 30 d
1,962
Opened
31.2%
Replied
18.4%
Copy that earns a reply
Section updated
Good invite copy names the page or task, asks a question the visitor can answer now, and fits in one sentence. Write a different line for each rule.
| Page | Generic | Specific |
|---|---|---|
| Pricing | How can I help? | Comparing Pro and Max? Ask about event limits or data retention here. |
| Setup docs | Need help? | Stuck installing the snippet? Paste your site URL and we will check it. |
| Checkout, step 2 | Any questions? | Questions about delivery times to your country? We can answer before you pay. |
| Returning to a product | Welcome back! | Still deciding on the Studio Pro kit? Ask us about sizes or shipping. |
A useful test before you ship a line: read it as the visitor, on that page, at that second. If it could appear on any other page unchanged, it is too generic. If it asks something the visitor cannot answer yet ("Ready to buy?" on a docs page), it is too early.
Frequency limits that keep it polite
New section
- Once per visitor. TapCub invites each visitor once by default. You can turn that off so every new connection on a matching page shows it again, but most sites should not.
- Never on the first second. Give the visitor time to read; the dwell timer is there for that.
- An obvious close control. Closing should be as easy as replying, on desktop and on touch screens.
- Do not steal focus. An invite that moves keyboard focus or covers the input the visitor was typing in is a usability bug, not a sales tactic.
- Fewer rules, not more. A handful of rules on the pages that matter beats a site-wide rule. Plans cap them anyway: Free includes 1 invite rule, Pro 10, Max unlimited.
Matching and frequency run on TapCub's server, and nothing about the invite is written into the visitor's browser.
Staff it, or say what happens next
New section
An invite promises a reply. If nobody is online, the promise breaks. Run invites when agents are online, and make the offline path explicit: outside office hours the widget uses your offline greeting, and the AI assistant can answer from the knowledge base and hand off when it cannot. Say "we reply by email within a day" if that is the truth. A visitor who knows what to expect is not disappointed.
Measure conversion, not conversations
Section updated
The wrong metric for an invite is the number of conversations it starts. Start with the rule's own numbers: TapCub's rule list records impressions, open rate and reply rate for each rule, so you can retire lines nobody answers.
Then ask the real question: did visitors who were invited convert more than comparable visitors who were not? Compare on the same page, over the same period, and remember that people who choose to chat were already more engaged. Treat the gap as an upper bound, and if you can, hold out a share of eligible visitors who are never invited. Because chat and analytics share one script and one visitor ID, the visitor's pages and later conversion sit next to the conversation.
| Pricing page · sample month | Visitors | Signed up | Rate |
|---|---|---|---|
| Invited and replied | 361 | 74 | 20.5% |
| Invited, did not reply | 1,601 | 142 | 8.9% |
| Left before the dwell time (not invited) | 438 | 19 | 4.3% |
| All pricing visitors | 2,400 | 235 | 9.8% |
Sample workspace. Visitors who chat are already more engaged, so read the gap as an upper bound and watch the trend.
Start with one page
Section updated
- Pick the one page where visitors are most likely to be stuck: pricing, a long setup guide or the second step of checkout.
- Write one sentence for it and set a dwell time.
- Run it for two weeks and read the reply rate weekly.
- Compare conversion for invited and comparable visitors.
- Change the copy or the delay before you add a second page.
Setup steps are in the chat installation guide. If your visitors write in other languages, two-way translation lets any agent answer the conversations an invite starts.
FAQ
New section
What is a good proactive chat trigger?
Time on a high-intent page, such as pricing or a long setup guide, is the most reliable starting trigger because it works on every device. Add page-specific copy and invite each visitor only once.
How long should I wait before showing a chat invite?
Long enough for a question to form. Start with tens of seconds on decision pages, not a few seconds after arrival, and adjust from the reply rate you see.
Do proactive chat invites annoy visitors?
They do when they fire on arrival, repeat after a dismissal, cover the page or use generic copy. A small, specific, one-time invite on the right page reads as help.
Should proactive chat run when no agent is online?
Only if the visitor gets a clear answer path: an AI reply from your knowledge base, or an honest promise of an email reply. An invite that leads to silence does more harm than no invite.
How do I measure whether proactive chat works?
Compare conversion for invited visitors against comparable visitors who were not invited, on the same page and period, alongside each rule's impressions, open rate and reply rate.
See also: Canned responses: 40 examples and how to write ones that don't sound canned.
See also: Live Chat Lead Generation: From First Chat to Closed Deal.
See also: Live Chat Examples: 10 Annotated Conversations and What Worked.
See also: Live Chat Welcome Message: Examples by Page Type and How to Test.
See also: Customer Engagement Automation: Three Trigger Rules With Numbers.
See also: Real-Time Customer Engagement: Triggers, Data and Examples.
Update history1
- Major updateRewritten with triggers, copy and frequency limits that match the product, measurement guidance and an FAQ.
- First published
Was this article helpful?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Customer Experience Consultant
Writes about live chat, visitor conversations, and self-service, sharing practical ways to make customer communication clearer and more effective.

Product Experience Specialist
Explores usability, user journeys, and feature adoption through practical examples of onboarding and everyday product use.



