External-recipient correspondence

Generate an external PDF without emailing

Create the external history record and PDF when no recipient email is supplied.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → leave Email blank → Generate PDF & Email

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 external history record and PDF when no recipient email is supplied. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter sufficient recipient details for the intended record.
Leave Email blank.
Complete Subject and Letter PDF Content.
Select Generate PDF & Email.
Open Sent Letters History and verify the PDF.
Treat Email status as pending/not confirmed because no send was attempted.

Fields, choices and supported possibilities

Action scopeCreate the external history record and PDF when no recipient email is supplied.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → leave Email blank → Generate PDF & Email

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 inserts the history row and generates the PDF before checking target_email.
No email is sent when recipient_email is empty.

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.