Email Marketing & Newsletter module overview
Understand the complete campaign, queue, history and read-receipt flow implemented by the module.
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter
Before you begin
- 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 covers
Understand the complete campaign, queue, history and read-receipt flow implemented by the module. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Open Letter Manager and select the Email Marketing / Newsletter tab.
- Choose a valid recipient source and selection method.
- Compose and validate the campaign.
- Start delivery and allow the browser processor or cron to continue the queue.
- Review campaign history, delivery states and read-receipt evidence.
Fields, choices and supported possibilities
Action scopeUnderstand the complete campaign, queue, history and read-receipt flow implemented by the module.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- The module sends email only; it does not create Letter Manager PDFs or add records to Letter History.
- The global delivery ceiling is 100 attempted recipients in any rolling five-minute window.
- Campaigns continue through the normal CRM cron hook even after the browser page is closed.
Expected result and verification
- 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.