External-recipient correspondence

Enter external recipient name and company

Provide the person and organisation used for salutation and PDF receiver formatting.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Name / Company

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

Provide the person and organisation used for salutation and PDF receiver formatting. 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 person’s name when known.
Enter the organisation when applicable.
Review the generated receiver window before relying on the document.
Use at least one meaningful recipient identifier even though both fields are optional in the form.

Fields, choices and supported possibilities

Action scopeProvide the person and organisation used for salutation and PDF receiver formatting.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Name / Company

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

recipient_name and recipient_company are trimmed and stored.
The email salutation uses recipient_name first and recipient_company as fallback.

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.