External-recipient correspondence

Write an external letter subject and content

Create the recipient-facing subject and official PDF body for a non-customer record.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Subject / 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

Create the recipient-facing subject and official PDF body for a non-customer record. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter the required Subject.
Write or review the Letter PDF Content.
Confirm names and addresses match the external fields.
Preview by generating a controlled test when layout is material.

Fields, choices and supported possibilities

Action scopeCreate the recipient-facing subject and official PDF body for a non-customer record.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Subject / 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

Subject is browser-required.
The content editor is not marked required by the supplied view.
The server does not reject a blank content value explicitly.

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.