Edit appointment history notes
Correct or clarify the editable note content attached to appointment history without rewriting the underlying lifecycle action.
What this feature does
Correct or clarify the editable note content attached to appointment history without rewriting the underlying lifecycle action. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The history-note action targets the note field on an existing appointment activity record under authorised access.
Changing a note does not reverse the appointment status or external notification that created the history entry.
The edited wording should preserve an honest audit explanation.
Step-by-step workflow
- Open the relevant history entry.
- Confirm the appointment and original action.
- Edit only the note text that needs correction.
- Save.
- Reopen history and verify the action and timestamp remain understandable.
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 alter notes to conceal material events.
- Use a correction explanation where audit policy requires it.
- Change appointment state through its dedicated action.
- 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.
