Broadcasts
Send to the whole list or a saved filter. Schedule it, send yourself a test first, and let the system pick the winning subject line.
Broadcasts, sequences and automations in the same system as the courses and the payments. No sync, no webhook that goes quiet.
I want to create with IdunA relationship that keeps going
Illustrative workflow. No real customer data.
Broadcasts, multi-step sequences and automations triggered by purchases, tags and course progress — in the same system as everything else.
Send to the whole list or a saved filter. Schedule it, send yourself a test first, and let the system pick the winning subject line.
Multi-step flows with delays between the emails, triggered by what actually happens — a purchase, a tag, a sign-up.
Purchases, tags, course progress and other workspace events can start a flow that sends, waits, grants access or branches.
Mail goes from the platform address with you as the reply-to until a sender domain is verified. Studio never shows a sender as verified when it is not.
When someone buys your course, the email system knows immediately — not because a webhook was sent and hopefully arrived, but because the purchase and the mailing list are in the same database.
That sounds technical and shows up practically: a saved filter that says “bought Course A but hasn’t started module 2” is correct the moment you look at it. No sync delay, no “my email tool has a different subscriber count than my course platform”.
A broadcast is a one-off email to your whole list or a saved filter. You build it from blocks, see a preview, and send yourself a test before it goes out.
You can schedule it for a time, cancel a scheduled send, and test two subject lines against each other and let the system send the winner to the rest.
The builder needs a computer, like every builder surface.
A sequence is several emails with delays between them, started by something that happens: someone buys, gets a tag, fills in a form. You write the emails once and they go out for every new person, at the right pace counted from when they entered.
Automations are the wider tool: workspace events can start a flow, and the flow can send an email, add or remove a tag, grant access, wait a number of hours or branch on a condition.
This is where you build what the platform doesn’t do for you automatically. Your own timings for abandoned checkouts, a note to yourself when someone books, a tag when someone finishes a module.
Under Email › Sender & deliverability you see which address your mail goes out from. Sending from your own domain requires that domain to be verified with SPF and DKIM records, and during the beta it is not available for every workspace.
What matters most about this feature is what happens before it’s done: while the domain is unverified, mail goes out from the platform address with your address as reply-to. We don’t pretend your sender is verified when it isn’t — mail that looks forged to Gmail lands in spam, and you only find out when nobody replies.
If you already have your own mail account or a Resend key, you can use that instead.
Every email measures opens and clicks. Opens are counted with a pixel, clicks through a signed link that logs the click and then forwards.
In the stats you see delivered, bounced and failed, open rate, how many of those who opened also clicked, which links got the clicks, and for a sequence: which step loses people.
Your list is contacts and members in one view. You tag them, save the filters you use often, import from CSV, and see each person’s timeline: purchases, course progress, emails, bookings.
The first places open soon. The waitlist hears first and the price is SEK 1,000/month excl. VAT.