Existing-customer correspondence

Write client-letter PDF content

Author the official letter body that is stored and rendered into the generated PDF.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Letter PDF Content

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

Author the official letter body that is stored and rendered into 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

Open or select the required content.
Write and format the body in TinyMCE.
Review names, dates, amounts, obligations and links.
Do not place a cover-note-only message here.
Send a controlled test when layout is important.

Fields, choices and supported possibilities

Action scopeAuthor the official letter body that is stored and rendered into the generated PDF.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Letter PDF Content

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 controller reads content with XSS filtering disabled to preserve HTML.
The stored HTML is rendered into the PDF.
The module does not provide server-side content completeness validation.

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.