Recipient email delivery overview
3 min read
Updated Apr 9, 2026
Recipient delivery is part of the workflow infrastructure, not just a decorative email feature. Invite, reminder, resend, voided, declined, and completed notifications all matter when you think about automation or support behavior.
Before you begin
A workflow that depends on recipient notifications
Awareness of the different delivery moments in the lifecycle
A need to explain delivery behavior to an operations or integration team
Know the delivery moments
Notifications cover invites, reminders, resends, voids, declines, and completion-related messages.
Those moments often define when downstream teams notice the workflow at all.
Treat delivery as tracked work
The backend tracks notification deliveries rather than pretending every email was delivered successfully.
That tracking matters when you troubleshoot or build process expectations around email.
Plan fallbacks
If a workflow is critical, decide what your team should do when the recipient needs resend or when delivery is skipped because a transport environment is unavailable.
Operational planning matters as much as the mail path itself.
Pro Tips
Do not assume every delivery issue is a platform outage.
Use reminder and resend intentionally based on the actual problem.
If email is business-critical, document who owns first-response support on your side.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.
Need more help?
Our support team is here to assist you.