The customer who fired a contractor over a bot: what "never stuck with a bot" has to mean

At 19:30 UTC on 23 March 2026, a Hacker News user called CodingJeebus posted a warning under a thread titled "I built an AI receptionist for a mechanic shop." He had a quote from a reputable plumber for a home remodel. When he called to book, an AI receptionist could not understand his address. "And it couldn't forward to me to human." He hired someone else.¹

"Never stuck with a bot" has to mean something checkable. The bot stops. The owner gets the whole conversation in one message. The customer hears who will reply and by when, and gets an update if that time slips. Anything less is a trap.

What happened when a customer could not reach a human?#

The plumber's customer told the story himself, about six months after it happened. He was mid-remodel. He had already chosen the plumber and wanted to schedule the rough-in. The receptionist that answered was an AI.

It "got confused during the scheduling flow and could not understand my address, asking me to repeat it over and over." There was no exit from the loop. Then he wrote the line that turns a support glitch into a lost job: "If I'm paying you tens of thousands of dollars for remodeling work, I damn well better be able to get in touch with you. I found a different contractor and never looked back."¹

Look at it from the plumber's side. A call came in and ended. Maybe a log showed a failed booking. Nothing on any screen said a remodel had just walked out the door.

The pattern repeated in August 2026 on the Jobber community forum, where home-service owners were debating AI receptionists. A customer named matt_kaleafirm described trying to hire a cleaner: "I reached out to four smaller companies. All four of them used AI in some form for the intake." Then: "I heard back from one company 5 weeks later and didn't hear back from the rest of the companies."²

In September 2026 the same story arrived from inside a contractor's family. A thread in r/PickAorB titled "Our HVAC company lost a big job after we switched to an AI receptionist. Do I push my brother to bring back a human?" drew more than 1,300 comments. One line in Google's snippet of the thread said the writer would be "happier to reach the contractor's voicemail than to reach an AI receptionist."³ The question in the title was a rollback: undo the change, put a person back on the phone.

The same month, a founder in r/micro_saas posted "We lost 56 customers after I tried to save money with AI" (240+ comments). One line in Google's snippet of the thread was blunt: "escalate to a human when it detects the AI is stuck on a loop."⁴

Why do AI-to-human handoffs fail so often?#

AI-to-human handoffs fail more often than the AI's own answers do, and the best measurement comes from car dealerships. Pied Piper's 2025 Service Telephone study called 2,105 dealerships across 26 large US dealer groups plus 200 independent service centers. When the AI could not handle a request and passed it to a person, "those handoffs failed 56% of the time."⁵

The same study scored AI calls that went start to finish at 72. Calls transferred from AI to a human scored 50. Pied Piper's Cameron O'Hagan put it this way: "AI now often outperforms human staff on service calls, but handoffs to people frequently fall apart."⁵

Written support shows the same break. Gorgias analysed its merchants' AI Agent tickets from October 2025 to April 2026, in accounts with 200 or more AI-touched tickets.⁶

Sources: Auto Remarketing on Pied Piper (7 July 2025);⁵ Gorgias Ecom Lab platform data.⁶

The public cases show five distinct ways a handoff breaks. Each needs its own fix.

The bot does not notice it is stuck#

A bot that cannot tell it is stuck keeps asking the same question. The plumber's receptionist asked for the address "over and over."¹ The r/micro_saas fix, detect the loop and escalate, exists because the default is to keep trying.⁴

The handoff lands in a queue nobody watches#

A handoff that lands in an exception queue with no owner is a dead end with a label on it. Gorgias's 33% never-answered share is that queue, measured.⁶ The cleaning customer's five-week wait is what it feels like from outside.²

The context does not travel#

A handoff without context makes the customer start again. Meta's Business Agent documentation, published by 360dialog, states: "On hand-back, the agent loses earlier conversation context."⁷ A 2026 California Management Review article lists passing the transcript and history to the human, so the customer need not restart, among its best practices.⁸

The bot goes silent#

A bot that stops talking after handing off leaves the customer with no signal at all. The same 360dialog page states: "Once the agent hands off to a human, it stops answering that chat," and the handoff notice is "the fixed message you define."⁷ If no person picks it up, the customer hears nothing.

The promise is vague or too slow#

A vague callback promise can lose the highest-value inquiry of the month. Lilach Bullock reported a small test for a five-person events-staffing client in Manchester: when a caller asked the AI to match a £3,900 competitor quote, it offered a callback "within 2 business days" instead of flagging the request. She estimated the lost booking at about £4,200.⁹ It is one practitioner's test with seven calls, but the failure is easy to recognise.

Do customers hate AI, or do they hate being trapped?#

Customers' objection to AI service is mostly an objection to being trapped by it. Five9's March 2025 survey of 1,006 consumers in the US, UK and Canada found "72% of consumers are open to AI-powered interactions, provided they can escalate to a human when needed." The same survey found 40% will stop doing business with a company after one bad experience.¹⁰

The other side of that condition is harsher. The California Management Review piece, citing Gartner, reports that 64% of customers would prefer companies not use AI for service and 53% would switch to a competitor over it.⁸ A September 2026 thread in r/customerexperience summed up the gap in its title: "Customers don't hate AI support. They hate being trapped."¹¹

For a small business the arithmetic is short. One remodel, one cleaning contract, one HVAC install. The customers in these cases did not wait for the business to fix it. They left, and told strangers online.

What does "never stuck with a bot" have to mean?#

"Never stuck with a bot" is a promise a business can test, made of five conditions. If any one fails, a customer can get stuck.

1. One plain request reaches a person. "Can I talk to a person?" works on the first try, at any point, with no menu and no second attempt.
2. The bot stops on that topic. After handing off, it does not keep guessing about the question. It also does not go silent: it tells the customer what happens next.
3. The person gets the full context in one message. Who the customer is, what they asked, what the bot already said, and anything it promised.
4. The customer gets a named reply-by time. A role or name and a clock time in the customer's time zone, such as "Sam will reply by 17:00 today." Never "someone will be in touch."
5. A missed time triggers an update. If the reply-by time passes, the owner is reminded and the customer hears a new time. Nobody waits five weeks in silence.

Notice what the list leaves out. It does not require a phone transfer or an instant reply. A written reply by 17:00 that arrives at 16:40 keeps the promise. A live transfer that rings out breaks it.

Some platforms now ship a switch for this. Google's pilot AI agent in Business Profile messages has a "Customer handoff" setting that notifies the owner when the AI passes a conversation on.¹² A notification covers condition three at best. The other four are still the business's job. More on that pilot in Google Business Profile's AI agent.

The handoff contract: a template you can copy#

The handoff contract is a one-page agreement between a business and its AI assistant about when it stops, who takes over, and what the customer is told. Fill it in before the assistant answers its first customer.

Handoff message (assistant to customer)
"I'm [Business]'s AI assistant. Your question about [topic] needs [Name/role], so I've passed them our full conversation. They'll reply by [time, day] ([time zone]). I won't guess on this in the meantime. If you need anything else, such as availability or opening hours, I can help with that now."

Update if the time slips
"Quick update: [Name] hasn't replied yet and I didn't want you waiting without word. You'll hear by [new time]. Sorry for the delay."

Context packet (assistant to owner)
"[Customer name, contact] asked: '[their words]'. I said: [summary]. I promised: [anything held or offered]. Handed off because: [trigger]. Customer told: reply by [time]. Reply options: [1] [2] [3] [write my own]"

How to test whether your own bot traps customers#

A handoff test takes about fifteen minutes, and it is worth running on your own assistant and on two competitors'. Use a phone and an email address the business does not recognise.

1. Ask for a person first. Open with "Can I talk to a person?" Note whether you get a name, a time, or a loop.
2. Ask a money question. Ask for a discount or a price match. A pass is a handoff, not an invented number.
3. Give a hard detail. Spell an unusual street name or give an apartment number. Count how many tries the assistant takes before it hands off.
4. Try after hours. Ask at 21:00 on a weekday. Note the reply-by time it gives you.
5. Time the human. Record when a person actually replies, and whether they already knew what you asked.
6. Check the owner's side. On your own setup, look at what arrived for you. Could you reply without opening the transcript?

Valet has not published results from a test like this at scale. The method is here so you can see your own setup the way the plumber's customer saw his.

What the evidence does and does not show#

The handoff evidence is strong on failure and thin on fixes. Pied Piper measured dealership phone calls. Gorgias measured e-commerce tickets. The Hacker News, Jobber and Reddit cases are individual accounts, and the Reddit snippets are short fragments of long threads.¹²³⁵⁶

No public study yet measures what a small business gains by adopting a handoff contract. Gorgias's own conclusion runs the other way, toward fewer handoffs: "The only exit is fewer handoffs."⁶ Both can be true. Fewer handoffs is a goal; a kept promise on the ones that remain is the floor. For how vendors count a "resolution" when a handoff is involved, see what counts as an AI resolution. For where a founder should start, see should a startup use AI for customer support.

Where Valet fits#

Valet answers written inquiries (email, website forms, listing leads) for a small business, not phone calls. Each topic runs on one of three rules: Autopilot, Ask me first, or Always you. Money questions, complaints, contracts, deposits and health, legal or safety questions go to the owner with one-tap replies, and the customer is told when the owner will reply. Every reply is signed as the business's AI assistant, and the Valet receipt records what was asked, the rule used and the sources. A handed-off inquiry keeps its place in the Valet Inquiry States until it is booked or closed with a reason. The free lead check looks at 10 to 20 recent inquiries and shows which ones went unanswered or stalled. If your form is the leak, start with the contact-form test.