Confirm and start a newsletter campaign
Follow this guide to create the queued campaign after reviewing recipients, the 100-per-five-minute limit and ETA. 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 → Letter Manager → Email Marketing / Newsletter → Start Newsletter Send
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 you’ll accomplish
Create the queued campaign after reviewing recipients, the 100-per-five-minute limit and ETA. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Complete recipient selection, subject and body.
- Select Start Newsletter Send.
- Check the confirmation details.
- Verify the action.
- Keep the page open for immediate processing or allow cron to continue it.
Fields and options to review
Action scopeCreate the queued campaign after reviewing recipients, the 100-per-five-minute limit and ETA.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Start Newsletter Send
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Campaign creation stores a queued campaign and one pending recipient row for each unique validated email.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.