Read recipient delivery details
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Interpret recipient name, email, delivery status, sent time, error and tracking evidence.
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What this guide helps you do
Interpret recipient name, email, delivery status, sent time, error and tracking evidence. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Find the recipient row.
- Read its pending, processing, sent or failed state.
- Check sent_at or the stored error.
- Check open count, first/last open and detected client evidence where present.
Fields and options
Action scopeInterpret recipient name, email, delivery status, sent time, error and tracking evidence.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- Only values and transitions exposed by the supplied module code are supported.
- Server-side validation remains authoritative even when browser controls appear to accept a value.
Check it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Related guides
Was this guide useful?Your response is stored only in this browser.