Handle a Caller Who Changes the Requested Time Before Booking
Handle appointment-time corrections before booking by replacing the proposed slot, checking availability and obtaining a fresh confirmation.
Table of Contents▼
A caller can change the requested appointment time before booking without asking to reschedule an existing appointment. That distinction matters. The first situation changes an unfinished proposal; the second requires modifying a booking that may already exist.
For a voice assistant, the safe sequence is to replace the proposed time, check the new choice and ask for confirmation again. An earlier “yes” cannot approve a different slot that the caller has not heard.
Know whether a booking has happened
Your workflow should distinguish collecting preferences, offering an available slot, awaiting confirmation, requesting a booking and receiving its outcome. These stages can sound similar in conversation, but they authorize different next steps.
Before a booking request is sent, the assistant can revise the proposal. Once a request has been sent, an uncertain result needs investigation before another slot is booked. After confirmation, a change request belongs to the business's supported rescheduling process.
Burki's current Cal.com setup guide describes its supported creation workflow. Do not present that capability as native appointment rescheduling.
Make the correction explicit
Suppose the assistant offers Wednesday morning and the caller says, “Actually, Thursday afternoon would be better.” A useful reply is: “I'll look for Thursday afternoon instead.” That acknowledges replacement rather than adding another appointment preference without resolving the first.
Check availability for the revised date. If a suitable slot exists, read back the new full date, time and timezone. If it does not, ask which constraint the caller is willing to change. Do not quietly fall back to Wednesday because it was the first available option.
Cal.com's slot documentation provides the availability reference. The product workflow must still keep the returned slot connected to the caller's latest request.
A hypothetical correction during confirmation
Imagine the assistant says, “Would you like me to book Thursday at two in the office's local time?” The caller responds, “Yes—sorry, make that three if it's available.”
That is a correction, not an unconditional approval of two o'clock. The assistant should treat three as the new requested time, check it and ask for a fresh confirmation. It should not seize on the first word and submit the old booking while the rest of the sentence changes the meaning.
A clear follow-up is: “Three is available. To confirm, you want Thursday at three in the office's timezone. Shall I book that?” This hypothetical example is useful for a practice script because the first word and final intent differ.
Preserve the other confirmed details
A time correction does not necessarily invalidate the attendee's name or email. Keep the unchanged information when its meaning remains clear. Repeating the entire intake can frustrate callers and create new opportunities for errors.
However, some details depend on the appointment. If the caller changes from a remote consultation to an in-person visit, location and timezone may need review as well. Identify which values depend on the changed choice instead of resetting everything or preserving everything automatically.
Staff should be able to read the final request without finding two competing times. The record can mention that a correction occurred, but the intended slot must be unmistakable.
Handle late corrections honestly
If the caller changes the time after the booking is confirmed, explain that this is now a change to an existing appointment. Offer the business's actual supported process. Do not create another appointment and imply that the first one disappeared.
If the first booking outcome is unknown, say that it needs checking before another appointment is requested. The absence of a spoken confirmation does not prove that the provider did not create it.
Use the voice-assistant testing guide to organize a bounded review of these distinctions. Ordinary browser practice can test the dialogue; actual provider writes require separate authorized evidence.
Start with three correction scripts: before a slot is offered, during the final confirmation and after a result returns. Give each a different expected next step. That simple exercise prevents “change the time” from becoming one ambiguous instruction.
Ready to try Burki?
Create an assistant and check your available browser practice allowance.
Start Free TrialTrial eligibility and available practice are shown in your workspace.