AI Scheduling for Doctors: Appointment Types and Waitlist Rules

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Scheduling for Doctors: Appointment Types and Waitlist Rules.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Scheduling for Doctors: Appointment Types and Waitlist Rules.

To set up AI scheduling for a doctor's practice, define each appointment type with its length and buffer, set a capped overbooking rule only for slot types with stable no-show rates, and write waitlist fill rules that offer freed slots in a fixed order. Link the tool two-way to the EHR calendar, test for double bookings, and keep urgency decisions with staff.

The order matters. Most scheduling tools can be switched on in an afternoon, and most problems come from skipping the definitions: if "appointment" means the same twenty minutes for every visit, an AI will fill your day efficiently with the wrong lengths. The work is in the rules, which are a one-off job for the practice manager and a clinician, and the AI then applies them consistently.

Follow me on Instagram@sagnikteaches

Start with appointment types, not with the tool

List every kind of visit your practice offers, then give each a length, a buffer, who can book it, and which clinician or room it needs. Use the actual time your doctors take, taken from a week of calendar history, not the length the system defaults to.

Connect on LinkedInSagnik Bhattacharya
TypeLengthBuffer afterWho can self-bookNotes
New patient, full history40 min5 minYes, new patients onlyNeeds records-request form first
Routine follow-up15 min0 minYes, existing patientsOne issue only
Medication or results review10 min0 minYes, by phone or videoStaff confirm results are back
Long or complex visit30 min10 minNo, staff bookMultiple issues, or flagged by a doctor
Annual health check30 min5 minYesPre-visit form required
Procedure (minor)20 min plus room set-up10 minNo, staff bookNeeds treatment room
Telehealth15 min0 minYesVideo link sent automatically
Same-day (held slots)15 min0 minNo, offered by staff or the AI under the same-day ruleReleased at set times

All figures are illustrative; your clinicians set the real ones. Two columns catch most trouble. "Who can self-book" is the control: an AI that lets any patient book a complex visit as a 10-minute slot creates a late-running day. "Notes" holds the conditions: pre-visit forms, room needs, one issue per slot. The tool can only apply what is written down.

Subscribe on YouTube@sagnikteaches

To check the lengths are honest, pull a week of actual appointment start and end times from your EHR and compare each type's average against its scheduled length. If follow-ups scheduled at 15 minutes run at 19 on average, the AI will build a day that runs behind from 9:30 onwards. Adjust the length or split the type, for example "follow-up, one issue" and "follow-up, several issues".

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Patient-facing wording that routes people to the right type

Patients do not know your type names. Describe each in plain words and let them choose, with a short free-text reason that staff can see. Words matter here, because a patient picking from labels will often choose the shortest.

Which best describes your visit?
( ) I'm new to the practice - 40 minutes
( ) Follow-up on one health issue I've seen you about - 15 minutes
( ) Several issues, or I'd like a longer talk - 30 minutes
( ) Medication or test results review - 10 minutes, phone or video
( ) Annual health check - 30 minutes
In a few words, what is the visit about? [______]

If you think this is an emergency, call [emergency number] now.
This form does not tell the doctor how urgent your problem is.

The last two lines are important. They tell patients the form does not assess urgency, which sets expectations and reduces the risk of someone assuming it does. The free-text box gives staff a chance to reclassify: when the reason reads "chest tightness on exercise", a person, not the AI, decides what to do. The AI can be given a list of words that move a booking into a "staff review" queue, but the decision stays human. The chatbot scope and hand-over tutorial covers wording for a chat route.

Buffers and the day's shape

Buffers decide whether a clinic day runs to time. A five-minute gap after long visits lets a doctor write notes, so notes do not pile up at day's end. Instead of adding them to every slot, apply them where they matter: after new-patient visits, after complex visits and before procedures that need set-up.

Next, shape the day. A common arrangement is long visits early, when the doctor is fresh and the day has not run late, with short follow-ups after lunch. Another is to hold two same-day slots at the start of each session and release them to the general pool at a set time. The AI can enforce either, but only if you give it the rule: "never place a long visit after 3pm" or "release held slots at 10am, and at 2pm for the afternoon".

A worked sum. A doctor sees patients 9:00 to 12:30, 210 minutes. With a mix of seven 15-minute follow-ups (105 minutes), one 40-minute new patient (40 minutes), and two 10-minute reviews (20 minutes), that comes to 165 minutes. Add the 5-minute buffer after the new patient and two 15-minute same-day held slots (30 minutes): 200 minutes. The session is nearly full, with ten minutes spare; an eighth follow-up would push it five minutes over before anyone runs late. Doing this arithmetic in advance for a typical session is the quickest way to see whether the rules are realistic.

An overbooking rule that is capped and reviewed

Overbooking is the most contentious setting. Done carelessly, it produces waiting rooms of angry patients. Done carefully, it protects capacity against no-shows. A safe approach has five parts.

  1. Measure first. Calculate the no-show and late-cancel rate for each appointment type over the past three months. If you cannot, do not overbook yet.
  2. Apply only where the rate is high and stable. Illustratively, a 12 per cent no-show rate on routine follow-ups in the late afternoon, steady across months, is a candidate. A 3 per cent rate is not.
  3. Cap it. At most one extra booking per session, and never on long, complex or new-patient visits.
  4. Write the "everyone came" rule. Who sees the extra patient, how long they may wait, and what the front desk says. A fair rule: the overbooked patient is seen next free slot or offered a call back, with an apology, and the event is logged.
  5. Review monthly. Count how often the overbooked patient waited more than 20 minutes. If more than one session in four, remove the rule.

Say a late-afternoon session has 12 follow-up slots and a steady 12 per cent no-show rate, so on average about 1.4 patients fail to arrive each session. Book 13 instead of 12. If each patient's attendance is independent, the chance that all 13 turn up is 0.88 to the power of 13, about 0.19, so roughly one session in five the extra patient has to wait; in the other four, the overbook fills a slot that would have sat empty. Whether that trade is worth it is a decision for the doctors, not the software. Giving them the number is the AI's best contribution. The tutorial on reducing no-shows with AI reminders is the first alternative to try, since cutting no-shows is better than overbooking against them.

Waitlist rules that fill cancelled slots fairly

A waitlist turns cancellations into appointments rather than empty time. Without rules, it becomes whoever the front desk remembers. Write the rules as a short list the AI follows and staff can audit.

WAITLIST RULES (illustrative)
Who can join: any patient with a booked or requested visit of a type
  they may self-book, who has agreed to be messaged.
Order: by clinical priority flag set by staff, then by date joined.
Matching: a freed slot is offered only to patients waiting for that
  type, that clinician (or "any"), and a day/time they said suits.
Offer: text with the slot and a reply option; 30-minute window.
No reply or decline: offer moves to next person automatically.
Limits: a patient is offered at most 2 slots a week; the third offer
  waits until the next week.
Late slots (less than 2 hours away): offered only to patients who
  chose "short notice OK".
Fail-safe: if no one accepts, slot returns to the general pool.

Two details keep it fair. The clinical priority flag is set by staff, never by the AI, so the order cannot drift from clinical judgement. And the weekly limit stops one eager patient absorbing all the cancellations while others wait.

Consider a doctor with six cancellations in a week, of which four were within 24 hours. Without a waitlist, those four slots are likely lost; the practice has roughly 60 minutes of clinician time it cannot recover. With it, if the matching rules and short-notice flag capture half, that is two filled slots, about 30 minutes, at essentially no staff time. The gain is modest per week but compounds, and every filled slot is also a patient seen sooner. For an example of the same idea in another business, see how a class waitlist runs automatically.

Waitlist messages that disclose nothing

A text can be seen by anyone who picks up the phone. Keep it neutral: "A slot has opened at [practice name] on Thursday at 2:20pm. Reply YES to take it or NO to pass. This offer lasts 30 minutes." Do not name the doctor's specialty if it reveals a condition, and never include the reason for the visit. Confirm in writing that the patient agreed to text messages, and honour a "no texts" choice every time.

Connecting the tool to the EHR calendar

The calendar link is where most scheduling projects get hurt. The goal is one source of truth: the EHR calendar. The AI tool should read availability from it and write bookings back, so staff and the AI never see different pictures.

Ask the vendor these before you sign, and note the answers:

  • Is the sync two-way and near real time, or does it run every few minutes? What happens to a booking made in the gap?
  • Which EHR calendar and version does the integration support, and is it a supported connector or a workaround?
  • Can it read appointment types and their rules, or must you recreate them in the tool?
  • How are cancellations, reschedules and no-show flags passed back?
  • What patient data leaves the EHR, where is it stored and for how long?
  • What happens if the link fails: does the tool stop taking bookings, or keep offering stale slots?

Then test, before any patient sees it. Create ten test bookings across types and confirm each appears correctly in the EHR. Book the same slot from two places at nearly the same moment. Cancel and rebook. Block a clinician's day in the EHR and check the tool stops offering it. Turn the link off and confirm the failure behaviour. A practice-management system's own booking features may do much of this, so compare before buying a separate tool; the tutorial on a practice-management tool and AI add-ons for doctors looks at that.

Continuity, telehealth and room limits

Some rules are not about time at all. Continuity of care means a patient with a long-running condition is best booked with the same doctor, so give each patient a preferred clinician in the record and tell the AI to offer that doctor first, falling back to "any available" only when the patient agrees. The cost is longer waits for some patients; the benefit is fewer repeated histories. Say which matters more in your practice and write it down.

Telehealth has its own constraints. Video slots need a working link, a patient who has tested their device and a doctor in a suitable space. Treatment rooms are a second hidden limit: two doctors cannot both do minor procedures if there is one procedure room. Add rooms as a resource in the tool, so a procedure booking needs a free doctor and a free room at the same time. A frequent surprise is that the AI offers a slot that is free in a doctor's calendar but not in the room's, and a patient arrives to find nowhere to go.

What the rules look like as instructions to the tool

However the tool is configured, through menus or written instructions, the rules should read as plain statements a new staff member could follow. Here is an illustrative set for one doctor, written the way you might enter them into a tool that takes instructions:

Dr A, Monday to Thursday, 9:00-12:30 and 14:00-17:00.
- Follow-up (15 min): existing patients, self-book, max 1 issue.
- New patient (40 min): self-book mornings only, form required.
- Long visit (30 min): staff book only.
- Hold 2 same-day slots per session; release at 10:00 and 15:00.
- Never place long or new-patient visits after 15:30.
- Overbook: 1 extra follow-up per afternoon session only.
- If the reason text includes any word on the watch-list, do not book;
  create a staff-review task and tell the patient "our team will
  contact you shortly; if this is an emergency call [number]".
- Always offer "speak to a person" on every screen.

Keep this document, with a date and an owner, and update it every time a doctor's hours or preferences change. When the schedule behaves oddly, the first check is whether the instructions say what you think they do.

A sample patient exchange in a chat booking route shows the rules at work. It is illustrative.

Patient: I need to see Dr A about my blood pressure tablets.
Assistant: I can help with that. Is it a review of your current
tablets (10 minutes by phone or video) or a face-to-face follow-up
(15 minutes)? If you have other issues to discuss too, a 30-minute
visit would suit better, and our team can book that for you.
Patient: Face to face, and I also want to ask about my knee.
Assistant: Thanks. Since that is two issues, I'd suggest a longer
visit. I'll pass this to our team and they'll contact you today to
find a time. If you feel unwell right now, please call [number].

The assistant did not guess that two issues fit in 15 minutes, did not judge either problem and gave a clear next step. That behaviour comes from the "one issue per follow-up" rule, not from any cleverness.

Where the AI stops and staff take over

A short list of cases should always go to a person, and the tool should be configured so it cannot do otherwise.

  • Any request that mentions a symptom suggesting urgency, or any reason text matching your watch-list.
  • Requests to book more than the type's allowed number of issues, or visits for another person.
  • Any change to a procedure or long visit.
  • A patient who has missed several appointments in a row: a person should decide how to proceed, kindly.
  • Any complaint, or any patient who says the booking system did not work for them.

The patient must always have a route to a person, on every screen and every message. If the practice also covers calls out of hours, the after-hours call rules tutorial sets out the matching voice rules.

A four-week rollout for an illustrative four-doctor practice

Take a practice with four doctors, three front-desk staff and about 120 bookings a day. They decide to roll out online booking for follow-ups first.

  1. Week 1. Pull a week of appointment data; correct lengths; write the type table and the waitlist rules; get each doctor's sign-off on their own types.
  2. Week 2. Configure the tool, connect the EHR calendar and run the ten-booking test and the failure test. Staff use the patient form themselves on a dummy patient.
  3. Week 3. Open booking for follow-ups and reviews to existing patients only. Front desk reviews every booking the next morning for wrong types.
  4. Week 4. Switch on the waitlist for those types. Count wrong-type bookings, double bookings (target: zero), waitlist fills, and complaints. Decide whether to add annual checks next.

Judge the first month on four numbers: wrong-type bookings per hundred, double bookings, filled cancellations and calls to the front desk about booking. If wrong-type bookings exceed about five in a hundred, improve the patient wording before adding any new types. The broader appointment scheduling tutorial covers tool choices beyond the clinical specifics here.

How to check the rules are working after go-live

Pull a short report every Friday for the first six weeks and read it with the doctors. Four checks are enough. First, the average actual length of each type against its scheduled length: a gap of more than three minutes means the type needs changing. Second, the number of bookings reclassified by staff, with the reason; a pattern, such as patients choosing "follow-up" for several issues, shows where the wording fails. Third, the waitlist: offers made, accepted, expired and the minutes of clinician time recovered. Fourth, patient comments, including any in the free-text box that mention frustration with booking.

A quick sum for a month: if 40 cancelled slots of 15 minutes were offered through the waitlist and 22 were filled, that is 330 minutes, or 5.5 hours of clinical time recovered, at near zero staff time. If the offers were mostly too late, 22 would fall fast, and the fix would be the short-notice flag, not the software.

Mistakes that show up in the first month

Default lengths left on. The tool ships with 30-minute slots and nobody changes them, so follow-ups waste half their time. Fix: the type table, before anything else.

A hidden second calendar. A doctor keeps a personal calendar for meetings and the tool does not see it, so patients are booked over a lunch meeting. Fix: block all non-clinical time in the EHR calendar, or sync the other one.

Overbooking with no "everyone came" rule. It works for three weeks until a Monday when everyone attends, and the waiting room revolts. Fix: the five-part rule above and a monthly review.

Waitlist offers that disclose too much. A text names a specialty or condition. Fix: neutral wording and a patient-consent record.

Scheduling is one of the more forgiving places to use AI, because the rules are explicit and the results countable. Keep the clinical judgement human, write the rules down, test the calendar link hard, and the tool will apply them tirelessly.

Questions practice managers ask about AI scheduling

Should patients choose their own appointment type?

Only for types that are safe to self-select, such as a routine follow-up or a repeat review. For anything where the wrong choice leads to a short slot and a rushed visit, give plain-language descriptions, require a reason in a few words, and let staff reclassify before the day. The AI should never decide clinical urgency.

Is overbooking ever sensible in a medical practice?

In a controlled form, sometimes. Where no-show rates for a slot type are high and stable, a capped overbook of one per session can protect capacity. It needs a rule for what happens when everyone arrives, and it should never apply to long or complex visits. Review it monthly against actual arrivals.

What should the AI do when someone asks for an urgent same-day visit?

Follow a fixed rule: offer any slots held back for same-day need, and otherwise hand the call or message to a person. It must not judge how urgent the problem is. Add emergency wording on every booking screen telling patients to call emergency services if they think it is an emergency.

Can a waitlist message be sent automatically?

Yes, for offering a freed slot, if the patient has agreed to be messaged and the wording discloses nothing sensitive. Keep the text neutral, set a response window such as 30 minutes, and have the system move to the next person automatically when the window closes.

Further reads

Sources: no vendor or product is named, so there are no prices or features to cite. The rules, slot lengths, no-show rates and capacity figures in the examples are illustrative and must come from your own data and clinicians.

Want your appointment types and rules set out?

On a 1:1 call we'll go through your current slot types, no-show data and waitlist, then decide which scheduling rules an AI tool should run and which should stay with your staff.

Book a 1:1 call with me