A confirmation call script says who is calling and why, checks that it reached the right person, reads the appointment details from the record and asks one question. After that it needs a prepared line for each answer the person might give: yes, a new time, a cancellation, a question, a request for a person, or "you have the wrong number." Here is the base script the rest of this guide builds on. Fill the bracketed fields from the appointment record.
Hi, this is [caller name] from [organization], calling about an upcoming appointment. Am I speaking with [first name]?
Thanks. You're booked for [appointment type] on [day, date] at [time], at [location]. Can you still make that time?
What happens after that question depends on the answer, so the branches come first below, then reminder and voicemail versions, scripts for pickups and deliveries, and the intake sheet a contact center fills in with each client before anyone makes the first call.
What should a confirmation call script include?
A confirmation call script has six parts, in this order: the opening, a check that you have the right person, the details from the record, one question, a prepared line for each answer, and a close that repeats the result. The close matters to your team as much as to the person on the line, because it decides which outcome gets logged.
| Part | What to say | Why it's there |
|---|---|---|
| Opening | "Hi, this is [caller name] from [organization], calling about an upcoming appointment." | Tells the person who is calling before asking anything of them |
| Right person | "Am I speaking with [first name]?" | No appointment details until the person is confirmed |
| Details | "[Appointment type] on [day, date] at [time], at [location]." | Read from the record word for word, with the time zone when the person might be traveling |
| The question | "Can you still make that time?" | A yes or no question gets an answer you can log |
| Branches | The prepared lines in the next section | Keeps reschedules and cancellations off the improvised path |
| Close | "You're confirmed for [day] at [time]. See you then." | Saying it back catches a misheard date before it becomes a no-show |
A confirmation call script for every answer
Write a line for every answer before the first call goes out, and next to each line write what changes in your system and which outcome your team will see. If the script stops at the question, the caller improvises the rest, and a reschedule agreed on the phone is easy to forget to enter in the calendar.
| The person says | Next line | What changes in the record | Outcome to log |
|---|---|---|---|
| Yes, I'll be there | "Great, you're confirmed for [day] at [time]. [One preparation line, if any.] See you then." | Appointment marked confirmed | Confirmed |
| I need a different time | "No problem. I have [option one] or [option two]. Which works better?" | Old slot released, new one booked | Rescheduled |
| Cancel it | "Understood, I've cancelled your [day] appointment. Would you like to book another time while I have you?" | Slot released | Cancelled |
| I'm not sure yet | "That's fine. Your appointment stays booked. To confirm or change it, call [callback number]." | Nothing | Needs follow-up |
| A question about parking, directions or preparation | The approved answer, or: "I don't have that in front of me. Let me transfer you to someone who does." | Nothing | Confirmed, or transferred |
| I want to talk to someone, or a complaint | "Of course. I'll transfer you to someone on the team now." | Nothing | Transferred |
| Now's not a good time | "No problem. Is there a better time today to reach you?" | Callback time noted | Callback requested |
| Wrong number | "Sorry to bother you. I'll take this number off our list." | Number flagged on the record | Wrong number |
| Stop calling me | "Understood. I've noted that, and you won't get these calls from us again." | Number added to your opt-out list | Opted out |
Two branches need care. On a wrong number, say nothing about the appointment, not even its type. And when someone else in the household answers, ask them to have [first name] call [organization] at [callback number], and leave it there.
For a reschedule, offer two specific times rather than asking when suits them. Two real slots give the person something to answer on the spot, while an open question invites "I'll call you back."
Appointment reminder call script and voicemail version
A reminder call gives the details and invites a change. A confirmation call asks for an answer. Use the reminder when the appointment stays booked unless the person speaks up, and the confirmation when your client wants every slot answered for. Both need a voicemail version, because some of these calls will reach voicemail.
Reminder, when the person answers:
Hi [first name], this is [caller name] from [organization] with a reminder about your [appointment type] on [day, date] at [time], at [location]. [Preparation line, such as what to bring or when to arrive.] If you need to change it, I can do that now. Otherwise, we'll see you then.
Voicemail:
Hi, this message is for [first name]. This is [organization] calling about your appointment on [day] at [time]. To confirm or change it, please call us at [callback number]. Thank you.
The voicemail leaves out the appointment type and the reason for the visit, since anyone in the house might play the message. It names the organization, the day and time, and a number to call. Read it aloud with a timer before the program starts.
Confirmation scripts for pickups, deliveries and service visits
Contact centers confirm more than appointments. A delivery, a pickup or a technician visit adds three things to the script: a time window instead of a time, an address to confirm, and whether someone will be there.
Hi, this is [caller name] from [organization] about your [delivery, pickup or service visit] on [day], between [start time] and [end time]. Is [street address] still the right address, and will someone be there?
| The person says | Next line | What changes in the record |
|---|---|---|
| Yes to both | "Great, you're all set for [day] between [start] and [end]." | Confirmed |
| Different day | "I have [option one] or [option two]. Which works?" | Moved to the new window |
| Address changed | "Thanks. Let me get you to someone who can update that." | Transferred, so a person checks the new address |
| Access notes, such as a side door or a gate | "Got it, I'll add that for the [driver or technician]." | Note added where the driver or technician sees it |
Treat an address change as a transfer unless your client explicitly allows it to be changed on the call, since a delivery sent to the wrong address costs far more to fix than a transfer does.
What to collect from each client before you write the script
Before anyone takes a single confirmation call for a client or a program, fill in one sheet. It covers the record fields the script reads, the changes a caller may make and the rules for them, the answers to common questions, when to hand off, the voicemail wording, the calling window and the outcome labels your client wants back.
| Field | Example | What goes wrong without it |
|---|---|---|
| Record fields the script reads | First name, appointment type, date, time, time zone, location, provider or technician | The script reads blanks or the wrong time |
| Caller ID and callback number | The client's main number, or a number set up for the program | The voicemail leaves no way to confirm |
| Identity check | First name only, or first name plus date of birth | Details reach the wrong person |
| Changes allowed on the call | Confirm and reschedule only, or cancel as well; which appointment types | The caller promises a change the calendar won't take |
| Reschedule rules | How far ahead, which slots, same provider only | New times that break the client's booking rules |
| Cancellation wording | The client's own policy text, word for word | A fee or deadline gets paraphrased wrong |
| Approved answers | Address, parking, what to bring, how to prepare | Questions get guessed answers |
| Handoff | The transfer number, the hours it is staffed, topics that always go to a person | Transfers land on a closed line |
| Voicemail text | The exact message, callback number included | A message says more than it should |
| Calling window | Days, hours, holidays, and whose local time applies | Calls go out at the wrong hour |
| Languages | English, Spanish | People who speak another language get no confirmation |
| Opt-out handling | Where "stop calling me" requests go, and who removes the number | People keep getting calls after asking to stop |
| Outcome labels and delivery | Confirmed, rescheduled, cancelled, voicemail, transferred, needs follow-up; a daily file or a webhook | The client can't act on the results |
A BPO keeps one sheet per client program. When a client changes a rule, update the sheet first and the script second, so the two never disagree. For the federal limits on calling hours, see our outbound call center guide.
What an AI agent needs written down
A person on your team fills gaps from experience. An AI agent works from what you give it, so the intake sheet becomes its instructions, and a few judgment calls have to be spelled out:
- What counts as confirmed. "Yes" is clear, "I think so" isn't, so decide which bucket the second one goes in.
- The limit on changes, such as rescheduling only into open slots in the next two weeks with the same provider.
- The topics that always go to a person: billing, complaints, anything clinical, anything your client marks off limits.
- What to do on voicemail and on call screening services, and the exact message to leave.
- How the agent introduces itself at the start of the call.
The FCC treats AI-generated voices as artificial voices under the Telephone Consumer Protection Act (FCC 24-17, released February 8, 2024). Our guide to AI outbound calling covers that ruling, the consent it implies and the disclosure rules the FCC has proposed. Before going live, test every row of the branch table with a role-played call, then score a sample of recorded calls each week once the program is running.
Rules that change a healthcare reminder script
Healthcare reminder calls to cell phones can rely on an FCC exemption instead of the patient's prior express consent. When a program does, the exemption's conditions shape the script itself: the provider's name and number at the start, a short call, a way to opt out on every call, and nothing about bills.
The conditions are in 47 CFR 64.1200(a)(9)(iv). Here is how each one lands in the script:
| Condition in the rule | What it means for the script |
|---|---|
| Calls go only to the wireless number the patient provided | The list comes from the number in the patient's record, never from an appended or looked-up number |
| The provider's name and contact information, stated at the beginning of the call | The opening names the provider and gives a number before anything else |
| Purposes limited to appointment and exam confirmations and reminders, and the other listed purposes | The call stays on the appointment |
| No telemarketing, solicitation or advertising, and no billing, debt collection or other financial content | No balance reminders or offers in the same call |
| Concise, generally one minute or less for a voice call | Time both versions read aloud |
| One message a day per patient, up to three calls or texts combined per week | Caps how many attempts the program makes, across calls and texts |
| An opt-out in each message: an interactive voice or key press opt-out on calls a person may answer, a toll-free number on calls that may reach voicemail | Add the opt-out line to both the live version and the voicemail |
| Opt-out requests honored immediately | The "stop calling me" branch removes the number right away |
A live-answer version with those lines added:
Hi, this is [provider name], [phone number], calling with an appointment reminder for [first name]. You're booked on [day, date] at [time]. Can you still make it? [Branches as above.] To stop these reminder calls, [opt-out instruction, such as say "stop" or press a key].
And the voicemail version:
This is [provider name], [phone number], with an appointment reminder for [first name] on [day] at [time]. To confirm or change it, call [callback number]. To stop these reminder calls, call [toll-free number].
This table summarizes the federal rule and isn't legal advice. Programs that rely on consent, state laws and HIPAA bring their own requirements, so have counsel review the script before the first call.
How Telvana runs a confirmation program
Our team builds the agent's call from your script and the rules on your intake sheet, tests it on your call types, and you approve it before it takes a live call. Calls go out from a contact list inside the calling hours you set, or your own systems trigger each one through the API when something is booked. The agent confirms, reschedules or cancels in the scheduling system you connect, answers questions from your knowledge base, and transfers to the number you choose under your rules. Every call is recorded, transcribed, summarized and tagged with its outcome, so your team sees which ones need a person. Calls run in English and Spanish, and each client program gets its own workspace. Texting is a separate channel with its own campaigns, and pricing starts at $399 a month, based on call volume, plus a one-time setup fee. The confirmations and reminders page has the details.
Frequently asked questions
What do you say when confirming an appointment by phone?
Say who you are and where you're calling from, check you're speaking to the right person, read the appointment type, date, time and location from the record, and ask whether they can still make it. Then use the prepared line for their answer and repeat the result before you hang up.
How long should a confirmation call be?
Long enough to read the details and get one answer. Read your script aloud with a timer, voicemail included, and cut anything that isn't the details, the question or a branch. Healthcare reminder calls that rely on the FCC exemption must be concise, generally one minute or less (47 CFR 64.1200(a)(9)(iv)(E)).
What is the difference between a confirmation call and a reminder call?
A reminder gives the details and invites a change, and the appointment stays booked unless the person speaks up. A confirmation asks for a yes or no and logs the answer, so your client knows which slots are firm and which are at risk before the day.
Should you leave a voicemail for an appointment reminder?
Yes, a short one: the organization, the day and time, and a number to call back. Leave the appointment type and the reason for the visit out, since anyone in the household may hear it. A healthcare program relying on the FCC exemption also needs a toll-free opt-out number in the message.
When should confirmation calls go out?
Early enough that a cancelled slot can still be filled, which depends on how far ahead people book with that client. Set the timing per appointment type in the intake sheet, and keep every call inside the calling window you agreed with the client.
Can an AI agent make confirmation calls?
Yes. Confirmations come in volume, follow the same path almost every time and have one clear outcome, which makes them a good first program for an AI agent. Give it the intake sheet, the branch table and the voicemail text, and transfer anything outside them to a person.
Put one client's list on an agent
Fill in the intake sheet for one client program, then book a demo and bring it with your script. We'll let you hear an agent take a confirmation call built from it. More on running outbound programs is in the outbound guides.