Monday, 9.04am. Someone opens the CRM and there, in the "New" column, is an immaculate record: name, phone, email, source "website form", campaign tagged, owner assigned. Time received: Saturday, 9.47pm.
The CRM did its entire job without a single fault. It captured, cleaned, attributed, assigned and notified. The one thing it did not do was reply.
And there is something worse. This month's report will say that lead was answered in four minutes.
Nobody searches for this problem in these words
Google's autocomplete only suggests strings with real search volume behind them. It is crude, but it does not lie. Here is what it returns at the end of July 2026.
My CRM doesn't, crm response time, sales enquiries not answered: no suggestions at all. Type why is my CRM and Google offers why is the CRM bad, why is the CRM evil — the Civic Republic Military, from The Walking Dead. Nobody is typing this complaint.
What does have a long tail is the workaround: crm whatsapp integration, hubspot crm whatsapp integration, crm with whatsapp integration free. People already know where the hole is. They want a bridge between the place messages arrive and the place they get logged.
The problem does have a name — speed to lead — with a whole family behind it: speed to lead statistics, speed to lead data, lead response time harvard business review. Look at that last one: they are not searching for the fix, they are searching for the study, to put on a slide. And that is most of the content that already exists: pages titled "response time statistics 2026" recycling two old pieces of research without saying how old.
Where the numbers you'll be quoted come from
Worth knowing the provenance, because you will hear these in any CRM demo.
The 21× comes from the 2007 Lead Response Management Study, led by James Oldroyd at MIT Sloan with InsideSales.com: three years of data, six companies, more than 15,000 leads and over 100,000 call attempts. It says the odds of qualifying a lead if you call within 5 minutes versus 30 drop by 21 times, and the odds of making contact by 100. Those are phone calls to web-form leads, in the United States, in 2007. Not WhatsApp, not Britain, not 2026. The 42-hour average comes from Oldroyd and McElheran in Harvard Business Review, March 2011, "The Short Life of Online Sales Leads". Also fifteen years old.
The recent and more uncomfortable figure is RevenueHero's, published 20 March 2024: they requested demos from 1,000 B2B software companies. 635 never replied. Of the 365 that did, the average was 1 day, 5 hours and 17 minutes — though 172 replied in under two minutes. It is real data with a method behind it, but it is B2B software. It tells you nothing about how long a dental practice in Guildford takes.
The figure you actually want does not exist. There is no public 2026 dataset on how quickly a British service business answers a sales enquiry. If someone shows you one, ask for the methodology before you look at the number.
The CRM counts from the record, not from the customer
Here is the mechanism behind the four-minute report.
Almost every "time to first response" report starts the clock when the record is created. And the record is not created when the customer writes. It is created when the form syncs, when the integration flushes its queue, or when someone pastes the message in by hand on Monday. The customer waited thirty-five hours. The CRM timed four minutes. Both numbers are correct; only one matters.
Check it in five minutes: take the last enquiry that came in on WhatsApp out of hours, look at the timestamp on the phone, then look at the record's created-at timestamp. If they do not match, your response metric is measuring the speed of your integration, not your team.
Two other effects push the same way. Assigning is not answering: round-robin allocates the lead to whoever is next on the list, whether they are in a meeting, off sick or at lunch, and the record sits still but owned — which on a dashboard looks a lot like handled. And the acknowledgement counts as a reply in the report and as nothing to the customer: "thanks, we've received your message" closes the task in the system without closing anything in the head of the person who wrote it.
WhatsApp's 24-hour window does not wait until Monday
This part is not a matter of opinion. It is in Meta's documentation.
When someone messages or calls you on WhatsApp, a 24-hour customer service window opens. While it is open you can send free-form messages and they cost nothing — "all non-template messages are free", the documentation says, and they can only be sent inside that window. When it closes, you can only send pre-approved templates. Since 1 July 2025 Meta bills per delivered message, and only charges for templates.
Translated into your Monday: the Saturday 9.47pm message had its window open until Sunday 9.47pm. By 9.04am Monday you can no longer simply reply. You need an approved template, which costs money and reads like a company rather than a person. Your CRM does not carry that countdown on the card. Meta publishes per-country rates in sheets it updates on its own schedule, and has announced changes for 1 October 2026; we are not reproducing figures here because they age faster than the article.
What answering fast does not fix
It does not sell. A bad lead answered in thirty seconds is still a bad lead; all you gain is finding out sooner. Speed widens the top of the funnel, it does not close the bottom.
It does not discharge a legal duty, because there isn't one. No UK law sets a deadline for replying to a sales enquiry. The only response clock in general law that touches nearly every business is UK GDPR: a subject access request must be answered without undue delay and within one month, extendable by up to two further months where the request is complex or numerous, per ICO guidance. That is a data request, not someone wanting a quote. For contrast, Spain passed a customer service law in December 2025 requiring 95 per cent of calls to be answered within three minutes on average. Britain has nothing equivalent.
It does not stop people leaving. YouGov, for Answer4u, surveyed 2,046 UK adults between 5 and 8 June 2026: 37 per cent would give up on a call inside 60 seconds and try a competitor, and 24 per cent would switch to another way of contacting the business rather than wait. That is the phone, not chat, but it tells you where the traffic goes when nobody picks up: into your inbox, at nine on a Saturday night.
It does not replace a person, and it does not tidy your CRM. Answering in seconds and dumping it into a pipeline nobody opens just moves the problem.
How to measure yours this week
Without buying anything. Take the last thirty enquiries. Two columns: the timestamp of the customer's first message, taken from WhatsApp or the inbox and never from the CRM; and the timestamp of your first reply with actual content in it, which is not the auto-acknowledgement. Work out the median, not the mean — one three-day reply wrecks an average and hides everything else. Then split working hours from out of hours. That second number is usually the whole article.
If the gap turns out to be evenings and weekends, we have written about that. If it turns out to be the form itself, that too.
Zatio is one way to cover that gap: it replies on WhatsApp and on your website chat in seconds, inside the 24-hour window, and hands the conversation to your team with the context when it needs to. It discloses that it is an AI in the first message. It will not fix your CRM or close your deals; it just stops someone talking into the void until Monday.