External-recipient correspondence

Require an e-signature on an external letter

Send a public signature link to the external email recipient.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Require Recipient to E-Sign this Document

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

Send a public signature link to the external email recipient. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter a valid recipient email.
Select the signature checkbox.
Generate and email the letter.
Ask the recipient to use the Review & Sign Document link.
Review the signed state and acceptance evidence.

Fields, choices and supported possibilities

Action scopeSend a public signature link to the external email recipient.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Require Recipient to E-Sign this Document

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

A signature link is added to the email only when require_signature=1.
If no email is supplied, the record still receives a hash but the module cannot deliver the signature link automatically.

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.