Existing-customer correspondence

Select an existing customer recipient

Follow this guide to use the live-search selector populated from CRM customer companies and primary-contact email addresses. 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 → Dashboard → Search Clients & Leads → Select Recipient
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

Use the live-search selector populated from CRM customer companies and primary-contact email addresses. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

  1. Go to the recipient dropdown.
  2. Search by company name or the email shown in the option label.
  3. Select the intended [Client] entry.
  4. Verify the correct company before authoring or sending.

Fields and options to review

Action scopeUse the live-search selector populated from CRM customer companies and primary-contact email addresses.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Select Recipient
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

  • The option value uses client_{userid}.
  • The controller extracts the numeric segment and stores it as client_id.

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.