Booking requests, confirmation and message delivery: what differs?
A submitted form, a business approval and a delivered notification are three separate events, rather than one success signal.
What does a request show?
A request through a booking link expresses a customer's preferred service and time. Do not treat it as a confirmed service before checking the business calendar and record state. When reviewing a repeat request, make sure it does not create a duplicate.
What changes with approval?
Business approval records the scheduling decision. If the date changes, agree the new time with the customer and update the existing booking. Marking a cancellation completed makes the history and reports misleading.
What does delivery prove?
An accepted notification request is not the same as delivery to the recipient. A delivery indicator also does not guarantee attendance. In Rezerve, assess the appointment and notification states separately and check the customer's communication choice.
| Comparison point | First approach | Second approach |
|---|---|---|
| Request | Customer asks for a time | Not final approval or a completed service |
| Approval | Business accepts the appointment | Not evidence of message delivery |
| Delivery | Notification reaches recipient | Not evidence of attendance or payment |
Worked example
A request arrives for 16:00. The business proposes 16:30 and the customer agrees. Update the record to 16:30. If a notification fails, do not assume the old 16:00 entry is correct; check communication and the scheduling decision separately.
Before you apply this
- Read appointment state separately from message state.
- Compare old and new times after a change.
- Do not send notifications without customer permission.