Customer work, connected.

Help & supportMyAccount
Setup, access and Letter Manager integration

Email Marketing & Newsletter module overview

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains the complete campaign, queue, history and read-receipt flow implemented by the module.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter
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

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.

Follow these steps

  1. Go to Letter Manager and select the Email Marketing / Newsletter tab.
  2. Select a valid recipient source and selection method.
  3. Compose and validate the campaign.
  4. Start delivery and allow the browser processor or cron to continue the queue.
  5. Check campaign history, delivery states and read-receipt evidence.

Fields and options

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

Rules and limits

  • 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.

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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page