Configure email delivery for Letter Manager
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use the CRM SMTP/company email settings that the module reads when sending.
Where to goAdmin Area → Setup → Settings → Email / SMTP
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 this guide helps you do
Use the CRM SMTP/company email settings that the module reads when sending. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Configure and test the CRM SMTP transport.
- Set smtp_email or company_email.
- Set companyname for the sender label.
- Send a controlled Letter Manager test.
- Check Email Sent, Email Sent To and Email Sent At in Internal Full View.
Fields and options
Action scopeUse the CRM SMTP/company email settings that the module reads when sending.
Module version1.0.0
Exact routeAdmin Area → Setup → Settings → Email / SMTP
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- from_email uses smtp_email first and company_email as fallback.
- from_name uses companyname and falls back to Pixie CRM.
- Letter Manager uses the host email library and does not provide separate SMTP credentials.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.