The situation
Fictional planning example. These are sample decisions, not customer results or a demonstration of a live configuration.
A caller to a fictional appointment-based business wants to move an existing visit to a later morning. None of the currently offered times works for them. The team needs a clear record of the request without accidentally cancelling or replacing the existing booking.
Sample intake record
Use the distinction between reported information and confirmed outcomes when reviewing your own process.
| Field | Sample entry | How to use it |
|---|---|---|
| Existing visit | Caller supplies the permitted appointment reference. | Follow the approved identification process before discussing or changing booking details. |
| Requested change | Later morning preferred. | A preference is not an available or accepted slot. |
| Offered times | Caller declines the available options. | Do not record a new booking from a declined offer. |
| Current status | No booking change confirmed in this example. | Keep the existing appointment status clear; do not infer cancellation. |
| Next owner | Scheduling follow-up owner. | Assign review of the unfulfilled request. |
Walk through the decisions
- Clarify the caller’s intention. Separate a request to reschedule from a request to cancel. Confirm the change the caller is actually asking for.
- Use the approved availability path. Offer only eligible times from the configured process. Do not invent availability or suggest that a preferred time is held when it is not.
- Keep the outcome accurate. Record that no new time was accepted. Any change to the existing booking must follow the business’s explicit approval and confirmation rules.
- Give Scheduling a usable next step. Capture the preferred timing and contact path. Explain the agreed follow-up process without promising an unconfirmed slot or callback time.
Example handoff note
Caller requests a later-morning visit. Offered options declined; no replacement booking confirmed. No cancellation is inferred. Scheduling owner to review alternatives and contact the caller through the agreed service-response path.
When the routine path does not fit
- The caller now wants to cancel: Use the approved cancellation process and clearly distinguish it from the earlier rescheduling request.
- The booking reference cannot be confirmed: Follow the business’s identity/lookup process rather than guessing which appointment to change.
- The caller accepts a later offer: Record the confirmed outcome only after the approved booking process supports it, keeping the current status clear.
Use this with your team
What confirms a booking change? Who handles an unfulfilled preference? How does your team avoid confusing an open request with a cancellation?
Replace the fictional choices with your approved process before configuring service. This page does not collect or send your answers.