Interpret customer-profile email/read evidence
Follow this guide to review send, open count, first/last time, detected IP, source and proxy note. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Customers → Open customer → Letter History → Email
Before you start
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What you’ll accomplish
Review send, open count, first/last time, detected IP, source and proxy note. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Read Sent or Not confirmed.
- Read Read receipt confirmed or No read receipt yet.
- Check open count and first/last times.
- Check IP source and warning note when present.
- Use Internal Full View for the complete record.
Fields and options to review
Action scopeCheck send, open count, first/last time, detected IP, source and proxy note.
Module version1.0.0
Exact routeAdmin Area → Customers → Open customer → Letter History → Email
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
- Browser controls are not a substitute for server-side and operational verification.
How to confirm it worked
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.