Require an e-signature on a client letter
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 add the recipient Review & Sign link and track acceptance evidence.
Where to goAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Require Client to E-Sign this Document
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
Add the recipient Review & Sign link and track acceptance evidence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Select the signature checkbox.
- Complete the letter and send it.
- Verify the email contains Review & Sign Document.
- Monitor the signature icon in Sent Letters History.
- Go to Verify or Internal Full View after signing to review acceptance details.
Fields and options
Action scopeAdd the recipient Review & Sign link and track acceptance evidence.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads → Require Client to E-Sign this Document
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 checkbox stores require_signature=1.
- The email sign link uses the letter hash.
- The dashboard shows pending or signed status only when require_signature is set.
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.