Skip to content

How to Set Up an AI Receptionist for a Small Business (Step by Step)

The full build sequence, in the order that avoids the hang-up-inducing mistakes: script first, conditional forwarding, calendar constraints, handoff rules, and the ten-call gauntlet before launch.

August 1, 202610 min readShift The Culture

You can stand up a working AI receptionist — one that answers when you can't, captures the caller's details, and books real appointments — in a day, for $0–50/month in parts. This is the full sequence, vendor-neutral, in the order that avoids the mistakes that make callers hang up.

A quick scope note before step one: most guides for this query are written by receptionist vendors, so every “step” bends toward their signup page. We sell a written setup guide, not a receptionist service — so we have no reason to push you toward any platform. If you've already decided whetherto do this and just want the how, keep reading. If you're still on the fence, start with our honest breakdown of whether AI receptionists work and come back.

Step 0 — Decide what it will NOT do

Every bad AI receptionist we've seen failed at the scoping step, before any tool was chosen. A receptionist has exactly three jobs: answer the call, capture who it was and what they need, and booka slot if your calendar allows it. That's it. It does not quote complex jobs, troubleshoot, negotiate, or calm down an angry customer. Write those exclusions down now, because every platform will tempt you to switch on more.

The receptionist that tries to do everything does nothing well enough to keep a caller on the line.

Step 1 — Write the script on paper before touching any tool

The script is the product. The platform is plumbing. Three pieces, in this order:

The opening line.Disclose that it's automated, immediately, and pair the disclosure with the benefit. The version we recommend:

Opening line — copy and adapt
"Thanks for calling [business]. I'm the automated assistant — I can book
you in right now, or take a message and a human will call you back.
What do you need today?"

Do not skip the disclosure. A caller who realizes mid-call that they were tricked into talking to a bot doesn't just hang up — they stop trusting the business. Callers who are told upfront mostly just want their problem handled. (In some U.S. states, call recording also requires consent from everyone on the line — if your platform records calls, say so in the greeting and check your state's rule. Two minutes of reading now saves real trouble later.)

The intake questions. Five, maximum — more and callers bail:

  1. Name.
  2. Best number to reach you (confirm the one they called from).
  3. What do you need done? (free text — let them talk)
  4. Where? (only if your work is at the customer's location)
  5. When do you need it — is this urgent?

The escape hatch.One sentence, available at every turn: “If you'd rather leave a message for a human, just say so and I'll pass it along.” The 10% of calls that don't fit the script become polite messages instead of furious hang-ups.

Step 2 — Pick your stack (two honest routes)

There are two ways to run this, and the right one depends on how much control you want, not on which vendor shouts loudest:

  • Route A — an all-in-one AI receptionist service.You pick a persona, paste your business details, connect a calendar, and you're live in an afternoon. Typical cost: $20–100/month. Trade-off: you rent the script, and switching later means re-doing setup.
  • Route B — assemble it from parts. A voice-AI platform, a phone number, and a calendar connection. More setup (a day, not an afternoon), usually cheaper at low call volume because you pay per minute of actual talk time, and the script is fully yours.

Whichever route, judge candidates on the same five things — ignore everything else on the pricing page:

  • Latency. Call the demo line. If replies lag a beat too long, callers talk over it and the call falls apart.
  • Interruption handling. Talk over the demo mid-sentence. It should stop and listen, not bulldoze on.
  • Real calendar booking — writes to your actual calendar, not a lead form pretending to be one.
  • Instant summaries — a text/email to you after every call with name, number, need, and outcome.
  • A human-transfer or message path you control — the escape hatch has to be wireable, not aspirational.

Step 3 — The phone-number move most guides skip

You do not need to change your business number, and you shouldn't start by routing every call to the AI. The low-risk setup is conditional call forwarding: your number rings you first, exactly as it does today, and forwards to the AI receptionist's number only when you're busy or don't pick up. Every mobile carrier supports this — it's usually a short dial code (often *004*or a carrier setting called “call forwarding when unanswered/busy”).

This one decision de-risks the whole project. The AI only ever gets the calls that were going to voicemail anyway — which voicemail converts to almost nothing. The floor is where you are today; the upside is every after-hours and both-hands-full call you currently lose.

Step 4 — Connect the calendar, then constrain it

Connecting Google or Outlook is the easy part; every serious platform does it. The part that prevents chaos is the constraints, and they're yours to set:

  • Define bookable job types with fixed durations — “estimate visit, 30 min” — never open-ended slots.
  • Add buffer time between bookings (drive time, cleanup — whatever your trade needs).
  • Set a same-day cutoff. An AI that books a 4pm job at 3:45pm while you're on a roof is a liability, not a feature.
  • Anything complex or expensive → the AI captures details and marks it “needs human callback” instead of booking.

Step 5 — Write the handoff rules

Decide, in writing, when the AI must stop being helpful and start being a message-taker:

  • Urgency keywords (“flooding”, “no heat”, “locked out” — your trade's versions) → text you immediately, don't book a Tuesday slot.
  • Frustration — caller repeats themselves twice or asks for a person → apologize once, take the message, end warmly.
  • Price questions beyond a flat rate → “that one needs the owner — I'll have them call you” is a fine answer. A confidently wrong quote is not.

Step 6 — The ten-call gauntlet

Before a real customer ever hits it, call your own line ten times and try to break it:

  1. The ideal call — book a standard job start to finish.
  2. Mumble the name and street. Does it confirm spellings instead of guessing?
  3. Interrupt it mid-sentence. Does it stop and listen?
  4. Ask what it costs. Does it stay inside the pricing you gave it?
  5. Ask for a human immediately. Count the seconds before it yields.
  6. Present an emergency. Does the urgent path actually fire — did you get the text?
  7. Ask something outside your services. Does it decline gracefully or improvise a yes?
  8. Go silent for ten seconds. Does it prompt gently or hang up?
  9. Try to double-book a taken slot. Does the calendar constraint hold?
  10. Be mildly rude. Does it stay even and route to a message?

Fix what broke, run the gauntlet again, and only then point real traffic at it.

Step 7 — Launch after-hours first, then widen

Week one: forward to the AI only outside business hours — pure upside, since those calls were hitting voicemail. Read every transcript daily; each awkward exchange is a free script edit. Week two, if the transcripts look clean: add busy/no-answer forwarding during the day. Most small operations should stop there — you answering when you can, the AI catching what you miss, is the configuration that makes callers happiest.

What it actually costs

  • Dedicated number for the AI: $1–5/month.
  • Voice-AI usage: typically $0.05–0.30 per talk-minute on parts-built routes — low call volume lands at $10–30/month.
  • All-in-one services: commonly $20–100/month flat.
  • Calendar connection: free with the calendar you already have.

Compare against a human answering service at $200–1,000/month — or against the value of one job a month you currently lose to voicemail. For the fuller budget picture across every intake channel (not just phone), see the cheapest way to automate customer intake.

The bottom line

Script first, tools second. Disclose the bot. Forward conditionally so the AI only catches what voicemail was losing. Constrain the calendar, write the handoff rules, run the ten-call gauntlet, launch after-hours first. Do it in that order and the “AI receptionist horror story” failure modes — deception, over-reach, no exit — never get a chance to happen. If you want the long-form version with the platform-level details filled in, the AI Receptionist Setup Guide ($67) is exactly that, and nothing more.

SharePost on X
Free · 13 pages · no upsell inside

Get the Operator Field Kit — free

Six production prompts, the five-step operator setup, and nine rules from our own failure log.

  • 6 complete prompts — printed in full, not previews
  • The five-step setup, each step with a pass/fail test
  • 9 rules from the failure log that produced them

The kit, then the occasional operator note. One click unsubscribes and we never sell the address.

Keep reading