Existing-customer correspondence

Handle a customer without a primary-contact email

Generate the record and PDF while recognising that the module cannot send the email without a target address.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Customers → Open customer → Contacts; then Letter Manager → Dashboard

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

Generate the record and PDF while recognising that the module cannot send the email without a target address. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open the customer and create or correct the primary contact email.
Return to Letter Manager and send or resend the letter.
If the original record already exists, use Resend Email after the contact is corrected.
Confirm Email Sent changes only after a successful send.

Fields, choices and supported possibilities

Action scopeGenerate the record and PDF while recognising that the module cannot send the email without a target address.

Module version1.0.0

Exact routeAdmin Area → Customers → Open customer → Contacts; then Letter Manager → Dashboard

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

When no target email is available, generate_and_send writes a missing_target_email diagnostic and does not call the email send.
The PDF and history row may still exist.

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.