Track appointment email read status
Interpret the module's email-read tracking signal as delivery engagement evidence rather than guaranteed human acknowledgement.
What this feature does
Interpret the module's email-read tracking signal as delivery engagement evidence rather than guaranteed human acknowledgement. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Supported appointment emails can include a tracking mechanism that updates read state when the remote client loads it.
Privacy settings, image blocking and security scanners can prevent or falsely trigger the signal.
Read state belongs to communication activity and does not change appointment lifecycle status.
Step-by-step workflow
- Send a supported appointment email.
- Open communication/activity details.
- Review sent and read indicators.
- Compare with mail delivery logs.
- Use direct confirmation for critical attendance changes.
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 treat no read signal as proof the email was unseen.
- Do not treat an automated scanner as human confirmation.
- Respect privacy and tracking policy.
- 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.
