Set up an AI receptionist that books real appointments

Before you touch a tool, read the other guide

This one is the build, not the decision. If you haven't already worked out whether an AI receptionist is worth it for your call volume, and whether missed-call text-back alone would cover you, start with the guide on AI receptionist basics at /guides/ai-receptionist-basics. Come back here once you've decided a voice agent is the right move and you're ready to set it up.

Budget 30 focused minutes for the account setup and script writing, plus a few days of watching transcripts before you trust it with a full week unsupervised.

Pick a tool based on what it connects to, not the demo

Every AI receptionist demo sounds good. The difference that actually matters is whether it plugs into the calendar and phone system you already run, so skip the sales pitch and check three things: does it integrate with your calendar or field service software directly, does it forward true emergencies to a real phone number, and does it text you a transcript after every call.

For small operators on Google Calendar or a simple scheduler, look at Goodcall, Rosie, or Smith.ai (which pairs the AI with human backup agents for a higher fee). If you already run Housecall Pro or Jobber, check their built-in AI answering add-on first, since it writes straight to the schedule your crew already uses.

Pricing moves fast enough that any number here is stale by the time you read it, but as of mid-2026 expect somewhere around $30 to $150 a month for a standalone tool, usually with a free trial or a money-back window. Sign up for the trial on two tools and run the same test call through both before committing to either.

Wire it to your calendar the right way

The setup screen for most tools asks you to connect a calendar (usually Google Calendar) or a field service app account. Do this before you write a single word of script, because the booking rules you write depend on what the calendar actually looks like.

Set job-type durations first: a diagnostic visit might be 30 minutes, a full install 3 hours. If every job type defaults to a 1 hour slot, the AI will double-book your afternoon without knowing it. Add buffer time between jobs, 15 to 30 minutes is typical, so a job that runs long doesn't collide with the next one.

Block off the calendar for days you're out, and turn on double-booking protection if the tool offers it. Then have the AI check the same calendar your crew uses live, not a separate booking calendar that somebody has to reconcile by hand at the end of the day. A second calendar is where jobs get lost.

Write the greeting and the instructions box

Most tools split this into a greeting (the first thing callers hear) and an instructions box (the plain-English brief that steers everything after). Keep the greeting short and honest about what it is.

• Greeting, copy and adapt: "Thanks for calling Badger Plumbing. I'm an AI assistant, I can book you an appointment or take a message. If this is an emergency, say emergency now and I'll connect you to a person."
• Business basics in the instructions box: name, cities served, hours, licensed-and-insured line.
• Services offered in plain words, and what you don't do, so it can decline politely instead of guessing.
• The only price it's allowed to say out loud (your service call or diagnostic fee), with a hard rule that anything else gets "pricing depends on the job, let's book you an estimate."
• A clear emergency list (burst pipe, no heat below freezing, a sparking panel) and what to do about each: transfer live, or grab the first morning slot.
• The fallback: if it's unsure, take a name, callback number, and one line about the problem, then promise someone will call back within a set window you actually keep.

Set the escalation rule before you set anything else

The single most important setting in the whole build is what makes it stop talking and hand off to a person. Get this wrong and either every call gets kicked to your cell phone (defeating the point) or a real emergency sits in a voicemail queue while a basement fills with water.

Give it a short, specific trigger list, not a vague "if it sounds urgent" instruction. Name the actual words and situations: active flooding, no heat with a baby or elderly person in the house, gas smell, sparking or smoke. Anything on that list transfers live to a number that rings through immediately, not a message that waits for business hours.

For everything else, let it book normally or take a message. If you're worried about missing the transfer call because you're on a job, forward that emergency line to a second person, a partner, dispatcher, or on-call tech, not just your own phone.

Attack-test it before a real customer does

Call the number yourself from a different phone and try to break it. Mumble. Talk over it. Ask for a full repipe quote on the spot. Describe a fake emergency at panic speed and see if it actually transfers. Have someone else try too, since you'll unconsciously go easy on your own setup.

Every place it fumbles is a line you add back into the instructions box, usually two or three passes before it holds up. Once it's live, forward only the calls you don't personally answer (conditional call forwarding, covered in the basics guide) and read every transcript for the first two weeks. That's where you catch the questions customers actually ask that never made it into the script.

If you're already running text-based follow-up, see the guide on quote follow-up systems at /guides/quote-follow-up-system for how to chain a booked estimate into the follow-up sequence so a booked call doesn't go cold after the appointment.