Letter Manager module overview
Follow the complete Letter Manager flow from authoring and PDF generation to email, signatures, verification, read evidence, postal tracking and customer history.
Exact navigationAdmin Area → Letter Manager → Dashboard
Before you begin
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What this guide covers
Follow the complete Letter Manager flow from authoring and PDF generation to email, signatures, verification, read evidence, postal tracking and customer history. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Open Admin Area → Letter Manager → Dashboard.
- Choose Search Clients & Leads for an existing customer or Manual Entry (External) for a non-CRM recipient.
- Create or select letter content, choose whether a signature is required and send the letter.
- Review the generated record in Sent Letters History.
- Use the PDF, internal view, public verification, email/read-receipt, signature, task and postal controls as required.
Fields, choices and supported possibilities
Action scopeFollow the complete Letter Manager flow from authoring and PDF generation to email, signatures, verification, read evidence, postal tracking and customer history.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Code-backed validations and workflow rules
- The supplied module metadata identifies version 1.0.0 and requires CRM version 2.3 or later.
- Normal staff work is performed under Letter Manager → Dashboard, Templates and Settings.
- The module has no separate API, webhook, campaign queue or scheduled cron process.
Expected result and verification
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.