Get started
Types of emails
Campaigns, Journeys, and transactional sends — when to use each.
Audryo sends three kinds of customer email. Picking the right one keeps consent and deliverability honest — and it's usually obvious once you ask who's actually triggering the send.
| Type | Who triggers it | Who receives it | Best for |
|---|---|---|---|
| Campaign | You, right now (or on a schedule) | Everyone currently in an audience | Newsletters, launches, one-time announcements |
| Journey | Someone joining an audience, or an event over time | Contacts as they individually qualify | Onboarding, reactivation, nurture sequences |
| Transactional | Your product, for one specific action | One recipient at a time | Receipts, invites, password resets |
Rule of thumb: "Something happened for this one person" → transactional. "Tell this whole segment something now" → campaign. "Guide people through a path over days" → Journey.
Campaigns
A one-shot send to an audience snapshot. Membership isn't re-checked after the send starts — someone who joins the segment afterward doesn't get it unless you send again. See Campaigns.
Journeys
A lifecycle sequence: entry rule, steps (email, wait, branch, exit, update a field), a conversion goal, and built-in safety rules around consent and how often someone can be messaged. The structure and the email copy are reviewed separately, so you can approve the shape of a journey without also having to bless AI-written copy in the same breath. See Journeys.
Transactional
One-to-one, triggered by your product the moment something happens — someone resets their password, places an order, gets invited to a team. You confirm the email template once; your product tells Audryo when to send it and who to. Never route promotional content through this path — it's meant for things people expect regardless of marketing consent, not a way around it.
Communication class
Every Journey and campaign is labeled with a communication class, and Audryo enforces the matching consent rule:
| Class | Typical content | Consent |
|---|---|---|
marketing | Promos, win-back, upsell | Explicit marketing grant |
newsletter | Recurring editorial | Newsletter grant |
product_service | Product updates you disclosed | Product-updates grant |
operational | Account notices that are not marketing | Suppressions still apply |
transactional | Receipts, resets, invites | Suppressions still apply; not a promo loophole |
Mislabeling a sale as operational is not a silent escape hatch. Eligibility fails closed. Pick the class that honestly describes the content.
One editor, everywhere
All three types share the email editor — blocks, locales, draft/confirm, test sends. Campaigns and Journeys reference a confirmed document. Transactional send references it by id from your backend, with Idempotency-Key.