Proactive Chat: When to Start the Conversation (With Examples)

Proactive chat means your team reaches out before the visitor asks — a short, relevant message at the moment someone is likely to need help. Done well, it feels like a good shop assistant who notices you hesitating. Done badly, it's the pop-up everyone closes on reflex. This guide covers when starting the conversation pays off, what to say on different pages, the rules that keep it from becoming noise, and how to practice it even without heavy automation.

What proactive chat is and why it works

Most visitors with a question never ask it. They hesitate on the pricing page, reread the shipping policy, and leave. A proactive message lowers the effort of asking: the chat is already open, someone has already spoken, and replying takes one line.

It works for three reasons:

• It removes the first-message barrier. Typing the opening line is the hardest part for many people.
• It's contextual. A message tied to the page the visitor is on feels like help, not marketing.
• It surfaces objections early. You learn what stops people from buying, which is valuable even when the chat doesn't convert.

Reactive vs proactive: when each makes sense

Reactive chat — waiting for the visitor to write — is the right default for support. People who come to fix a problem will find the button.

Proactive outreach makes sense when:

• the visitor is close to a decision (pricing, plan comparison, checkout);
• the product is complex or expensive enough that questions are expected;
• you have the people to answer quickly — a proactive message followed by a slow reply is worse than no message.

It makes less sense on blog posts, help articles people are reading calmly, or pages where the visitor is clearly browsing.

The best moments to start a chat

These are the moments teams most often use. Treat the timings as starting points to test, not rules.

• Pricing page. People comparing plans have specific questions about limits, billing and fit. A wait of roughly 20–40 seconds filters out quick bounces.
• Checkout or cart. Hesitation here is costly. A gentle offer of help with shipping, payment or promo codes can save the order.
• Return visits. Someone who comes back to the same product or plan page is seriously considering it.
• Long dwell on one page. A minute or more on a feature or product page often means the visitor is looking for an answer that isn't there.
• After an error or failed action. A form that didn't submit, a payment that failed — this is when help is most welcome.

Proactive message examples by page

The best proactive messages are short, specific and easy to answer. Avoid "How can I help you?" — it asks the visitor to do the work.

Pricing page:

• "Comparing plans? Tell me roughly how many people will use it and I'll point you to the right one."
• "Questions about billing or switching plans later? Happy to answer."

Product page (store):

• "Not sure about sizing? I can check measurements for this item."
• "Need it by a specific date? Tell me your city and I'll check delivery times."

Checkout:

• "Anything stopping you from completing the order? I can help with shipping, payment or promo codes."

Return visit:

• "Welcome back! Still deciding? I can answer anything that's holding you up."

B2B or service page:

• "Want a rough quote? Share what you need and we'll get back with a number."

For longer conversation flows after the first message, see our live chat scripts.

Rules that keep proactive chat from being annoying

Proactive chat fails when it's frequent, generic or slow. A few rules prevent most of the damage:

1. One invitation per visit, at most. If the visitor ignores or closes it, don't try again on the next page.
2. Never open on page load. Give people time to orient themselves first.
3. Be specific to the page. If you can't write a message that only makes sense on that page, don't send one.
4. Don't cover content. On mobile especially, an expanding chat window over the product photo hurts more than it helps.
5. Only reach out when someone can reply fast. Outside working hours, either stay quiet or say clearly when people are back.
6. Make it easy to dismiss. No guilt-tripping copy, no repeated nudges.
7. Review messages regularly. Retire the ones nobody answers.

Doing proactive chat manually: watching visitors' current page

Automated triggers are one way to do this, but not the only one, and they're not always the best starting point for a small team. A lot of what makes proactive chat work — relevance and timing — can be done by people with the right context.

ChatDeck doesn't send automated pop-up invitations. What it gives you to work proactively:

• A greeting you write yourself. The text visitors see when they open the widget is configurable. Make it useful ("Questions about plans or shipping? We usually reply within a few minutes.") instead of a generic hello.
• A visible launcher. You choose position, size, colors and corner style so the button is easy to find without getting in the way.
• Live page context. Once a visitor writes, the operator sees which page they're on right now, and that updates as they browse. If they move to checkout mid-conversation, you can offer help with that step before they ask.
• Follow-up in the same thread. Conversations are tied to the visitor, so an operator can add a follow-up to an existing conversation — say, "the size you asked about is back in stock" — and it's waiting in the chat when they return.
• Identified visitors. If you pass customer details via identify, operators know who they're talking to and can tailor the next step.

In practice, "proactive" for a small team often means being proactive *inside* the conversation: anticipating the next question, suggesting the right page, and offering help at the step the visitor has just reached. The AI assistant can also move the visitor to a relevant page of your site when that's the quickest answer.

Measuring whether proactive messages help

Don't judge proactive chat by gut feel. Track a few things before and after a change:

• Reply rate to the greeting or invitation — are people engaging?
• Conversion of visitors who chatted vs those who didn't, on the same pages.
• Chat volume vs response time — more chats are only good if you can still answer quickly. See lead generation with live chat for how to qualify the extra conversations.
• Ratings after resolved conversations, to check that engagement isn't coming at the cost of satisfaction.

Change one thing at a time — the copy, the page, the timing — and give each version enough traffic before deciding.

Frequently asked questions

What is proactive chat?

Proactive chat is when a business starts the conversation with a website visitor instead of waiting for them to write, usually with a short message tied to the page they're on or what they're doing.

How long should I wait before sending a proactive message?

There's no universal number. Many teams start somewhere around 20–60 seconds on high-intent pages and adjust based on reply rates. Never send it the moment the page loads.

Is proactive chat intrusive?

It can be, if it's generic, frequent or blocks content. One specific, well-timed message that's easy to dismiss rarely bothers people; repeated pop-ups on every page do.

What should a proactive chat message say?

Something specific to the page that's easy to answer: a concrete offer of help ("Not sure about sizing?") rather than a generic "How can I help you?".

Get started

ChatDeck gives you a configurable greeting and launcher, live page context for operators, and an AI assistant that can answer first and hand off to a person, with no per-operator fees. Create a free workspace and read our guide to ecommerce live chat for store-specific ideas. To set the greeting text and launcher, see Style the chat widget.