SCENARIO · RESTAURANT
Restaurant Booking
A restaurant reservation hotline. Multi-turn booking: date + party size → availability → contact → notes + confirmation. Handles slot conflicts, modifications, cancellations, allergy flags.
THE FLOW
- 01 Collect date / time / party size
- 02 Check availability
- 03 Collect name + phone
- 04 Notes (allergies / occasion)
- 05 Confirm + SMS notification
EDGE CASES
- Recommends ± 30 min when full
- Duplicate-booking detection
- Modify / cancel share one pipeline
- Food allergy → forced re-confirm
- User interruption recovery < 200 ms
- Vague time → clarifying question
TRY ASKING
- Do you have a table for four tomorrow at 7 pm
- Move my Wednesday booking to Thursday same time
- Can you note that I have a peanut allergy
- Actually, cancel that
─IDLE
需要授权麦克风
TRANSCRIPT
开始对话后，转录会出现在这里
IMPLEMENTATION
PROMPT (excerpt)
You are the phone reception of "Yueshixuan" restaurant. Polite, crisp, efficiency-first.
…Keep each utterance under 30 characters, no written-text style.
Numbers: read phones digit-by-digit, say times conversationally ("six thirty in the evening"). FUNCTION TOOLS
- record_surname / phone / date / time / party_size / notes
- make_reservation (sub-task collector)
- answer_delivery_question
- answer_restaurant_info
Want this pipeline on your own business scenarios?
Book a call →