Email delivery, attachments and read receipts

Interpret read count and timestamps

Review first open, last open and total detected image requests.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Internal Full View; or customer profile → Letter History

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

Review first open, last open and total detected image requests. 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 letter’s Internal Full View.
Review Email Open Count.
Review First Opened At and Last Opened At.
Compare repeated opens with the detailed email-open table when authorised.
Do not equate open count with unique human readers.

Fields, choices and supported possibilities

Action scopeReview first open, last open and total detected image requests.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Internal Full View; or customer profile → Letter History

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

Every valid pixel request increments email_open_count.
The first timestamp is set only when previously empty.
The opens table retains one event row per detected request.

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.