The calendar request times out, and the caller asks, “Am I booked or not?” The receptionist needs an answer based on the operation's evidence, even when that answer is that confirmation remains pending.
This is a communication and recovery problem, not an invitation for the model to choose whichever response sounds reassuring.
Translate technical uncertainty into a useful status
Distinguish a known rejection from an unknown write outcome. A rejected time can lead to another offer. An unknown write needs reconciliation before another booking attempt.
| Verified state | Appropriate communication |
|---|---|
| Booking saved and matched | Confirm the agreed appointment |
| Provider explicitly rejected it | Explain that the booking did not complete |
| Response missing after submission | Explain that confirmation is still being checked |
| Staff action required | Give the approved follow-up route |
Do not expose raw errors to the caller or promise a completion time that operations cannot support.
Give the caller a reference the office can use
A local request reference can help staff find an unresolved operation, but label it as a request reference. It must not be presented as a confirmed calendar booking number if no such result is known.
Keep the requested details and last known evidence under that reference. If the customer calls again, staff should not need to reconstruct the case from several disconnected transcripts.
The tool-timeout guide explains the integration mechanisms behind this status. The caller-facing layer should use those explicit outcomes instead of interpreting a generic error paragraph.
Reconcile before offering a replacement
If the original appointment may exist, a second offered slot can create conflicting commitments. Check the remote state using supported identifiers or route the uncertainty to staff.
When a result is found, compare its actual date, location, service, and customer boundary. Finding any event near the requested time is not sufficient.
If the outcome cannot be established automatically, preserve the pending status and assign a reviewer. A truthful unresolved state is more useful than a false yes or no.
Test the words as well as the records
Use fictional scenarios for a request never sent, remote rejection, accepted write with lost response, and delayed success arriving after a fallback message.
Check that the next spoken statement uses the newest verified state. A background success should not silently contradict a message already sent to the caller; decide how the follow-up communicates the resolution.
Calendar-timeout questions
Should the AI say “booking failed” for every timeout?
No. The remote action may have succeeded.
Can a request reference reassure the caller?
It can make follow-up traceable, provided its meaning is clear.
What should staff see?
Show the request, uncertainty, reconciliation evidence, and next owner in the operating workflow.