Email Studio
Build an e-mail from blocks or from a brief, review it with your team, send it to an audience, and read how it did – all on the same document.
Build
Blocks on the left, the canvas in the middle, settings on the right. The header carries the e-mail itself: its name (click to rename), its review status, the brand it belongs to, and Send and Save. The chevron next to the name opens recent e-mails, a new one, or the template gallery. AI Generate, on the canvas toolbar, drafts a whole e-mail from your brief in your brand's voice. It writes from what your brand profile says – what the business is, what it sells, what sets it apart, who it serves and the problems they have – and from your brief, and from nothing else: a price, a discount, a deadline or a customer quote appears only when you give it. The more the brief says, the more specific the e-mail. Each block can be rewritten on its own; whatever a block needs that the AI does not know goes in [square brackets] for you to fill in. Where a picture helps, the AI places a picture slot and describes what it shows; click Generate on the slot (or describe a picture in any Image block's settings) and it is drawn in your brand's style at the size the e-mail shows it. The e-mail carries a light JPEG copy; the full-size original is kept in your library. A slot you never generate is left out of the e-mail, and the Quality tab says so. Every draft gets a second, editing pass before you see it: it keeps one idea and one call to action and cuts to the length that type of e-mail needs. The template gallery's templates are written the same way; what only you know – a product, an offer, a date, a code – is in [square brackets], your brand's name is filled in, and the Quality tab counts what is still to fill. The Logo block and the Header block use your brand logo by default (see Your logo under Personalizing your messages). Personalize inserts fields and smart blocks; Display Condition shows a block only to people it applies to. Every save keeps a version under History and puts a copy in your library, where journeys and the rest of the platform find it.
Email tab: To, Subject, Sends from
To is the audience this e-mail goes to – one of your audiences from Customer Intelligence → Audiences. It is saved with the e-mail, and Send starts from it. Sends from shows the identity a real send uses: your connected domain or your managed sending domain. It is not typed per e-mail; change it under Connections → E-mail sending. With no verified identity connected, a real send does not go out.
Subject and preheader
As you type, the Email tab checks the subject and preheader against what inboxes and spam filters do, and says what it finds under each field:
- Fix – a fake "RE:" or "FW:", a placeholder like
[Product name]still in the text, repeated "!!" or "??". - Consider – a subject over 50 characters (with the words a phone
actually shows), words in capitals, an exclamation mark, more than one
emoji, words spam filters weigh, a
{{p.first_name}}token with no fallback; a missing, short or long preheader, or one that repeats the subject.
Below the fields, the e-mail is shown as a phone inbox lists it: sender, subject and preheader. There is no score and no predicted open rate – nobody can know an open rate before the send.
The preheader is the line an inbox shows after the subject. It goes out
hidden at the very top of the e-mail, followed by invisible spacing so the
first words of the e-mail do not run on into it, with its
{{p.first_name}} and {{brand.name}} tokens filled like the subject's.
That is true of every send – a journey, a test, the API. When the e-mail's
own HTML already opens with a hidden preview line (an imported design or
one written in code often does), that line is kept and no second one is
added.
Suggest writes alternatives. Use it puts one in the subject; Test it against the current subject opens Send with it as a second subject.
Your subjects that got opened most lists this brand's own subjects from journey and API sends to 20 or more people, with how often each was opened and clicked. Tests and service e-mails are left out. Apple Mail opens some e-mail on its own, so compare your subjects with each other, and treat clicks as the steadier signal.
Style: your brand's colours
Apply [brand]'s colours puts the brand's primary colour on every button (including the hero button), the secondary on dividers and the accent on countdown timers, and switches headers to the brand logo. It tells you what it changed. The Primary and Secondary pickers below do the same for a colour you choose. Set the brand's colours under Brand.
Quality
The Quality tab checks the e-mail before it ships: deliverability
(spam words, image-to-text ratio, link count, size, subject and
preheader, the unsubscribe link), accessibility (alt text, contrast, font
size, link text, touch targets), and Links – placeholders, empty
buttons, http where https exists, tokens inside a URL. Clicks are
attributed when the e-mail is sent; there are no tracking codes to add.
Review
The Review tab carries the e-mail's status – Draft, In review, Changes requested, Approved – and the comment thread your library uses: @-mention a teammate, reply, resolve; mentions ring the bell. Anyone who can manage the brand can approve or request changes. A marketing send needs an approved e-mail.
Approval is off by default – Send goes straight to the audience, and Review is optional feedback. A brand that wants a gate turns it on under Brand → Messaging → Review & approval: choose the people who approve, or leave it to everyone who can manage the brand (its owner and the organization's owners, admins and managers), and decide whether creators may approve their own e-mails. The studio names the reviewers before you click. Each gets a notification in their bell (and by e-mail, if they turned Email me my notifications on in Settings) that opens the e-mail on the Review tab, and you get the verdict back the same way. A reviewer sending their own e-mail sees Approve & continue instead – one click.
Send
Send is a one-off send: everyone in the To audience gets this e-mail once. It opens the e-mail as a one-step journey – the audience enters, the e-mail goes out. Publish it there, send yourself a test from the e-mail step, then Run now sends to everyone in the audience. Suppressions, the blacklist and your plan's allowance apply; every send is logged. Send Test Email under More sends one copy to one inbox at any time, from your own sending identity or The AI CMO's.
Test a second subject in Send writes subject B next to the current one. The journey then opens with a 50/50 split: half the audience, picked at random, gets the e-mail under subject A, and the other half gets it under B. The e-mail is the same. Each e-mail step shows its subject, and a test from either step uses that step's subject. Once the sends are in, Experiments shows which subject was opened and clicked more. In any journey, an e-mail step that uses an e-mail from your library has an optional Subject for this step field. Leave it empty to send with the e-mail's own subject.
Recurring or multi-step e-mails – a welcome series, a monthly newsletter, a win-back sequence – are journeys. Use in a journey under More opens the journey builder with this e-mail as a step; you choose the trigger (a lifecycle stage, an event, an audience) and the timing there.
Performance
Once a journey has sent the e-mail, History shows sends, opens and clicks per journey, from your sending provider's reports. Tests are left out.