Chat only helps if somebody answers. An unattended chat widget is worse than no chat at all.
TL;DR Decide whether you can genuinely staff it before installing anything. Use AI for the first exchange and booking, humans for anything specific. Delay the widget load or it will wreck your page speed for the majority who never open it.
The honest first question
Can somebody reply within two minutes during business hours?
If no, do not install live chat. Install a callback form instead.
A chat that goes unanswered creates a worse impression than no chat, because the visitor tried and was ignored. Some widgets display a response-time indicator, and a bad one is public.
Human, AI, or hybrid
| Model | Cost | Best for |
|---|---|---|
| Human, staffed | Time or salary | High-ticket work, complex quoting |
| AI only | Low monthly | FAQs, booking, after hours |
| Hybrid | Medium | Most service businesses |
| Outsourced chat service | Monthly per lead | High volume, no internal capacity |
Hybrid is usually right. AI handles the opening, answers the three questions everybody asks, and offers booking. It escalates to a human the moment the conversation gets specific.
Test any AI tool by asking it your hardest question. If it produces a confident wrong answer about pricing or scope, your customers will get the same, and that is worse than silence.
Proactive prompts, used sparingly
A chat bubble that opens itself can help or can be an interruption. Placement and timing decide which.
Rules
- Never in the first 20 seconds. Let them read.
- Trigger on intent, not on arrival. Time on a service page, scroll depth, or a second visit.
- Page-specific messages. On a pricing page: “Want a ballpark for your job?” On a service page: “Want to check if we cover your street?”
- Once per session. If they dismiss it, do not reopen.
- Never on mobile as a full-screen takeover. Google treats intrusive interstitials unfavourably, and users treat them worse.
Generic prompts fail. “Hi, how can I help you today?” gets dismissed reflexively. A specific question about the page they are on gets answered.
Pre-qualifying without an interrogation
You want enough to route the conversation, not a full intake.
Three questions, maximum, conversationally
- What is going on? Open, lets them describe it.
- Which town are you in? Confirms serviceability immediately.
- Is this urgent or are you planning ahead? Routes to today’s schedule or the quote pipeline.
Then move to booking or a human. Anything past three questions in a chat window feels like a form with extra steps, and people leave.
Ask for contact details after you have given value, not before. Answer their question first, then “what is the best number to reach you on?”
Booking inside the chat
The strongest chat implementations close the loop without a channel switch.
- Embed available slots directly in the conversation.
- Or send a booking link into the thread.
- Or take the phone number and call while they are still on the site.
That last one is underrated. “What is your number, I will call you in two minutes” converts extremely well because the person is on the page right now, and it removes every remaining step.
The page speed problem
Chat widgets are among the heaviest third-party scripts on a typical site. Most visitors never open the chat, but every visitor pays the loading cost.
How to fix it
- Delay the script until the user scrolls, moves toward exiting, or after 5 to 10 seconds.
- Or load on interaction: show a lightweight button, load the real widget only when tapped.
- Check the impact. Run PageSpeed Insights with the widget and without it. If it is costing you a second, that trade is almost certainly bad.
Google’s threshold is 2.5 seconds for main content at the 75th percentile. A chat widget alone can push a decent site past it.
After-hours behaviour
Change the mode when you close.
- Set the status to offline honestly. Do not show “online” at 11pm.
- Switch the prompt to a message-capture: “We are closed until 7:30am. Leave your number and we will call first thing.”
- Or route to a booking link, which works without you.
- Reply first thing, before anything else in your day.
What to measure
- Chats started, and what percentage of visitors that represents.
- Response time, which is the metric that decides whether chat works.
- Chat to booked job rate, not chat to lead.
- Page speed impact, measured with and without.
- Abandoned chats, meaning the visitor left mid-conversation. High numbers mean slow replies.
Install the widget on a delayed load and answer every chat within two minutes for two weeks. If you cannot sustain that, remove it and use a callback form. Half-staffed chat costs more than it earns.
Need a pro to set it up? [CALL NOW]