Build email templates your whole team can use, with variables, previews and version history.
AI drafts subject lines and copy variants; your team approves what ships.
Subject: Your order {{order_id}} has shipped
Hi {{first_name}},
Good news. Your order is on its way.
Track it here: {{tracking_url}}
{{#if gift}}This order includes a gift note.{{/if}}
Work visually or in code, whichever fits the author.
Personalise content and show blocks conditionally.
Every change is saved and can be restored.
Check rendering before anything goes live.
Share headers, footers and legal text.
Keep brands and clients separate.
Start blank or from a base layout.
Mark the parts that change per message.
Call the template from the API or SMTP headers.
Switch between stages to see what you control at each step. Illustrative interface with sample data.
Marketing and support can edit content while engineering keeps the sending logic untouched.
Create an order-shipped template with order number, tracking link and an optional gift note. Your code sends the name and variables, and copy tweaks never need a deploy.
Let the marketing team update promotional wording and imagery in the editor, publish when approved, and leave engineering free of requests for small text changes.
Keep each client's brand blocks and templates in a separate workspace library, so headers, footers and legal text never leak between accounts. Brand elements stay in their own space and remain easy to find later.
If a published change breaks rendering, open the version list and restore the previous version. Messages sent afterwards use the restored template immediately. Nobody needs a code deployment to revert a change.
Give the assistant a goal and audience and it proposes several subject lines and preheaders. You choose, edit or discard; nothing is saved to a live template without your approval.
Highlight a paragraph and ask for shorter, clearer or more formal wording. The assistant shows its edit as a suggestion that you accept or reject, preserving your variables.
A copilot checks a template for broken variables, missing alt text, heavy images and phrases that commonly trigger spam filters, then lists fixes. You decide which to apply.
For campaign-style sends, models suggest delivery windows based on past engagement of your own audience. Suggestions are optional, and you can keep a fixed schedule.
AI features are assistive: they propose wording and checks, and your team reviews and publishes every template. [Confirm which AI features are available at launch.]
Multipart messages with a sensible text version look more legitimate to filters and work better for accessibility. Generate it from HTML, then edit by hand.
If a first name is missing, an empty greeting looks broken. Define a fallback such as a neutral salutation for every personalised field.
Test with long names, missing values and unusual characters. Edge cases are where layouts and conditions most often fail.
Edit in draft, send a test to yourself, and publish only after review. Role-based rights make this a rule rather than a habit.
Avoid image-only emails and oversized files. Check rendering in the clients your audience uses, since support for CSS differs widely.
An email template is a saved email layout with placeholders, called variables, that are replaced with real values when a message is sent. It lets you write the design and wording once, then send many personalised messages from code or a campaign.
Create the template, mark its variables, then call it by name from the API with values for each variable, or reference it in SMTP headers. The system renders the template and delivers the message. See the API reference for fields.
[Confirm templating syntax and document it here.] The editor supports variables and conditional blocks, and previews with sample data show the rendered result before you publish. Document variables in the template description so authors know what each placeholder means, and test conditional blocks with sample data that triggers each branch.
Yes. Paste or upload your HTML and add variables where content should change. Review the preview, check the plain-text version, and send a test before using the template in production. Generate a plain-text part and review it too, because the two versions should say the same thing and both appear in tests.
A template is reusable content and layout. A campaign or send is an instance of that content going to specific recipients at a point in time. One template can power many sends, so improving it improves all of them. Review the result carefully before publishing.
Yes. Every saved change creates a version, and you can restore an earlier one. Messages sent after the restore use the restored version, while earlier messages are unaffected. Rollback is useful when a late edit breaks a layout. Compare versions side by side first to be sure you restore the one you want to keep.
AI can suggest subject lines, tighten copy, review a template for broken variables and spam-prone phrasing, and recommend send times. All output is a suggestion your team reviews, edits and publishes. [Confirm which AI features are available at launch.] Nothing goes live until you publish it.
Yes. Role-based rights let marketers and support staff edit and, if you allow it, publish content, while developers retain control of API keys and sending logic. Draft and published versions keep unfinished work away from live sends. Drafts stay private until they are published.
Yes. Paste or upload HTML and add variables where you need them.
A plain-text part can be generated from the HTML or edited by hand.
Create an account, add your domain and send your first email.