Send and verify a client letter
Complete the supported create, PDF, email and history sequence. 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 → Send Letter & Generate PDF
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
Complete the supported create, PDF, email and history sequence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Recheck recipient, subject, content, signature option, note and enclosure.
- Select Send Letter & Generate PDF once.
- Wait for the redirect to the dashboard and success alert.
- Find the new reference in Sent Letters History.
- Go to the PDF and internal full view.
- Check email status and public verification link.
Fields and options to review
Action scopeComplete the supported create, PDF, email and history sequence.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Send Letter & Generate PDF
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 history row is inserted before PDF generation and email sending.
- The PDF is written to uploads/letter_manager.
- Email is attempted only when a target primary-contact email is available.
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.
