1. Identify appointment type
What kind of appointment do you need?
Collects appointment preferences and creates a booking request that staff can accept or send to a calendar tool.
What kind of appointment do you need?
Which days or times work best?
What timezone should we use?
What kind of appointment do you need?
Which days or times work best?
Book appointment requests by phone. Ask for appointment type, preferred dates and times, timezone, contact details, and notes. Avoid promising unavailable slots. Save a booking request.
{
"outcome": "Appointment booking 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": "appointment type captured during the call.",
"name": "appointment_type",
"required": true,
"type": "text"
},
{
"description": "preferred times captured during the call.",
"name": "preferred_times",
"required": true,
"type": "date"
},
{
"description": "timezone captured during the call.",
"name": "timezone",
"required": true,
"type": "date"
},
{
"description": "notes captured during the call.",
"name": "notes",
"required": false,
"type": "text"
},
{
"description": "confirmation required captured during the call.",
"name": "confirmation_required",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Appointment booking. What kind of appointment do you need?
Caller: I want to book a consultation if you have something this week.
AI: Which days or times work best?
Caller: Tuesday afternoon or Thursday morning would work for me.
Make the first screen and opening line match what the caller will actually get. For Appointment booking, 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, appointment type, 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 caller needs urgent help, special accommodation request, conflict or cancellation policy issue 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 consultations, inspections, clinic callbacks.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "What kind of appointment do you need?". 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, appointment type, 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: caller needs urgent help, special accommodation request, conflict or cancellation policy issue.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.