---
title: "Live Chat Triggers: 10 Examples With Rules and Messages"
description: "Live chat triggers are rules that open chat with a message when a visitor does something. Here are 10 examples with the exact rule and opening line."
canonical: https://luckpanda.app/blog/live-chat-triggers
author: "Dhrumil Barot"
author_bio: "Dhrumil is a small-business operations and compliance expert. Dhrumil built LuckPanda so small businesses can run invoicing, inventory, accounts and compliance in one place."
published: 2026-11-06
updated: 2026-11-06
category: "Customer support and chat"
keywords: "live chat triggers"
language: en
---

# Live Chat Triggers: 10 Examples With Rules and Messages

Live chat triggers are rules that open chat with a message when a visitor does something. Here are 10 examples with the exact rule and opening line.

By [Dhrumil Barot](https://luckpanda.app/about#founder), Founder. Published 6 Nov 2026. Updated 6 Nov 2026. 9 min read.

**TL;DR:** A live chat trigger is a rule that opens the chat window with a message when a visitor does something specific: lands on a page, stays a while, comes back, or hesitates at checkout. The good ones fire late, on high-intent pages, with one specific question. Below are 10 trigger examples, each with the rule to set, the message to send and when not to use it.

A live chat trigger (also called a proactive chat trigger, auto-greeting or targeted message) is an if-then rule in your chat tool: if a visitor matches a condition such as page URL, time on page, scroll depth, number of visits or cart value, then the widget opens or shows a message. Tidio, Intercom, Crisp, LiveChat, Zendesk and tawk.to all offer them under different names. The rules that work have three parts: a page (where), a condition (when) and an opening message that answers the question that page usually raises. Most lists stop at naming trigger types; the examples here give all three parts, plus the cases where a trigger hurts more than it helps.

![How a live chat trigger works: page, condition, message, reply](https://cdn.sanity.io/images/pcmcvz9y/production/778147d29baf843b2df471d367551971493418d9-1344x326.png?w=1200&auto=format&fit=max)

*A trigger only opens the door. The reply decides whether the chat turns into a lead.*

## What is a live chat trigger?

A live chat trigger is an automated rule that starts a chat conversation before the visitor clicks the chat button. It has three parts:

- **Audience and page:** who sees it and where. For example, URL contains /pricing, or first-time visitors only.
- **Condition:** when it fires. Time on page, scroll depth, number of pages viewed, returning visit, cart contents, an error on the page, or exit intent (the mouse moving toward the browser's close button).
- **Action:** what happens. Usually a short message in a small bubble next to the chat button; sometimes the full chat window opens.

Tidio describes triggers as rules that send automated messages to visitors and lists first visit, returning visitor, mouse leaves window, visitor clicks an icon, visitor opens a specific page, time on page, specific days, a new event and "visitor says" as the main types ([Tidio](https://www.tidio.com/blog/live-chat-triggers/)). Intercom calls the same thing an outbound Chat with audience and page rules, and notes that it can appear even on pages where the chat launcher is hidden, so you exclude pages with a rule such as "Current page URL does not contain" ([Intercom Help](https://www.intercom.com/help/en/articles/6612589-how-to-set-up-a-workflow-for-proactive-support)).

## How does the browser decide when to fire?

A proactive chat trigger fires by watching a few signals in the browser (the URL, a timer, scroll position, a cookie that marks a returning visitor, sometimes cart data from your store) and checking them against your rules. When every condition of a rule is true, the widget shows the message. Good tools also let you cap frequency (once per visitor, once per session) and stop the trigger when a chat is already open.

Three points the vendor lists leave out:

1. **Exit intent does not exist on phones.** It is detected from the mouse leaving the top of the window. On a touch screen there is no pointer, so an exit-intent rule never fires for most mobile traffic. Use time or scroll there instead.
2. **A trigger is a popup in Google's eyes when it covers content.** Google's guidance says intrusive dialogs that obstruct the page "may lead to poor search performance" and recommends small banners instead ([Google Search Central](https://developers.google.com/search/docs/appearance/avoid-intrusive-interstitials)). A small bubble beside the chat button is fine; a chat window that opens over the article on mobile is not.
3. **Bots must say they are bots.** If an AI bot sends the triggered message, say so in the greeting. NN/g found people talk more efficiently once they know a bot is answering ([NN/g](https://www.nngroup.com/articles/chat-ux/)), and since 2 August 2026 the EU AI Act's Article 50 requires telling people they are interacting with an AI system ([Article 50](https://artificialintelligenceact.eu/article/50/)).

## Sales triggers: examples 1 to 6

Each example gives the rule as you would set it in most chat tools, the opening message, and the case where you should leave it off. Times are starting points to test, not industry standards: no vendor publishes a neutral benchmark for them.

### 1. Pricing page hesitation

- **Rule:** URL contains /pricing AND time on page is more than 30 s AND the visitor has not clicked a plan.
- **Message:** "Comparing plans? Tell me roughly how many people would use it and I'll tell you which one fits."
- **Why it works:** someone reading prices for 30 seconds is doing maths. One question about their size gets you the qualifying detail you need anyway.
- **Skip it when:** your pricing page has a single plan and a clear button. There is nothing to help with.

### 2. Long read on a product or service page

- **Rule:** URL matches a product or service page AND scroll depth is more than 60% AND time on page is more than 45 s.
- **Message:** "Anything about \[product name\] the page doesn't answer? Sizes, delivery and lead times are the usual ones."
- **Why it works:** NN/g recommends a chat link on product pages because that is where clarification questions come up. Naming the usual questions shows you know what they are.
- **Skip it when:** the page is short. A 60% scroll on a 300-word page takes five seconds and proves nothing.

### 3. Returning visitor on a high-intent page

- **Rule:** visit count is 2 or more AND URL is a product, pricing or booking page AND no chat in this session.
- **Message:** "Welcome back. If you're close to deciding, I can answer the last question in under a minute."
- **Why it works:** a second visit to the same page is one of the strongest buying signals a small site gets.
- **Skip it when:** the visitor is a logged-in customer. Greet them with account help instead, or not at all.

### 4. Cart with items, idle

- **Rule:** cart value is more than 0 AND no activity for 60 s on the cart or checkout page.
- **Message:** "Stuck on anything? I can check delivery dates, returns or payment options for you."
- **Why it works:** the doubts at checkout are almost always delivery, returns and payment. Answering those beats a discount code.
- **Skip it when:** the visitor is typing card details. Never interrupt the payment step itself.

### 5. Checkout error

- **Rule:** an error message is shown on the page (failed coupon, address not valid, payment declined).
- **Message:** "That didn't go through. Want me to look at what happened? You can also just reply with the error text."
- **Why it works:** this is the one trigger where the visitor wants help immediately, so it can fire with no delay.
- **Skip it when:** you cannot see or explain the error. A bot that replies "please try again" makes it worse.

### 6. Booking or demo page, not booked

- **Rule:** URL contains /book or /demo AND time on page is more than 40 s AND the form is not submitted.
- **Message:** "If none of the slots work, tell me a time and I'll ask the team."
- **Why it works:** the usual reason for not booking is the calendar, not the decision.
- **Skip it when:** the page is a third-party embed you cannot see inside; the trigger cannot tell if they booked.

## Support and timing triggers: examples 7 to 10

These four catch visitors who are already trying to reach you, or who arrive when nobody is in.

### 7. Contact page

- **Rule:** URL contains /contact AND time on page is more than 10 s.
- **Message:** "I can answer most questions right here. What do you need?"
- **Why it works:** people on a contact page already want to talk. NN/g found that participants looked for chat under Help or Contact Us first.
- **Skip it when:** never, as long as someone or something can actually answer.

### 8. Help or FAQ page, deep search

- **Rule:** URL contains /help or /faq AND pages viewed in this session is 3 or more.
- **Message:** "Not finding it? Ask in your own words and I'll find the answer or pass you to a person."
- **Why it works:** three help pages in a row means the search failed. That is a support chat you want, and a note about a gap in your help content.
- **Skip it when:** the visitor arrived from a help-centre link you sent them yourself.

### 9. Visitor from a campaign

- **Rule:** URL contains a campaign parameter (for example utm_campaign=diwali) AND time on page is more than 20 s.
- **Message:** "Here for the \[campaign\] offer? Ask me anything about what's included."
- **Why it works:** the visitor already knows why they came; the message picks up the same thread instead of a generic hello.
- **Skip it when:** the campaign has ended. Expired offers in a chat bubble are worse than none.

### 10. After hours

- **Rule:** current time is outside your working hours AND URL is a pricing, contact or booking page AND time on page is more than 30 s.
- **Message:** "We're offline until 9 am, but I can answer from our pages now and pass anything else to the team for the morning."
- **Why it works:** it sets an honest expectation (NN/g recommends stating hours when live chat is not always on) and still captures the enquiry.
- **Skip it when:** nobody reads the overnight chats. Then you are only collecting disappointment.

### Which of the 10 to start with

Start with two or three triggers on your highest-intent pages and add more only after you have read the chats they produce.

| Trigger | Page | Condition | Starting delay | Main job |
| --- | --- | --- | --- | --- |
| Pricing hesitation | Pricing | No plan clicked | 30 s | Qualify and recommend a plan |
| Long product read | Product or service | Scroll over 60% | 45 s | Answer the open question |
| Returning visitor | Product, pricing, booking | Second visit or more | On load | Close the last doubt |
| Idle cart | Cart, checkout | No activity | 60 s | Delivery, returns, payment |
| Checkout error | Checkout | Error shown | None | Fix the problem |
| Booking not made | Book, demo | Form not sent | 40 s | Offer another time |
| Contact page | Contact | On the page | 10 s | Answer before they email |
| Help search | Help, FAQ | 3 or more pages | On the third page | Find the answer, hand off |
| Campaign visitor | Landing page | Campaign parameter | 20 s | Explain the offer |
| After hours | Pricing, contact | Outside hours | 30 s | Set expectations, capture |

## How long should the time-on-page delay be?

A time-on-page trigger should usually wait 20 to 60 seconds, and longer on pages that take time to read. The point is to fire after the visitor has had time to read and form a question, not on arrival. NN/g's popup research says never to prompt before people can get value from the page and never to ask for an email before they have interacted ([NN/g](https://www.nngroup.com/articles/popups/)). Tidio's own examples fire as early as 5 seconds on a first visit; that suits a simple store front page, not a pricing page someone is reading carefully.

A practical way to set it: check the average time on page in your analytics for that URL, and fire at roughly half of it. Visitors who are still there are the ones reading closely; visitors who leave earlier never see the bubble.

## Do proactive chat triggers annoy visitors?

Proactive chat triggers annoy visitors when they fire too early, too often, cover the content, or open with small talk. They help when they arrive at a moment of doubt with a useful question. The difference is in the details:

- **Too early:** a message on page load interrupts before the visitor knows what they need.
- **Too often:** a rule without a frequency cap fires on every page. Set once per session at most, and stop after the visitor closes it.
- **Covering content:** on mobile, a chat window that opens over the page is an interstitial. Show a small bubble and let them tap.
- **Small talk:** NN/g's study saw a user delete a typed question to answer "How are you?". Open with a question about their task.
- **Messages that look human but aren't:** NN/g also found automated system messages shown like agent replies confused users. Make bot and automatic messages look like what they are.

## Which pages should open a chat on their own?

The pages that should trigger chat are the ones where visitors make a decision or get stuck: pricing, product or service detail, cart and checkout, booking, contact and help. Pages that should not trigger chat are the ones people read for other reasons: blog posts and guides (unless a reader has scrolled to the end of a buying guide), careers, legal pages, the logged-in app for existing customers, and any page where the visitor is filling in a form.

![Pages that should and should not trigger chat](https://cdn.sanity.io/images/pcmcvz9y/production/efb824df1fcecb18e15a4936b3ac3c469736791b-1344x502.png?w=1200&auto=format&fit=max)

*Start with the left column, two or three pages at a time.*

## How do you measure whether a trigger works?

A trigger works when the chats it starts lead to something: a reply, a lead, a booking or a sale. Track for each trigger how many times it fired, how many visitors replied, and what those chats were about. A reply rate tells you if the timing and wording are right; the transcripts tell you if the page needs fixing. If the same question keeps coming from your pricing trigger, that answer belongs on the pricing page. Our guide to [live chat metrics](https://luckpanda.app/blog/live-chat-metrics) covers how to calculate reply, resolution and conversion rates, and [live chat best practices](https://luckpanda.app/blog/live-chat-best-practices) covers the rules for what happens after the first message.

The trigger only opens the conversation; the answer is what turns a visitor into a customer. [LuckPanda Chatbot](https://luckpanda.app/chatbot) answers visitors from your own pages and documents in the language they write in, asks at most two or three short questions, asks for contact details only once a visitor wants something, and suggests one next step. Every chat is saved word for word with the page it started on, so you can see which pages raise which questions. You can try it on your own website without an account.

## Questions

### What is the difference between a chat trigger and a chatbot?

A chat trigger decides when the chat starts; a chatbot decides what is said once it has started. Many tools combine the two: Tidio describes its triggers as chatbot nodes. You can use triggers with people answering, or a bot answering, or both.

### How many live chat triggers should a small website have?

Two or three to start: usually pricing, a key product or service page and the contact page. Each trigger you add is another message a visitor may see, so add one only after reading the chats the first ones produce.

### Should a chat trigger ask for an email address?

No, not in the first message. NN/g's research found that asking for an email before any interaction annoys people and makes them expect spam. Ask a question about their need first, and ask for contact details only when they want a quote, a booking or a follow-up.

### Do chat triggers work on mobile?

Time, scroll, page and returning-visitor triggers work on mobile. Exit-intent triggers do not, because they rely on the mouse leaving the window. On mobile, show a small bubble rather than opening the full chat window over the page.

### Can I write trigger messages in other languages?

Yes. Write the greeting in the language of the page it fires on. Intercom supports welcome messages in up to 45 languages. For quick wording ideas, our [free customer service tools](https://luckpanda.app/chatbot/tools/customer-service) include reply and greeting generators.

## More guides

- [Live Chat Best Practices: 12 Rules for People and AI Bots](https://luckpanda.app/blog/live-chat-best-practices)
- [Customer Feedback Categories: A Codebook With Examples](https://luckpanda.app/blog/customer-feedback-categories)
- [Live Chat Metrics: 14 KPIs, Formulas and What to Track](https://luckpanda.app/blog/live-chat-metrics)

## Related tools

- [Invoice generator](https://luckpanda.app/tools/invoice-generator): Bill a client in any currency, with tax worked out as you type.

## About the author

**Written by [Dhrumil Barot](https://luckpanda.app/about#founder)**, Founder. Dhrumil is a small-business operations and compliance expert. Dhrumil built LuckPanda so small businesses can run invoicing, inventory, accounts and compliance in one place. [LinkedIn](https://www.linkedin.com/in/bdhrumil) · [X](https://x.com/fyidhrumil)