Attach one enclosed file to a client letter
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to send one additional approved file alongside the generated PDF.
Where to goAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Enclosed File / Additional Email Attachment
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 this guide helps you do
Send one additional approved file alongside the generated PDF. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Select one PDF, PNG, JPG/JPEG, DOC or DOCX file.
- Verify the file is no larger than 25 MB.
- Send the letter.
- Go to Internal Full View and confirm the enclosure name, type, size and file link.
- Verify the recipient email contains both the generated PDF and enclosure.
Fields and options
Action scopeSend one additional approved file alongside the generated PDF.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Enclosed File / Additional Email Attachment
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- Only one additional file field is implemented.
- The generated PDF remains the primary attachment.
- Invalid enclosure upload does not stop the letter/PDF email flow; the module displays a warning and skips the enclosure.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.