Existing-customer correspondence

Understand client recipient data sourcing

Distinguish customer-linked data from external-recipient snapshot fields.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → create/open a client-linked letter

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

Distinguish customer-linked data from external-recipient snapshot fields. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm the customer company and primary contact before generation.
Open the generated PDF and public verify page to confirm the intended receiver.
Use Internal Full View to distinguish stored fields from customer-derived display data.

Fields, choices and supported possibilities

Action scopeDistinguish customer-linked data from external-recipient snapshot fields.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → create/open a client-linked letter

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

Client-linked send payload stores client_id, subject, content, signature option and optional email assets; it does not populate the external recipient fields.
Public verification may query the current client/company and primary contact for receiver display.
Changes to CRM customer data after generation can therefore affect some live display contexts even though the PDF file remains the generated snapshot.

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.