Deny a client reschedule request
Reject an unsuitable proposed time while retaining the original appointment schedule and a clear request decision.
What this feature does
Reject an unsuitable proposed time while retaining the original appointment schedule and a clear request decision. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The deny action updates the request state without changing the original appointment timing.
The appointment remains in its existing status unless a separate lifecycle action is taken.
Configured communication can inform the customer that the proposed time was not accepted.
Step-by-step workflow
- Open the pending reschedule request.
- Review the requested time and reason.
- Select Deny.
- Record a clear explanation where supported.
- Confirm original timing and customer communication.
Important fields and decisions
What happens after completion
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not edit the original time while denying.
- Use respectful customer-facing wording.
- A denied reschedule is not a cancellation.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
