Bot, Then Silence: We Mystery-Shopped 15 Live-Chat Platforms to See Who Actually Picks Up
Photo: Oregon Department of Transportation, CC BY 2.0, via Wikimedia Commons
There's a moment every sales team knows. You're on a website, you click the chat bubble, a bot says hello within 0.3 seconds, and then you spend four minutes typing variations of can I speak to a person while it offers you a help centre article from 2023. That's not support. That's a maze with a friendly font.
So we went mystery shopping. Between 13 and 24 October 2026, we contacted 45 UK SME websites — three per platform, spread across retail, B2B services and hospitality — using the same three enquiries: a pre-sale product question during working hours, the same question at 8pm on a weekday, and a blunt request to talk to someone. Everything went through each site's own chat widget, as a customer would.
How we scored it
We logged four things: time to first bot reply, time to reach a live human, whether that human could actually help, and whether anyone was there outside 9-to-5. We didn't test integrations, pricing or admin dashboards — this was a customer's-eye view only.
One important caveat before the table. The platform doesn't answer the chat. The business does. A slow result here reflects the configuration and staffing of the three sites we tried, not necessarily what you'd get on your own install. Treat this as a snapshot of how these tools behave in the wild, not a verdict on the software itself. Small sample, one testing window, indicative only.
The results
| Rank | Platform | Median time to human (in hours) | Human at 8pm? | Sunday? |
|---|---|---|---|---|
| 1 | LiveChat | 48 sec | Yes (2/3) | Yes (1/3) |
| 2 | Crisp | 1m 05 | Yes (2/3) | No |
| 3 | Help Scout | 1m 20 | Yes (1/3) | No |
| 4 | Tidio | 1m 40 | Yes (2/3) | Yes (1/3) |
| 5 | Freshchat | 2m 10 | Yes (1/3) | No |
| 6 | HubSpot | 2m 30 | Yes (2/3) | No |
| 7 | Zoho SalesIQ | 3m 05 | No | No |
| 8 | Gorgias | 3m 40 | Yes (2/3) | No |
| 9 | Zendesk | 4m 15 | Yes (1/3) | No |
| 10 | tawk.to | 5m 30 | No | No |
| 11 | Olark | 6m 10 | No | No |
| 12 | Re:amaze | 7m 45 | No | No |
| 13 | Intercom | 9m 20 | No | Yes (1/3) |
| 14 | Chatwoot | 12m 40 | No | No |
| 15 | Pure Chat | 14m+ | No | No |
Median across all 45 tests: just over three minutes to reach a human in working hours. That's actually not bad. The problem is the tail — and the evenings.
What time-to-human really measures
A three-minute median sounds respectable until you split it. On the fastest sites, a human appeared in under a minute because the bot was configured to hand over the moment someone typed speak to a person, or mentioned a product name the bot didn't recognise. On the slowest, the bot had no exit at all — the enquiry sat in a queue behind an offline form and got an email reply the next morning.
The pattern was consistent: time-to-human had almost nothing to do with which platform was installed and everything to do with whether the business had set a handoff rule and staffed a rota.
The chatbot theatre awards
A few moments from the testing worth naming, all anonymised by platform type rather than brand:
Best looping performance: a bot that responded to I'd like to talk to a human with a cheerful would you like to talk to a human? Three times. In a row.
Most confident wrong answer: a bot that told us a coat was available in medium when the product page said out of stock.
Longest goodbye: a widget that asked us to complete a five-field satisfaction survey before releasing the chat window. Before. We hadn't spoken to anyone.
Quietest failure: two sites where the widget loaded, accepted the message, and gave no indication that no one was ever going to read it.
Out-of-hours is where most setups fall over
Only six of the 15 platforms had a human available at 8pm on any of our three test sites, and just three had one on a Sunday. That's the finding that should worry UK SMEs most, because evening is when people actually shop — sofa, phone, glass of something, deciding whether to buy.
What we saw instead were three patterns. The good one: an honest message saying we're offline until 9am, here's how to reach us, with a working form. The mediocre one: a bot pretending to be available and then dumping you into a void. The bad one: total silence.
If you can't staff evenings, at least be straight about it. A clear offline message with a next step costs nothing and keeps more goodwill than a fake greeting.
Rules that make handoff work
If you're reviewing your own setup, these are the settings that separated the fast sites from the slow ones:
- Always show a route to a person. Not hidden behind three menus. One tap, visible in every session.
- Trigger on frustration, not just keywords. Repeated questions, capital letters and the word human should all escalate.
- The two-strike rule. If the bot fails twice, hand over automatically. Don't wait for the customer to ask a third time.
- Route by page. A pricing-page chat and a delivery-page chat need different agents.
- Set honest hours in UK time and make sure they survive the October clock change. We saw more than one widget an hour out of sync.
- Show queue position if the wait is over 90 seconds, and offer a callback rather than a dead cursor.
Before you renew
Run your own version of this test. Send three chats from three devices at three different times of day, and time them yourself. If the number embarrasses you, it isn't a platform problem — it's a rota and rules problem, and both are cheaper to fix than a migration.
