Communication and operations
Transactional emails you can change without a developer.
Block templates for confirmations, reminders, and notifications with versions, preview, and publishing. Conditions decide who it's sent to and from where, so one email can serve multiple brands and markets.
What the template can do
Blocks instead of code
Text, button, order summary. It's assembled the same way as a page in the CMS.
Versions and preview
The change shows up in the preview first and is published as a version. Sent messages remain unchanged.
Conditions
Brand, language, or customer type decides which variant is sent and from which address.
What this solves in practice
Text change in five minutes
Editing an order confirmation doesn't mean waiting for a new e-shop version to be deployed.
Language based on the customer
Texts go through Translations, so a new market doesn't mean a new set of templates.
Look based on the brand
The email takes its logo, colours and font from the Brand Catalogue, not from an email attachment.
Traceability
For every sent message, you can see which template version it was created from.
What you need
List of situations
When to write to the customer. Usually there are fewer than expected.
Domain for sending
Emails come from your address, not from ours.
Texts
Just the ones you send today are enough. Templates are built based on them.
Frequently asked questions
Can we manage the templates ourselves?
Yes, that's exactly what the editor is for. Publishing is an extra step, so an unfinished change won't be sent to anyone by mistake.
Do emails come from our domain?
Yes. They are sent through the platform's mail infrastructure under your domain and with the verification records that belong to it.
Can it handle an exception for one market?
There are conditions for that. One template can have a variant for a market, brand or customer type, without creating a second set.
Send us your order confirmation
We'll turn it into a template and you'll see it in your colours and in a different language too.