Email delivery, attachments and read receipts

Understand the generated PDF email attachment

Confirm every email attempt attaches the current reference-based PDF.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationSend or resend a letter → recipient email attachments

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

Confirm every email attempt attaches the current reference-based PDF. 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 received email.
Confirm Letter_{reference}.pdf is attached.
Open it and compare reference and subject with the history row.
Report a missing or corrupt PDF before relying on delivery status.

Fields, choices and supported possibilities

Action scopeConfirm every email attempt attaches the current reference-based PDF.

Module version1.0.0

Exact routeSend or resend a letter → recipient email attachments

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 generated PDF is attached before the optional enclosure.

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.