AI receptionist for home service businesses:
it answers every call and books the job.
And you can check that it booked it right.
Ihor Odariuk audits, tests and monitors AI receptionists for home service companies such as appliance repair, HVAC and plumbing: a voice agent that answers the phone, qualifies the caller, reads the technician schedule and books the visit, with a handoff to your team when a person is needed.
An AI receptionist (also sold as an AI answering service) answers your business line around the clock, finds out what the customer needs, checks technician availability and books the appointment into your calendar. The hard part is not the voice. It is making sure the agent reads your schedule and CRM correctly on every call, because when it is wrong, it is wrong quietly: every call is logged as a success while jobs land on technicians who are off.
What a working AI receptionist does on one call
The agent I audited and migrated answers the phone and books repair appointments for a home service company on five phone numbers. It runs on Retell AI with an ElevenLabs voice on top of a large language model, and it handles a few hundred calls a month. Behind the voice it has 15 conversation states and 16 custom tools, from reading the technician calendar to calling back customers.
Those tools are what separates a receptionist from a voicemail with a nicer voice. Every one of those tools touches your real data, and every one of them can fail without an error message.
Three failures from a live agent that no demo would have shown
- It booked jobs on technicians who were off. The scheduling system held 7,801 calendar events. The agent only ever read the 600 most recently touched ones, so older time-off blocks were invisible. Every run was logged as a success. At launch there were fewer than 600 events, so the bug did not exist yet. The full story of the 600 of 7,801 bug.
- The voice turned into gibberish. The transcript was clean English. The cause was one dash in the agent's text, which the voice engine turned into 3.4 seconds of garbled sound. It showed up in the word timings, not in the transcript. How one dash broke the voice.
- The phone bot went down at 3 AM. The automation database behind it filled its 5 GB disk with saved run history. Downtime was about 20 minutes, and the settings that prevent it are a few lines. What filled the disk.
None of these looked like a broken bot from the outside. Calls connected, the voice sounded fine, the dashboard showed green. That is why an AI receptionist needs checks on what it outputs, not only on whether it is running.
How I set up and check an AI receptionist
When an AI receptionist is the wrong answer
If most of your calls are complaints, warranty disputes or long diagnostic conversations, a person will do better, and the agent should route those calls rather than try to handle them. If your calendar and CRM are not kept up to date by the team, the agent will book on bad data no matter how good the prompt is. Fixing the data comes first.
And if you only need to stop losing after-hours calls, start smaller: forward missed calls to a person or a simple answering service, measure how many calls you were actually missing, then decide whether full booking is worth building.
Common questions about AI receptionists.
It is a voice agent that picks up your business line, talks to the caller in plain speech, finds out what broke and where, checks which technician is free and books the visit into your calendar. When it cannot book, it hands the caller to your team with a short summary. A good one sounds like a calm dispatcher. A bad one books jobs on technicians who are off and nobody notices for weeks.
They overlap. An answering service takes a message and passes it on. An AI receptionist is supposed to finish the job on the call: qualify the customer, read the schedule and book the visit. That second part is where the money is and where most of the failures are, because it depends on the agent reading your calendar and CRM correctly on every call.
Some will, and that is fine if the call still ends with a booked visit. What gives a bot away is rarely the voice. It is long pauses, repeating the greeting, or a burst of noise where the text had a symbol the voice engine cannot read. In one live agent a single dash in the script produced 3.4 seconds of garbled sound that a tester described as a foreign language. Those are the things worth testing before launch.
No. I work on top of the platform you already have or choose, such as Retell AI with an ElevenLabs voice, plus your CRM and calendar. My part is the setup, the testing and the monitoring: the conversation flow, the calendar and booking logic, the handoff to your team, and the checks that catch silent failures.
Two separate costs. The platform charges per minute of calls, and that is paid to the platform directly. My work is a fixed project: an audit of an existing agent from $700, a new build from $1,800, both on the pricing page. I do not resell minutes and do not charge a percentage of call volume.
Yes, and it is usually the better start. The audit reads the real call recordings and word timings, compares what the agent booked with what the calendar actually allowed, checks the callback logic and the data retention behind it, and flags platform deadlines. Retell, for example, stops letting you create multi-prompt agents on December 15, 2026 and stops edits on February 1, 2027, so agents built that way need a migration plan.
Find out if your phone line is losing jobs.
Send me what you use today, a person, an answering service or a voice agent, and I will tell you where calls are lost and whether an AI receptionist would fix it.