—See scheduled, sending, sent and failed campaigns in month, week, day or list view, always in your organization’s time zone.
—Choose a time slot to start a campaign with its schedule already prepared for confirmation.
—Move a scheduled campaign to a new time by drag and drop, or from the keyboard; the old and new times are shown before anything changes.
v1.1.0
Help where the question is asked, and the documentation to back it.
Help and documentation
—A help system with two depths behind one icon: hover for a short panel, click for a modal that renders the real documentation page — never a copy of it.
—Contextual help on twelve screens: sending domain, topics, suppressions, invitations, segments, sequences, campaigns, import, contacts, sending preferences, statistics and plan limits.
—Twenty new documentation pages covering the whole product — audience, email, sending and settings — each one written to be readable inside the modal as well as on its own page.
Audience
—Editorial topics: a reader can decline one theme without unsubscribing from everything else. A campaign or a sequence carries at most one, and the refusal is applied at send time.
—Every contact now records where it came from — an import, the API, a sign-up form or a manual entry — along with the file or the key that created it.
Email
—The template screen became a workspace: editable from the moment it is created, with the preview alongside.
—One way to insert an image, whether it comes from the media library or from an address you paste.
—New merge tag {{today}}, resolved at send time in the sending organization’s language and time zone.
Campaigns
—Campaign settings are separated from the content editor: two steps instead of one crowded screen.
—Statistics: the metric and the granularity became two independent choices, with an hourly breakdown over the first 48 hours.
Under the hood
—Next.js 16.3.2, Node 24 LTS and Better Auth 1.7.1.
—Account, checkout and contact screens translated.
v1.0.0
Sequences became a versioned graph, and sending got its guardrails.
Sequences
—A journey is now a versioned graph. Publishing freezes a version, and contacts already on their way keep walking the one they entered on.
—A send step carries its own subject and content instead of pointing at a template.
—Steps that act on the contact rather than write to them: add a tag, remove a tag, end the journey.
—The number of sequences is capped by the plan — paused ones included, because they still exist.
Deliverability and domains
—A domain becomes usable only once the organization has proved it owns it, through a TXT challenge of its own.
—A sender address must belong to one of your verified domains; anything else is refused before a single email leaves.
—The sending setup reads as a checklist in plain words rather than as an error code.
—A pause imposed by the email provider blocks sending and notifies the organization instead of failing silently.
—Domains declared and never verified are purged on a schedule.
—Each organization sends under its own tenant, so one sender’s reputation no longer rides on another’s.
Application emails
—The fourteen application emails share one layout.
—They leave through Amazon SES, like everything else you send.
Elsewhere
—The limits shown are the ones actually enforced — no more marketing table next to a different reality.
—The dashboard shows today’s sign-ups and unsubscribes under their own window.
—The usage screen is back on, counting emails sent.