What Is an AI Receptionist and How Does It Handle Bookings?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for What Is an AI Receptionist and How Does It Handle Bookings?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for What Is an AI Receptionist and How Does It Handle Bookings?

An AI receptionist is software that answers your phone in a natural-sounding voice, works out what the caller wants, and acts on it. For bookings, it checks your diary, offers free slots, books, moves or cancels the appointment and texts a confirmation. That only works when it is connected to your booking system; otherwise it just takes messages.

That last point catches many owners out. "Handles bookings" can mean the AI writes the appointment straight into your diary, or that it sends your staff a request to confirm, or merely that it notes the caller's name and preferred time. Vendors use the same phrase for all three, and the gap between them is the gap between saving hours and creating a new inbox to clear.

Follow me on Instagram@sagnikteaches

What happens inside a booking call

Here is the sequence when someone rings an osteopathy clinic and asks for an appointment, with an AI receptionist connected to the clinic's practice software.

Connect on LinkedInSagnik Bhattacharya
  1. The call arrives. Either the clinic's number forwards to the AI (all the time, after a few rings, or only out of hours), or the AI vendor supplies a new number.
  2. Speech becomes text. The caller's words are transcribed in real time. Accents, background noise and poor mobile signal all affect accuracy here.
  3. A language model works out the intent. "I hurt my back lifting a box on Saturday and wondered if anyone could see me this week" becomes: new patient, wants an initial consultation, this week, back pain.
  4. The AI asks your booking system for availability. This is a direct request to the practice software through its API (the connection that lets one program ask another for data). It asks: which initial-consultation slots are free this week, with which practitioners?
  5. It offers a choice. "I can offer Wednesday at 10:15 with one of our osteopaths, or Thursday at 4:30. Would either suit you?" Good systems offer two or three options rather than reading out a list.
  6. It collects the details your rules require. Name, date of birth, mobile number, email, and perhaps how they heard about you.
  7. It writes the booking. A second request to the practice software creates the appointment in the right slot, with the right appointment type and length.
  8. It confirms. The caller hears the details read back, then gets a text or email confirmation, often with a link to the clinic's new-patient form.
  9. Your team gets a record. A call summary and often a recording or transcript land in your inbox, practice software or a dashboard.

Steps 4 and 7 are the whole difference between a booking assistant and an expensive answerphone. If the vendor cannot read and write your diary, the AI has to stop at step 3 and promise that someone will call back.

Subscribe on YouTube@codingliquids

Here is what a short reschedule call might sound like, as an illustrative transcript:

AI:     Good afternoon, you're through to the clinic. I'm the
        clinic's AI assistant; I can book or move appointments,
        or take a message for the team. How can I help?
Caller: I've got an appointment Thursday at half four, can I move
        it to next week? Same sort of time.
AI:     Of course. Can I take your name and date of birth?
Caller: [gives name and date of birth]
AI:     Thank you. I can see your follow-up on Thursday at 4:30
        with your usual osteopath. Next week she has Tuesday at
        4:15 or Thursday at 5:00. Which would you prefer?
Caller: Tuesday's fine.
AI:     Done. You're booked for Tuesday the 21st at 4:15, and
        Thursday's appointment is cancelled. I'll text you the
        details now. Anything else?

That call went well because the AI found the existing booking, kept the patient with the same practitioner and offered times close to what was asked. The one thing I'd change: it never mentioned that Thursday's cancellation was within 24 hours of the slot. If the clinic charges for late changes, the rules must tell the AI to say so before confirming, not leave the receptionist to raise it later.

The read-back at the end of that call is the safety net for step 2, and it's worth insisting on the exact form. Speech recognition confuses "thirteenth" and "thirtieth" easily, especially on a poor mobile line. An AI that confirms "You're booked for the 30th" gives the caller nothing to catch; one that confirms "Tuesday the 30th, at 4:15" does, because a caller who asked for Monday the 13th will notice the wrong day name. Put it in the rules: always read back the day name, the date, the time and the practitioner, and wait for a yes before writing the booking.

A second edge case: the caller isn't the patient. A daughter rings to book for her father, or a parent books two children back to back. An AI that takes "the caller's details" creates the appointment under the daughter's name and texts her the new-patient form. Add one question near the start of every booking flow, "Is the appointment for you or for someone else?", and a rule that the booking, the form and the reminders go under the patient's name, with the caller noted as the contact if the patient agrees.

Three things "handles bookings" can mean

LevelWhat the caller getsWhat your staff still doMain risk
Direct booking: reads and writes your live diaryA confirmed appointment before they hang upReview the day's AI bookings; handle exceptionsWrong appointment type or practitioner if your rules are vague
Booking request: sees availability but staff confirm"We'll text you to confirm shortly"Approve each request, ideally within the hourSlot taken by someone else before staff approve; callers who wanted certainty
Message taking: no diary access"Someone will call you back"Call everyone backYou have only moved the work, not removed it

The middle row fails in a specific, predictable way. Say the AI offers Wednesday at 10:15, the caller accepts, and the request waits in the inbox until the receptionist gets to it at lunchtime. Meanwhile a patient books that slot online. The caller then receives: "Sorry, that appointment is no longer available. Please call us to rebook." They were told they had a slot, and now they have a chore. If you're on request-only, set a rule that requests are approved within the hour during opening times, and have the AI's closing line say "the team will confirm by text within the hour" rather than "you're booked".

For clinics, the connection depends on the practice software. Cliniko, used by many osteopaths and podiatrists, runs a directory of connected apps, and several AI receptionists listed there (Lyngo and Aeva among them) say they read the live calendar and book directly into it. If your software has no such integration, the vendor may offer a workaround through calendar sync, which is less reliable when practitioners have complex rules about appointment types.

What a good human receptionist does that the AI should not

A clinic receptionist does more than fill slots. They notice when a caller sounds distressed, they know which practitioner a regular prefers, and they recognise when "my foot's been bad for a week" needs same-day attention. An AI receptionist can handle some of that if you write it down, and should hand over the rest.

  • Clinical questions. "Is it safe to have treatment while pregnant?" or "Should I keep walking on it?" are for the practitioner. The AI should say so and offer a call-back.
  • Red-flag symptoms. Each practitioner should write a short list of phrases that mean "transfer immediately" or "tell the caller to seek urgent medical help". For a podiatry clinic, a diabetic patient describing a new wound or colour change in the foot might be on it. The AI does not diagnose; it recognises the words you have listed and follows your instruction.
  • Complaints and billing disputes. These go to a named person, not into a booking flow.
  • Callers who ask for a person. Always honour it, straight away.

Writing those rules is the real setup work. How to write call scripts and escalation rules for an AI receptionist covers the wording in detail.

An illustrative week at a two-practitioner osteopathy clinic

Numbers make this concrete. Consider a clinic with two osteopaths, a part-time receptionist in the mornings, and the phone ringing about 140 times a week. Before any AI, a typical week looks like this:

  • About 85 calls are about bookings: new patients, follow-ups, reschedules, cancellations.
  • About 30 go unanswered, mostly in the afternoons and during treatments, when the osteopaths cannot pick up.
  • Voicemails get returned between patients or after the last appointment, and perhaps a third of new-patient callers have booked elsewhere by then.

With a direct-booking AI receptionist answering whenever the front desk is busy or closed, suppose it takes 70 calls a week. Of those, it completes 45 bookings, moves or cancellations on its own, sends 10 to staff as requests because they fall outside its rules (a patient wanting a double appointment, a caller asking about insurance billing), transfers 5 to a practitioner, and takes 10 messages about other things.

The receptionist now spends 20 minutes each morning reviewing the previous afternoon's AI bookings and handling the 10 requests, instead of an hour returning voicemails. The osteopaths stop answering the phone between patients. Whether it pays depends on the plan's price and on how many of those 30 unanswered calls were new patients; what an AI receptionist costs a small business sets out the pricing models to compare.

The same week also shows the failure modes. One caller asked for "the lady osteopath" and was booked with whoever was free. One follow-up was booked as a 30-minute slot when that patient always has 45. Both were caught in the morning review, which is why that review exists.

The review is quicker with a fixed format. An illustrative sheet for one morning, taken from the AI's call log:

Booked by AIType bookedCheckAction
Tue 14:10, new patient, lower backInitial consultation, 45 minCorrectNone
Tue 15:40, follow-up, moved from ThuFollow-up, 30 minNotes say double follow-upExtend to 45 min, text patient
Tue 17:05, cancellation, under 24 hoursCancelledPolicy read out? Yes, per transcriptApply fee as per policy
Tue 19:30, new patient, wants "the lady osteopath"Initial consultation with first free practitionerPreference ignoredRebook, apologise, add rule
Tue 20:15, request: insurance billing questionRequest to staffCorrect handoverCall back by 10:00

Two actions out of five in the first week is normal; the number should shrink as the rules improve. If it doesn't fall after three or four weeks, the rules are too vague or the vendor isn't applying them, and either way you've learned it from a sheet rather than from an angry patient.

One mistake the review can't catch in advance comes from holidays kept in the wrong place. Suppose one osteopath blocks her week off in her personal calendar but not in the practice software. The AI sees an open diary and books four patients into it. The first sign is a patient arriving for an appointment with nobody there to treat them. The rule is simple: the practice software is the only diary the AI trusts, so holidays, training days and lunch breaks must be blocked there, and a new staff member's first task is learning that.

The booking rules you need to write down first

An AI receptionist is only as good as the rules it is given. Most clinics carry these rules in the receptionist's head. Before any trial, write them out like this:

BOOKING RULES FOR THE AI RECEPTIONIST
Appointment types:
- New patient initial consultation: 45 min. Any practitioner
  unless the caller asks for a specific one.
- Follow-up: 30 min. Book with the patient's usual practitioner
  if possible; if not free within 7 days, offer the other.
- Double follow-up (45 min): only if the patient's notes say so.
  Otherwise send as a request to staff.
Held-back slots: never book Monday 8:00 or Friday 12:30
  (kept for urgent cases). Staff release these.
Cancellations: allowed any time. If under 24 hours' notice,
  read the cancellation policy and note it on the booking.
Deposits: new patients booking online pay a deposit via the
  confirmation link. Tell callers this before confirming.
Always transfer or call back: clinical questions, anything on
  the red-flag list, complaints, invoices, insurance queries.
If unsure: take a request, don't guess.

A podiatry clinic's rules read differently, because some of its appointments cannot be booked cold. A filled-in excerpt might say:

- Routine nail and skin care: 30 min. Any podiatrist.
- New biomechanical or gait assessment: 60 min. Only with the
  two podiatrists who do them. Ask the caller to bring the
  shoes they wear most.
- Nail surgery: NEVER book directly. It needs an assessment
  first. Offer an assessment appointment, or take a request.
- Home visits: request only. Staff check the route and day.
- Diabetic foot check: 30 min. If the caller mentions a new
  wound, redness, swelling or colour change, follow the
  red-flag instruction instead of booking.

This document is useful even if you never buy an AI receptionist. It is also the thing most vendors will ask for in the first week, so having it ready shortens setup.

Misconceptions worth clearing up

"It's just a fancy phone menu." Press-one-for-bookings menus route calls. An AI receptionist holds a conversation, understands a sentence like "can I move Thursday to next week, same time?" and acts on it. It is closer to a trained temp than a switchboard.

"It knows my diary once I sign up." Only if it is integrated with your booking system and the connection has been tested. Many trials disappoint because the AI was set up in message-only mode without the owner realising.

"Callers will hate talking to a machine." Some will, and they should reach a person quickly. Many callers mainly want to be answered and booked on the first ring, especially out of hours. The answer is in your own call reviews, not in general opinion.

"Once it's set up, it runs itself." Appointment types change, practitioners go on holiday, prices rise. Each change must reach the AI's rules the same day, or it will keep booking the old way.

"The vendor handles the legal side." You remain responsible for how callers' personal and health details are handled. Check where recordings and transcripts are stored and for how long, whether call recording needs announcing where you operate, and whether the vendor signs a data-processing agreement. If you serve customers in the EU, the AI Act's transparency rules mean callers must be told they are speaking to an AI; a short opening line does it.

Questions that tell you whether one will work for you

  1. Does it integrate with my specific booking or practice software, and can it write appointments as well as read availability?
  2. Can it follow different rules for different appointment types and practitioners?
  3. How does it transfer a live call to a person, and what happens if nobody answers the transfer?
  4. Where do call summaries go, and can my team see every AI booking in one list each morning?
  5. Can I change the rules myself, today, without a support ticket?
  6. What does a trial look like on my real number, forwarding only when we don't answer?

If the answers to the first two are yes, a direct-booking trial is worth running. If they are no, compare it honestly with an answering service or a hybrid: some services, Smith.ai among them, combine AI with live human receptionists. AI receptionist or answering service for a booking-based business walks through that choice, and when you are ready to configure one, how to set up an AI receptionist without losing callers covers the rollout. When it does get a booking wrong, as every system eventually will, what to do when an AI receptionist gets a booking wrong has the recovery steps.

Further reads

Sources: Cliniko connected-apps directory (AI receptionist listings), vendor pages for Lyngo, Aeva AI and Smith.ai, EU AI Act Article 50 transparency duties.

Not sure which calls an AI receptionist should take?

On a 1:1 call we'll go through a typical week of your calls, check whether your booking system lets an AI write appointments directly, and decide which calls it takes and which must reach a person.

Book a 1:1 call with me