Existing-customer correspondence

Attach one enclosed file to a client letter

Send one additional approved file alongside the generated PDF.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Enclosed File / Additional Email Attachment

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

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.

Exact step-by-step process

Select one PDF, PNG, JPG/JPEG, DOC or DOCX file.
Confirm the file is no larger than 25 MB.
Send the letter.
Open Internal Full View and confirm the enclosure name, type, size and file link.
Confirm the recipient email contains both the generated PDF and enclosure.

Fields, choices and supported possibilities

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.

Code-backed validations and workflow rules

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.

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.