1. Find current booking
Which appointment needs to move?
Captures why a caller needs to move an appointment and records replacement time windows without tying up staff.
Which appointment needs to move?
What new times would work?
Is this a cancellation or a reschedule?
Which appointment needs to move?
What new times would work?
Handle appointment reschedule calls. Ask for current appointment details, reason, preferred replacement times, and whether any cancellation policy issue exists. Save a reschedule request.
{
"outcome": "Appointment rescheduling outcome",
"fields": [
{
"description": "caller name captured during the call.",
"name": "caller_name",
"required": true,
"type": "text"
},
{
"description": "phone number from caller id captured during the call.",
"name": "phone_number_from_caller_id",
"required": true,
"type": "text"
},
{
"description": "current appointment captured during the call.",
"name": "current_appointment",
"required": true,
"type": "text"
},
{
"description": "reason captured during the call.",
"name": "reason",
"required": true,
"type": "text"
},
{
"description": "preferred times captured during the call.",
"name": "preferred_times",
"required": true,
"type": "date"
},
{
"description": "cancellation or reschedule captured during the call.",
"name": "cancellation_or_reschedule",
"required": false,
"type": "text"
},
{
"description": "policy issue captured during the call.",
"name": "policy_issue",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Appointment rescheduling. Which appointment needs to move?
Caller: I need to move tomorrow morning if possible.
AI: What new times would work?
Caller: Any time Friday afternoon is better.
Make the first screen and opening line match what the caller will actually get. For Appointment rescheduling, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.
Decide which fields are required before the call can be considered complete. A practical first version should capture caller name, phone number from caller id, current appointment, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.
Write down the cases that should not be automated. Use human review for fee dispute, same-day cancellation, repeated rescheduling so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.
Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for clinics, salons, tutors.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "Which appointment needs to move?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.
Save a structured result with caller name, phone number from caller id, current appointment, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.
Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: fee dispute, same-day cancellation, repeated rescheduling.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.