Appointment Booking

Book, reschedule, cancel, and hand off appointment requests for a service business.

The user wants a bot that collects appointment details, confirms requests, handles reschedule or cancellation paths, and can later connect to a booking or calendar API.

• Which services should users be able to book?
• Should availability be checked through an API or handled by staff manually?
• What customer details must be collected?
• Before going live, replace the placeholder availability, create-booking, reschedule, and cancel actions with a real booking/calendar API or calendar module.
• If the business confirms bookings manually, keep the placeholder actions but route staff review through the support handoff.

• Start with a menu for booking, rescheduling, cancellation, and help
• Let the user choose a service or type another service
• Collect preferred date/time, name, and phone
• Run an explicit placeholder availability check that can be replaced with a real booking API
• Confirm the booking with a generated booking reference
• Support reschedule and cancel paths for existing bookings
• Offer live support when a slot is unavailable or the user needs help

Good to know

• Before telling the user an appointment is confirmed, include an explicit placeholder or API request block.
• Use HTTP_REQUEST only if the user approves or provides a booking/calendar API.
• Without an API, keep availability and booking creation as clearly named placeholder SET_VARIABLE actions.
• Use START_CONVERSATION for live support when the user needs staff help.

Keep in mind

• Do not create a calendar integration module action unless an installed module exists.
• Do not claim a real appointment was created unless a real booking/calendar API step exists.
• Do not leave failed availability checks without retry or support options.