Interpret Letter Manager email status
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Distinguish pending/not confirmed from a successful send and a detected open.
Where to goAdmin Area → Letter Manager → Sent Letters History → Email / Read Receipt
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 this guide helps you do
Distinguish pending/not confirmed from a successful send and a detected open. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Read Sent when email_sent=1.
- Read Pending when email_sent is not 1.
- After Sent, read Not opened yet until an open event is detected.
- Read Read: timestamp after at least one pixel request.
- Go to Internal Full View for full evidence.
Fields and options
Action scopeDistinguish pending/not confirmed from a successful send and a detected open.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History → Email / Read Receipt
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- Email Sent is based on the email library send() boolean.
- Open status is independent from send status and depends on the tracking pixel being fetched.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.