1. Identify requester
What are you waiting for?
Screens waitlist callers, captures preferences, and marks who should be contacted when a slot opens.
What are you waiting for?
Which times or dates could work?
How much notice do you need?
What are you waiting for?
Which times or dates could work?
Manage waitlist calls. Ask what slot or item the caller wants, preferred times, flexibility, notice needed, and priority notes. Do not promise placement. Save a waitlist record.
{
"outcome": "Waitlist management 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": "waitlist item captured during the call.",
"name": "waitlist_item",
"required": true,
"type": "text"
},
{
"description": "preferred times captured during the call.",
"name": "preferred_times",
"required": true,
"type": "date"
},
{
"description": "flexibility captured during the call.",
"name": "flexibility",
"required": true,
"type": "text"
},
{
"description": "notice needed captured during the call.",
"name": "notice_needed",
"required": false,
"type": "text"
},
{
"description": "priority notes captured during the call.",
"name": "priority_notes",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Waitlist management. What are you waiting for?
Caller: I want to join the waitlist for the Monday class.
AI: Which times or dates could work?
Caller: I can take a same-day opening if someone calls before noon.
Make the first screen and opening line match what the caller will actually get. For Waitlist management, 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, waitlist item, 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 urgent clinical need, priority dispute, vip exception 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, classes, restaurants.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "What are you waiting for?". 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, waitlist item, 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: urgent clinical need, priority dispute, vip exception.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.