The Phone Assistant That Got Customer Bookings Wrong
An AI voice assistant was meant to book customer calls straight into the calendar without anyone checking — instead it produced wrong addresses and double bookings. What the cleanup cost, and where a simple approval step would have been enough.
- KI im Alltag
- Fehleranalyse
- Terminplanung
- Automatisierung
- Kundenkontakt
AI-assisted · editorially reviewed Details
The Phone Assistant That Got Customer Bookings Wrong
Say a plumbing and heating company with eight employees — a constructed example, chosen because the pattern repeats across small trades businesses — decides to hand phone-based appointment booking over entirely to an AI voice assistant. Once a calendar slot is created straight from a phone call with no human checking it, the quality of that entry depends entirely on how well the software understood what was said.
The plan: let calls turn into bookings on their own
According to the Trustlocal survey of local trades and service businesses, 66 percent of respondents use AI at least several times a week, and 44 percent use it daily. For the company in this example, the next step seemed obvious: if AI already handles customer messages, why not phone bookings too? The assistant was meant to pull the name, address, job type and preferred date out of the conversation and write a slot directly into the calendar — no one in the office would look at it again. The same survey does mention that step: 56 percent of businesses say they check AI output carefully before it goes further. In this example, that check was deliberately skipped, because it would have eaten up the time saved.
What actually happened
Street names spoken with a regional accent, house numbers rattled off quickly, callback numbers lost in background noise — routine for a receptionist, a source of errors for a speech recognition system. Calls from older customers who spoke slowly or paused mid-sentence were misrecorded far more often than average: double-booked slots, swapped weekdays, an address from the next town over instead of the caller's own street. A separate article on digital reading and explanation aids for people with reading difficulties describes a related pattern in a different context: tools built to remove barriers can, under certain conditions, create new ones instead. The phone assistant showed the same principle in its own domain: it helped the callers who already struggled to speak clearly and quickly the least.
Nobody noticed right away. It took two customers showing up expecting a technician at the same time on the same day for the pattern to surface. A quick check of the previous weeks showed it hadn't been a one-off.
What the corrections cost
There's no measured error rate from this particular business — the calculation below works with clearly stated assumptions instead of observed data.
| Variable | Assumed value |
|---|---|
| Calls per week | 30 |
| Recorded incorrectly | 6 |
| Weeks until discovery | 4 |
| Time per correction call | 15 minutes |
| Hourly rate (assumed) | €30 gross |
Fifteen minutes at €30 an hour comes to €7.50 per correction call. Six wrong bookings a week over four weeks means 24 correction calls, so €180 just for calling people back. On top of that, a one-time review of the past weeks' calendar entries, assumed at three hours and the same €30 rate, adds another €90. Total: €270 over four weeks, purely for cleanup — the time the assistant was supposed to save in the first place isn't counted in that figure.
As a check: doubling call volume to 60 a week at the same 20 percent error rate doubles the correction cost to €360. Halving it to 15 calls a week brings it down to €90, and that's where the calculation starts to miss the point. At low volumes, a single mistake surfaces less often, discovery takes longer, and the real cost stops being the correction calls and becomes the one customer who, after a missed appointment, simply doesn't call again. Neither version of the sum captures that, because a job that never happened is hard to price honestly in euros.
What the alternative would have looked like
The alternative isn't dropping AI, it's adding one step back in: the assistant transcribes and proposes a slot, someone in the office confirms it before it lands in the calendar. That's roughly the logic behind the piece on resource booking with Google Calendar, written about workshop equipment rather than customer appointments, but the principle of approval before final booking carries over. The same logic applies to drafting text: the article on setting up ChatGPT for free to write emails deliberately treats it as a draft a person reads before sending, not an autopilot.
For businesses with a small number of high-value jobs, custom installations, larger renovation work, fully automated phone booking rarely pays off. The minutes saved on the phone weigh less than one customer lost over a wrong appointment. With high, fairly uniform call volume and mostly standard bookings, the math looks different, but even there, human confirmation is what separates saved time from extra work.
Anyone currently checking where technology at a customer touchpoint causes more errors than time savings might as well look at their own website too. The free website check from Log-System Development measures things like load speed and basic SEO and shows within minutes where a site is more likely to turn inquiries away than bring them in. For businesses that go on to consider a new website, a targeted AI integration or an app, Log-System Development builds it directly with its developers, without routing the project through an agency first.