Resend a Letter Manager email
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Regenerate the PDF and attempt delivery again using the record’s target rules.
Where to goAdmin Area → Letter Manager → Sent Letters History → Resend Email icon
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
Regenerate the PDF and attempt delivery again using the record’s target rules. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Verify the current primary-contact or external email is correct.
- Go to Internal Full View and verify the record.
- Select Resend Email.
- Wait for the success alert.
- Check Email Sent At, Email Sent To and read-receipt state.
Fields and options
Action scopeRegenerate the PDF and attempt delivery again using the record’s target rules.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Sent Letters History → Resend Email icon
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- The route takes the letter ID and reruns generate_and_send.
- The controller displays a success alert regardless of the underlying send boolean; verify the stored Email Sent value.
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.
Important code-backed limitationDo not rely on the success alert alone. Confirm Email Sent and delivery evidence because the resend action does not expose the email library result directly.
Related guides
Was this guide useful?Your response is stored only in this browser.