AI Appointment Reminder Calls

Reduce no-shows with automated confirmation calls. This tutorial walks through a dental-clinic example end to end.

The scenario

Dr. Sarah Cohen runs Cohen Dental. Her patient Michael has a dental cleaning scheduled for Tuesday May 27 at 3:00 PM. The clinic wants to confirm 24 hours ahead - or reschedule if Michael can't make it.

One API call triggers a friendly confirmation call. The agent confirms, reschedules, handles cancellations, or leaves a voicemail - all without front-desk staff picking up the phone.

The API request

Send a single POST to kick off the call:

curl -X POST https://voice.talktomyagent.io/v1/calls \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "to": "+14165550234",
  "targetName": "Michael",
  "triggeredBy": "Cohen Dental scheduling system",
  "maxDurationSecs": 120,
  "task": {
    "goal": "Confirm Michael\'s Tuesday 3pm dental cleaning with Dr. Sarah Cohen, or reschedule if needed.",
    "script": "appointment-confirmation",
    "facts": {
      "patient_name": "Michael",
      "appointment_date": "Tuesday May 27",
      "appointment_time": "3:00 PM",
      "appointment_type": "dental cleaning",
      "clinic_name": "Cohen Dental",
      "clinic_phone": "+16475559876",
      "doctor_name": "Dr. Sarah Cohen"
    },
    "escalation": "If Michael has questions the agent cannot answer, provide the clinic phone number and offer to have the office call back."
  }
}'

Key fields

  • maxDurationSecs - 2 minutes is plenty for a confirmation call.
  • task.script - references the appointment-confirmation playbook profile below.
  • task.facts - all appointment details the agent needs to speak confidently.

What Michael hears

“Hi Michael, this is a quick call from Cohen Dental. I'm calling to confirm your dental cleaning with Dr. Sarah Cohen on Tuesday May 27 at 3:00 PM. Can you make it?”

Outcome branches

  • ✓ Confirms - the agent thanks Michael, reminds him of the time, and ends the call.
  • 🔄 Reschedules - the agent asks for a preferred day/time, notes it, and confirms someone from the clinic will follow up to finalize.
  • ✗ Cancels - the agent confirms the cancellation, asks if Michael wants to rebook later, and closes.
  • 📞 Voicemail - the agent leaves a brief message with the date, time, and clinic callback number.

Playbook script profile

Add this block to your voice playbook. The agent loads it when task.script matches appointment-confirmation.

#### appointment-confirmation

**Opening**: Greet the patient by name. State the clinic name, appointment
type, doctor, date, and time. Ask if they can make it.

**If the patient confirms**:
Thank them. Repeat the date and time once. End the call.

**If the patient wants to reschedule**:
Ask for their preferred day and time. Note it. Let them know the clinic
will call back to confirm the new slot. End the call.

**If the patient cancels**:
Confirm the cancellation. Ask if they'd like to rebook at a later date.
If yes, note the preference. If no, close politely.

**If you reach voicemail**:
Leave a message: "Hi [patient_name], this is Cohen Dental calling to
confirm your [appointment_type] with [doctor_name] on [appointment_date]
at [appointment_time]. Please call us back at [clinic_phone] to confirm
or reschedule. Thank you!"

**Hard limits**:
- Never diagnose, give medical advice, or discuss treatment details
- Never book outside business hours (Mon-Fri 8am-6pm)
- Never share other patients' information
- Keep the call under 2 minutes

Tips

  • Call 24-48 hours ahead. That gives patients time to reschedule without a last-minute gap in the calendar.
  • Respect do-not-call lists. Check opt-out preferences before triggering the call. The API does not enforce this - your scheduling system should.
  • Include a callback number in voicemails. Patients who miss the call need a way to respond. The clinic_phone fact makes this automatic.
  • Batch by time zone. If you serve patients across regions, schedule calls during local business hours.

Appointment reminders are the highest-ROI outbound use case. A single no-show costs more than hundreds of automated calls.