Live Chat Triggers: Setup Guide with Examples

A chat widget sitting quietly in the corner waits for visitors to decide they need help. Most never do — they just leave. Live chat triggers flip that: the widget reaches out when a visitor’s behaviour suggests they’re stuck.

Done well, this is the highest-return configuration change available in chat. Done badly, it’s a popup.

The triggers that work

Time on page

The workhorse. Fire after a visitor has been on a commercial page long enough to suggest they’re deliberating rather than scanning.

• Product page: 30–45 seconds
• Pricing page: 45–60 seconds
• Checkout: 30 seconds
• Blog or content page: 90+ seconds, or don’t trigger at all

Exit intent

Mouse movement toward the browser chrome on desktop. The last chance to intervene, and worth reserving for high-value pages — cart, checkout, pricing.

Doesn’t exist meaningfully on mobile, so don’t build your strategy around it.

Scroll depth

A visitor who’s read 70% of a pricing or product page is engaged and evaluating. Often a better signal than raw time, because it accounts for how fast people read.

Specific URL

Different messages for different pages. Someone on your returns policy has a different problem from someone on your enterprise pricing page.

Cart value

Higher-value carts justify more attention. A trigger on carts above a threshold — offering to answer questions about delivery or warranty — targets the sessions where intervention pays most.

Returning visitor

Someone viewing the same product or pricing page for the second or third time has unresolved doubt. This is one of the strongest intent signals available and one of the least used.

Referral source

A visitor from a comparison article or a competitor review is evaluating alternatives. Worth a different message from organic search traffic.

Timing, and the mistake everyone makes

The single most common error is triggering on arrival. Five seconds after landing, before the visitor has read anything, a message appears asking if they need help. They haven’t formed a question yet, so the only possible response is to dismiss it — and now they’ve learned to dismiss your widget.

You get roughly one interruption per session before a visitor tunes the widget out. Spend it at the moment of genuine hesitation, not on arrival.

Set a global rule: at most one proactive message per visitor per session. Without it, three triggers firing in sequence makes the site feel like it’s chasing people around.

Example triggers you can copy

Product page, 40 seconds:

Any questions about sizing or delivery? Happy to help.

Cart page, 45 seconds without proceeding:

Anything holding you up? I can check stock or delivery dates right now.

Checkout, exit intent:

Before you go — was something unclear about shipping or payment? I can sort it in a moment.

Pricing page, 60 seconds:

Not sure which plan fits? Tell me your team size and I’ll point you to the right one.

Returns policy page, 20 seconds:

Need to start a return? I can get it moving for you.

Returning visitor, same product, second visit:

Welcome back. Still deciding? Happy to answer anything about this one.

High-value cart (over your threshold), 30 seconds:

Big order — want me to check delivery timing before you complete it?

Notice the pattern: specific to the page, phrased as an offer, referencing what the visitor is actually looking at. Generic “How can I help?” underperforms consistently because it puts the work of forming a question back on the visitor.

Mobile

Be more conservative. A proactive message covering content on a 375px screen is genuinely intrusive in a way it isn’t on desktop.

Many teams disable proactive triggers on mobile entirely and rely on the launcher — which is a defensible choice given that a mistimed message can obscure the checkout button.

At minimum: test every trigger on a real phone, and make sure dismissing it is easy and obvious.

When not to trigger

• When nobody can answer. A proactive message outside your hours, with no bot behind it, is worse than silence. If you’re covering with AI, make sure it’s set up first.
• On content pages. Someone reading a blog post isn’t blocked. Let them read.
• After a dismissal. If a visitor closed your message, don’t try again this session.
• During checkout on mobile, if the message covers any part of the payment flow.

Measuring them

• Engagement rate — proportion of triggered messages that get a reply. Under 5% suggests the timing or copy is wrong.
• Dismissal rate — high dismissals mean you’re firing too early.
• Conversion for engaged vs non-engaged visitors on the same page.
• Revenue per triggered session, if your tool attributes it.

Test one variable at a time. Changing timing and copy together tells you nothing about which mattered.

Where EasyChatDesk fits

EasyChatDesk supports proactive triggers by page, time on page, scroll depth and visitor behaviour, with per-page messages and an AI chatbot behind them so triggered conversations get answered even outside your hours. Everything lands in CRM ticketing so a triggered chat that needs follow-up isn’t lost.

Pricing is $17/agent/month with a 15-day free trial — see the full live chat widget features.

The takeaway

Triggers work when they’re tied to hesitation rather than arrival, specific to the page, and limited to one per session. Three well-timed triggers on your commercial pages will outperform a dozen firing everywhere.

Related: proactive live chat guide, live chat best practices, and ecommerce live chat support.