Templates and content authoring

Apply a template to a client letter

Populate the client-letter subject and PDF body from a predefined template.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Predefined Templates

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

Populate the client-letter subject and PDF body from a predefined template. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Select the customer recipient.
Open Predefined Templates.
Search for and select a template.
Confirm Subject is populated.
Confirm the Letter PDF Content editor is populated.
Review and edit the copied values before sending.

Fields, choices and supported possibilities

Action scopePopulate the client-letter subject and PDF body from a predefined template.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Predefined Templates

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 selected option carries data-subject and data-letter-body attributes.
Selecting a template copies values into the form; it does not lock the fields or maintain a live link.

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.