A bounce is a visitor who arrives, looks at one page and leaves without doing anything. Some bounces are healthy: the visitor found what they needed, such as your phone number. Many are not: they had a question your page did not answer, could not find the price or were not sure the next step was for them. Chat can catch some of those visitors, but only if it is used carefully. A pop-up that fires the instant a page loads is an interruption, and it makes bounce worse. This guide explains what bounce rate does and does not tell you, when proactive chat helps, how to design triggers and messages that feel like service, how to limit frequency and how to measure whether it works.
What bounce rate really tells you
Bounce rate is the share of visits that end after a single page with no further interaction. Different analytics tools define it differently, and newer tools favour 'engagement' measures instead. A high bounce rate on a contact page may be fine if visitors call you. A high bounce rate on a pricing page is more worrying. Interpret it in the context of the page's job.
| Page | High bounce may mean | Response |
|---|---|---|
| Home | Unclear offer or wrong traffic | Clarify the promise; check traffic sources |
| Pricing | Price shock or unclear inclusions | Explain what is included; offer help in chat |
| Service page | Not convinced, or missing details | Add proof, FAQs and a chat prompt |
| Contact | Fine if they call or you get calls | Track calls; make phone tappable |
| Blog article | Read and left; normal | Offer a relevant next step, not a hard sell |
Do not chase a lower bounce rate for its own sake. The goal is more enquiries and bookings; bounce is a clue.
When proactive chat helps
- The visitor has been on a high-intent page (pricing, services, booking) for a while without acting.
- The visitor is about to leave, on a desktop, after viewing several pages.
- The visitor has returned to the site more than once.
- The visitor arrived from a source that usually means a question, such as a Google Business Profile or an ad for a specific service.
- Outside office hours, when your contact form will not be answered until morning.
When it hurts
- On the first second of the first page.
- On pages where reading is the goal, such as long articles.
- On mobile, where a pop-up covers most of the screen.
- On checkout, payment or form pages where it can derail completion.
- Repeatedly after being dismissed.
- When the message is generic and offers nothing.
The rule: interrupt only when you have something specific and useful to offer, and only once.
Trigger ideas that respect the visitor
| Trigger | Sensible setting | Message idea |
|---|---|---|
| Time on page | 20 to 40 seconds on pricing or services | Questions about prices or what is included? I can explain and show the next free time. |
| Scroll depth | After reading most of a service page | Want to know if this suits you? Tell me what you need. |
| Return visit | Second visit within a week | Welcome back. Want me to pick up where you left off, or check available times? |
| Exit intent (desktop) | When the cursor moves to close the tab | Before you go: can I answer a quick question? |
| Out of hours | Outside opening hours | Our team is offline, but I can answer questions and book you in. |
| Campaign landing page | After a short delay | Interested in [the offer]? Ask me anything, or book a time. |
Not every widget supports every trigger. Where triggers are limited, a greeting bubble that appears after a short delay, shown once per visit, is a safe default.
Write proactive messages that feel like help
| Avoid | Better |
|---|---|
| Need help? | Comparing options? I can explain what is included and find you a time. |
| Chat with us now! | Questions before you book? Ask me, I answer instantly. |
| Wait, do not leave! | Anything I can clear up before you decide? |
| Special offer just for you | Only mention offers that exist and apply to everyone |
- Be specific to the page.
- Offer something concrete: an answer, a price, a time.
- Keep it to one short line.
- Make dismissing it easy and respect the choice.
- Say it is an AI assistant, and mention that a person can help.
See chatbot welcome message copywriting for wording and thirty examples.
Frequency and courtesy limits
- Show a proactive message at most once per visit and not again for several days after dismissal.
- Do not open the full chat window automatically; show a small bubble.
- Never steal keyboard focus while someone is reading or typing.
- Respect accessibility settings such as reduced motion.
- Turn off proactive messages on pages where they interrupt tasks.
See accessibility for website chatbots for why auto-opening chats can exclude people.
What the assistant does after the click
A proactive prompt only helps if the conversation that follows is good. The assistant should answer the visitor's question from your documents, offer a next step such as booking or a callback, ask for contact details only when relevant and hand over to a person when needed. If the reply is slow, wrong or vague, the prompt just adds another reason to leave. Test the whole path, from prompt to booking, before you turn proactive messages on.
Measure the effect
- Record your baseline: bounce or engagement rate, enquiries and bookings for the pages involved.
- Turn on the proactive message for one page group only.
- Track chat opens, conversations, bookings and enquiries from those pages.
- Compare with the same pages before, or with similar pages without the prompt.
- Read the conversations that started from the prompt to see what visitors asked.
- Adjust the trigger and message, or turn it off if it does not help.
| Metric | What it tells you |
|---|---|
| Prompt views to chat opens | Whether the message attracts attention |
| Chat opens to booking or lead | Whether the conversation delivers |
| Bounce or engagement change | Whether visitors stay longer |
| Complaints or dismissals | Whether it is annoying |
| Total bookings per 100 visitors | The result that counts |
Give it several weeks and treat small differences with caution, especially on low-traffic pages.
Beyond chat: other ways to reduce bounce
- Make the first screen state clearly what you offer and the next action.
- Speed up mobile pages.
- Match landing pages to the ads or links that lead to them.
- Show prices and proof.
- Make phone numbers tappable.
- Fix broken links and confusing navigation.
A chat helps with unanswered questions, but it cannot rescue a page with an unclear offer. See the service business CRO playbook.
Example: a proactive prompt on a pricing page
A dental practice notices that its pricing page has a high exit rate. Reading conversations, the owner finds the same doubts: do you take my insurance, is the first visit different from a check-up, and is there a payment plan. She adds a small bubble on the pricing page, shown once after thirty seconds: 'Questions about prices, insurance or payment plans? I can answer them now.' She also adds those three answers to the assistant's documents and to the page itself. Over the next month the page's exit rate falls, chats from the page rise and bookings from it increase. The bubble helped, but so did fixing the page: the same questions that visitors asked in chat became content, which reduced the need to ask.
| Change | What it addresses |
|---|---|
| Bubble after thirty seconds on pricing | Visitors who read but hesitate |
| Insurance and payment answers added to the page | The doubts behind the exits |
| Handover if the assistant cannot answer | Visitors with unusual cases |
A quick audit of your own triggers
- List every place a chat message can appear today.
- For each, ask whether a visitor would welcome it at that moment.
- Remove any that fire before the visitor has had time to read.
- Check them on a phone.
- Check that dismissing one means it does not return the same day.
Frequently asked questions
Does a chatbot reduce bounce rate?
It can, when it answers questions that would otherwise make visitors leave. A badly timed pop-up can increase bounce instead.
When should a proactive chat message appear?
After a visitor has spent time on a high-intent page without acting, on a return visit, at exit intent on desktop or outside office hours. Not on the first second of a page.
Should the chat open automatically?
Generally no. Show a small bubble and let the visitor open it.
How often should proactive messages show?
Once per visit, and not again for several days after a dismissal.
Is bounce rate the right metric?
It is a clue, not the goal. Track enquiries and bookings per visitor.
Are proactive messages bad for accessibility?
They can be if they steal focus or interrupt. Avoid auto-opening and respect reduced-motion settings.
Try the assistant on your own pages' content in the playground, see the website widget options and start a free trial.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
ANSWER EVERY VISITOR. BOOK THE ONES WHO ARE READY.
Deploy Crescelo on your website in 15 minutes
Train your assistant on your price lists, documents, and service policies. Enable 24/7 grounded answers and conflict-free in-chat appointment booking.