Existing-customer correspondence

Enter a client-letter subject

Provide the required subject used in the PDF box, email subject and history row.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Subject

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

Provide the required subject used in the PDF box, email subject and history row. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter a clear recipient-facing subject.
Review any subject copied from a template.
Keep confidential data out of the subject where email previews could expose it.
Continue to the PDF content.

Fields, choices and supported possibilities

Action scopeProvide the required subject used in the PDF box, email subject and history row.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Subject

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 browser input is required.
The email subject is formatted as [reference] Official Correspondence: subject.
The PDF renders the subject in uppercase inside a highlighted box.

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.