Templates and content authoring

Create a Letter Manager template

Save a reusable internal name, letter subject and HTML body. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Templates → New Template

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 you’ll accomplish

Save a reusable internal name, letter subject and HTML body. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Go to Letter Manager → Templates.
Select New Template.
Enter Template Name (Internal Use).
Enter Letter Subject.
Write the Letter Content in the TinyMCE editor.
Select Save and verify the template appears in the table.

Fields and options to review

Template NameRequired by the form and used in the template selector.

Letter SubjectRequired by the form and copied to the send form.

Letter ContentHTML body copied to the PDF-content editor.

Rules the system enforces

Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
Browser controls are not a substitute for server-side and operational verification.

How to confirm 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.

Was this guide useful?Your response is stored only in this browser.