Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Sent-letter history and staff actions

Interpret Registered and External letter status

Distinguish customer-linked records from manual external entries. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0
Jump to steps
Where to goAdmin Area → Letter Manager → Sent Letters History → Status
Before you start
  • 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 you’ll accomplish

Distinguish customer-linked records from manual external entries. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

  1. Read Registered when the row has client_id greater than zero.
  2. Read External when client_id is zero.
  3. Go to Internal Full View for the source fields.

Fields and options to review

Action scopeDistinguish customer-linked records from manual external entries.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History → Status
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules the system enforces

  • These badges describe recipient source, not delivery, signature or legal status.

How to confirm it worked

  • 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.
Letter Manager module overviewSearch Sent Letters HistoryPage through Sent Letters HistoryInterpret recipient name and company in historyOpen the Letter Manager Internal Full ViewCopy a letter reference from Internal Full ViewConfigure SMTP email deliveryAdd and manage customer contactsClient portal overview