The receptionist collects the requested time, but a manager must approve the visit. Calling that appointment confirmed creates an expectation the approval process has not earned.
An approval-dependent booking needs a request state, an identified reviewer, and a clear rule for what happens to capacity while review is pending.
Make pending approval a genuine operating state
Store the requested service, customer contact, proposed time, approval reason, and next owner. Do not rely on the transcript as the only place those details exist.
For a fictional specialist visit, the approval might concern resource eligibility or scope. It should not be interpreted as an AI-generated decision about matters the business has reserved for staff.
| State | Permitted message |
|---|---|
| Request collected | Details are ready for review |
| Approval pending | The appointment is not yet confirmed |
| Approved, scheduling pending | Approval exists but capacity still needs confirmation |
| Confirmed | The required review and saved booking are complete |
The business may combine some stages, but it must define what evidence supports each promise.
Decide whether pending requests hold capacity
A temporary hold can protect the requested slot while staff review, but it needs expiry and cleanup. A request without a hold leaves the time subject to change.
Explain that distinction to the customer. Do not say “your slot is reserved” unless the scheduling authority actually enforces a reservation.
Reviewers also need the current request version. If the caller changes the date or service, an earlier approval should not authorise the revised booking automatically.
Keep approval completion separate from the calendar write
Approval does not guarantee that the slot remains available. Recheck the relevant constraints and execute the supported booking operation.
If the write fails or times out, preserve the approval and report the unresolved scheduling outcome. Do not ask staff to approve repeatedly just because an integration response was lost.
The approval-preview article describes what a reviewer should see before acting. The timeout guide covers uncertain external writes.
Test delay as well as rejection
Use fictional cases for approval, rejection, expiry, changed requests, and a reviewer who never responds. The last case reveals whether the queue has an owner or merely a notification channel.
Agree on follow-up timing before the AI mentions it. A truthful pending request with reliable staff review is useful; an unattended approval queue is another way to lose enquiries.
Approval-booking questions
Can we show the requested time to the caller?
Yes, as a request or actual hold according to the implemented policy.
Does approval mean the booking is saved?
Not unless the workflow also verifies the required scheduling action.
What belongs in acceptance?
Include delay, expiry, and a lost write response when scoping the approval flow.