Understand primary-contact email delivery
This guide explains that which customer contact receives a client-linked letter. 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.
Where to goAdmin Area → Customers → Open customer → Contacts; then Letter Manager → Dashboard
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
Know which customer contact receives a client-linked letter. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to the customer and confirm the correct primary contact.
- Verify that contact has the intended email address.
- Return to Letter Manager and send the letter.
- Check Email / Read Receipt and the internal full view for Email Sent To.
Fields and options to review
Action scopeKnow which customer contact receives a client-linked letter.
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.
Rules the system enforces
- generate_and_send calls get_primary_contact_user_id(client_id).
- The primary contact email becomes the target; the customer’s general company email is not used as a fallback in this flow.
- The primary contact first and last name are used for the email salutation.
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.