Enter external recipient name and company
Provide the person and organisation used for salutation and PDF receiver formatting. 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 → Letter Manager → Dashboard → Manual Entry (External) → Name / Company
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
Provide the person and organisation used for salutation and PDF receiver formatting. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Enter the person’s name when known.
- Enter the organisation when applicable.
- Check the generated receiver window before relying on the document.
- Use at least one meaningful recipient identifier even though both fields are optional in the form.
Fields and options to review
Action scopeProvide the person and organisation used for salutation and PDF receiver formatting.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Manual Entry (External) → Name / Company
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
- recipient_name and recipient_company are trimmed and stored.
- The email salutation uses recipient_name first and recipient_company as fallback.
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.