Completed example
A completed recommendation for an appointment-led business, with the next action and responsible role at every stage.
Hypothetical example: a wellness business receives appointment enquiries through messaging, offers a service or quotation, books a slot and handles payment and changes. This is an illustrative operating design, not an account of a customer, a tested product configuration or a commercial result.
| Stage | Typical failure | Recommended process | Responsible role | Evidence of completion |
|---|---|---|---|---|
| Enquiry received | A message is answered but nobody owns the enquiry. | Create an open enquiry with a responsible role and a visible next action; route unattended enquiries to the duty owner. | Reception or enquiry owner | An enquiry record shows its owner, current status and next action. |
| Need clarified | The customer repeats their request at each handoff. | Keep the permitted service request and agreed next step with the enquiry; hand clinical questions to the appropriate professional. | Reception for service details; clinician for clinical questions | The authorised record contains the agreed service request and any human handover. |
| Quote or slot offered | An offer is mistaken for an accepted order or confirmed appointment. | Keep sent, accepted and booked as separate states; record the customer decision before advancing. | Sales owner or booking coordinator | The offer is recorded, with acceptance or booking confirmation recorded separately. |
| Decision followed up | Follow-up continues after a decision or opt-out. | Base follow-up on the unresolved decision and permitted channel; stop on acceptance, decline, closure or opt-out. | Enquiry owner | The decision and stop condition are recorded; closed records leave the follow-up queue. |
| Booking confirmed | A message says booked while the appointment record is incomplete. | Confirm only after the authoritative appointment record succeeds; leave failed attempts pending and route the exception to a person. | Booking coordinator | A single confirmed appointment exists in the booking authority and is visible to staff. |
| Payment confirmed | A payment attempt is counted as money received. | Separate attempted, pending and confirmed payment; reconcile uncertain status before treating the obligation as settled. | Authorised payments owner | The payment authority confirms the transaction and the correct booking or order reference. |
| Change or cancellation | The conversation changes but the schedule does not. | Apply the authorised change to the booking record before confirming it; follow the approved cancellation and payment policy. | Booking coordinator; payments owner where needed | The appointment record shows the change, and any payment consequence has its own authorised record. |
| Human exception handled | An automated reply competes with the person resolving the problem. | Assign the exception to a named role, pause competing replies and close it only after the responsible person records the outcome. | Duty manager or appropriate authorised specialist | The exception has an owner, a recorded resolution and a clear return to the normal process. |
The recommended repair is a clear owner and an authoritative outcome at every handoff. An offer is not a booking, and a payment attempt is not confirmed payment. Keep the current tools where they can support these states reliably; consider a connection or replacement only for a demonstrated operating gap. This example establishes a recommended process, not an achieved result.
Discuss your enquiry and booking process with Vantage. We can review where ownership and follow-up break down and recommend the next step.
Discuss your business process with Vantage