External-recipient correspondence

Enter external recipient phone and email

Store contact details and provide the target address for email delivery.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

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

Store contact details and provide the target address for email delivery. 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 contact number when required for the record.
Enter a valid email when the letter must be emailed.
Recheck the email because the module uses it directly as target_email.
Leave email blank only when a PDF-only record is intended.

Fields, choices and supported possibilities

Action scopeStore contact details and provide the target address for email delivery.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Contact Number / 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 email input uses browser type=email but the controller applies no additional server-side format validation.
recipient_phone is stored but not used for delivery.

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.