Request appointment feedback
Invite the customer to rate or comment on a completed appointment through the module's feedback flow.
What this feature does
Invite the customer to rate or comment on a completed appointment through the module's feedback flow. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Feedback requests apply to eligible completed appointments and use the configured feedback options and message template.
The module stores request/sent state and later associates the submitted response with the appointment.
Feedback is separate from appointment status and invoice payment.
Step-by-step workflow
- Complete an eligible appointment.
- Confirm feedback options and template are configured.
- Send the request manually or allow cron processing.
- Open the customer feedback link.
- Verify the response on the appointment.
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 request feedback for cancelled or no-show outcomes unless your policy permits.
- Keep public feedback links confidential.
- Do not confuse payment status with feedback eligibility.
- 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.
