Operational guidance for the full Envoi workflow.
Use this page as the quick orientation layer for templates, campaigns, flows, SMS, and approval-heavy messaging teams.
Build emails by hand first
Templates should always be fully editable without AI. Teams need typography, spacing, image, button, HTML, and global styling controls before they need generation.
Flows should execute from real triggers
A usable automation product has to move past CRUD. Trigger sources, delays, branches, approvals, and queue execution all need to map to actual customer events and visible logs.
SMS needs operational readiness
SMS is not just copy and audience selection. It starts with a real sender number, default routing, and registration or compliance data before teams can rely on it.
AI stays assistive
Envoi should let AI accelerate drafts, variants, and recommendations while preserving the manual path. Humans stay in control for approvals, risk, and brand decisions.
Preview before you trust
The highest-friction failure in email tools is visual mismatch. The editor, preview output, and delivered HTML should be treated as separate checkpoints with deliberate QA.