Campaign content and validation

Confirm and start a newsletter campaign

Create the queued campaign after reviewing recipients, the 100-per-five-minute limit and ETA.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Start Newsletter Send
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

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.

Exact step-by-step process

  1. Complete recipient selection, subject and body.
  2. Select Start Newsletter Send.
  3. Review the confirmation details.
  4. Confirm the action.
  5. Keep the page open for immediate processing or allow cron to continue it.

Fields, choices and supported possibilities

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
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • Campaign creation stores a queued campaign and one pending recipient row for each unique validated email.

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.