Proactive chat messages that convert without annoying visitors

Most visitors with a question never ask it. They hesitate on the pricing page, reread a paragraph in the docs or stall at checkout, and then they leave. A proactive message, one your site sends before the visitor writes anything, gives them an easy way to ask. Done well, it starts conversations that would never have happened. Done badly, it teaches visitors to close your chat on sight.

The difference is almost entirely about relevance and restraint. Here is how to get both.

What makes a proactive message work

It is about the page the visitor is on. "Comparing plans? Happy to help you pick" works on a pricing page and nowhere else.
It is specific. Name a real question people ask on that page. Generic offers of help are easy to ignore because they say nothing.
It is rare. One well-timed message beats a message on every page.
It does not interrupt. The visitor should be able to carry on reading as if it were not there.
Someone can answer. Inviting a question when nobody is online sets you up to disappoint. Either match messages to your office hours or make the copy honest about reply times.

Targeting: who sees what

TalkingDot's auto messages can target visitors by six conditions. Combining two or three is usually enough.

Condition	What it is good for
Page URL	The most important one. Write a different message for pricing, docs, checkout and signup pages.
Time on page	Separates people skimming from people reading carefully or stuck. Wait long enough for the visitor to look around first.
Number of visits	Returning visitors are often closer to a decision, or still carrying the same unanswered question.
Country	Mention local delivery, currency or support hours, or speak to a regional audience.
Device	Keep mobile messages shorter, or skip them where screen space is tight.
Language	Greet visitors in their browser's language, if your team can actually reply in it.

Frequency: once or per session

Each TalkingDot auto message can be shown once, or once per session.

Once suits introductions and offers, such as a welcome for first-time visitors or a pointer to a setup guide. After someone has seen it, repeating it adds nothing.
Per session suits help tied to a task people come back to, such as a checkout question or an onboarding step, where a fresh visit often means a fresh need.

When in doubt, choose once. Over-messaging costs more than a message some visitors never see.

Copy examples you can adapt

Each example names the targeting it is written for. Only promise reply times you actually meet.

Pricing page

Target the pricing URL, after the visitor has spent a while on the page (try somewhere between 30 and 60 seconds and adjust).

Not sure which plan fits? Tell us roughly how many people will use it and we'll point you to the right one.

Documentation and help pages

Target docs URLs, a long time on page and a second or later visit. Someone who keeps coming back to the same page is often stuck.

Still working through setup? Tell us which step you're on and we'll help you finish it.

Checkout

Target the checkout URL, triggering only after longer than a normal checkout takes. Keep it short and practical: this visitor is close to buying and does not want a sales pitch.

Questions about delivery, payment or returns? Ask here before you order.

Returning visitors

Target a third visit or later on product pages, shown once.

Welcome back. If you're still weighing something up, ask us. We usually reply within a few minutes during office hours.

Visitors in another language

Target the browser language, matched to a language your team speaks. This Spanish example says "Have a question? Write to us in Spanish."

¿Tienes alguna pregunta? Escríbenos en español.

For the visitors who matter most, you do not have to wait for a rule. A teammate can start a conversation by hand from the live Visitors list, after checking which page the visitor is on.

What not to do

Firing on page load. The visitor has not had time to need help yet.
The same message everywhere. It becomes wallpaper, then an irritant.
Fake personal touches. "I noticed you've been looking around!" sent by a rule to every visitor feels personal only until people realise it is not.
Stacking messages. Several at once, or a proactive message to someone already chatting with you, is noise.
Silent promises. Inviting questions on a page where nobody can answer for hours, without saying so.
Discounts as a reflex. Offering a code to every hesitant visitor trains people to wait for one, including those who were going to buy anyway.

How to measure results

Change one thing at a time. One page, one message. Changing several at once makes it impossible to tell what worked.
Tag the conversations. A TalkingDot routing rule with a page condition can tag every conversation that starts on, say, your pricing page, so the tags report counts them for you.
Compare periods. Run the message for two weeks, then pause it or swap the copy for two weeks, and compare conversations started, CSAT and, in your analytics tool, conversions from that page.
Read the conversations. Numbers tell you whether people replied. Transcripts tell you whether the message helped or just interrupted.

If a message starts conversations but ratings fall, or replies are mostly "no thanks", rewrite it or switch it off. A quieter site with fewer, better messages usually wins.

The proactive messages guide shows how to set up targeting and frequency in TalkingDot. If you do not have a workspace yet, create one free and start with a single message on your pricing page.