Add an email-only cover note to a client letter
Include a highlighted sender message in the email without changing the official PDF. 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 → Dashboard → Search Clients & Leads → Email Message / Cover Note
Before you start
- 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 you’ll accomplish
Include a highlighted sender message in the email without changing the official PDF. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Write the optional covering message.
- Keep the official letter text in Letter PDF Content.
- Send the letter.
- Go to Internal Full View to confirm the note stored with the record.
- Check the PDF does not include the cover note.
Fields and options to review
Action scopeInclude a highlighted sender message in the email without changing the official PDF.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Email Message / Cover Note
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- The email_note value is stored as long text.
- The email body escapes the note and converts line breaks.
- There is no module word limit.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
