Emails
Emails
Library, draft vs confirm, lint, and how documents are versioned.
Every email in Audryo — Journey step, campaign, transactional template, or library draft — is the same message document: versioned, linted, and confirmed before anything customer-facing goes out.
This page is the map. Detail lives in the pages below.
In the product
Open Emails (Content) for the library, or open a step / campaign to edit in context. Cards sort by last edited. Hover a card for Edit (and on templates, Use for email).
Two tabs:
- Emails — documents you send. Language chips, assignment (library /
campaign / journey / system), delivery metrics.
- Templates — brand base, lifecycle library, team layouts. See
System mail (double opt-in) is protected; duplicate/delete may be hidden.
Lifecycle of a document
- Create (blank brand scaffold, template, or Ask AI).
- Edit on the canvas.
- Save draft while iterating (
proposed). - Send test to yourself.
- Confirm — immutable version journeys/campaigns actually send.
- Later edits create a new draft off the tip of the lineage, not a
silent rewrite of history.
Publish state in the toolbar follows the newest non-rejected revision. If Confirm looks like a no-op, you are often still looking at an older URL; the app redirects to the current tip.
Rules that fail closed
- Marketing layouts need a heading, a real button URL, and a footer.
- Merge tags with broken filters are linted on revise.
- Image
srcvalues should be project assets or bundled icons
(audryo-icon:…), not disposable CDN guesses.
- AI copy may only claim confirmed Foundation facts.
Languages
Each lineage can have en and de documents. Confirm every enabled locale before activating a Journey. See Localization.