Understand sender identity and personalised greeting
This guide explains that the sender fallback and fresh CRM name lookup used for each outgoing message. 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 goAutomatic queue delivery → SMTP
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What you’ll accomplish
Know the sender fallback and fresh CRM name lookup used for each outgoing message. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Configure a valid CRM SMTP sender address and company name.
- Keep recipient contact or lead names current.
- Send a controlled campaign and inspect the received greeting and sign-off.
Fields and options to review
Sender emailConfigured SMTP email; falls back to the company email and must validate.
Sender nameCompany name; falls back to Britixo.
GreetingFresh contact/lead name, then stored recipient name, then Valued Contact.
Sign-offBest regards followed by the configured company name.
Rules the system enforces
- Only values and transitions exposed by the supplied module code are supported.
- Server-side validation remains authoritative even when browser controls appear to accept a value.
How to confirm it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.