tous les systèmes opérationnels · 99,98 % sur 90 jours
Nouveautés
Ce qui a changé dans le produit, du plus récent au plus ancien.
v1.5.0
Send a dated campaign series to your whole audience.
Series
—A **series** is a new shape of sequence: instead of following each contact from the moment they enter, it follows the calendar. You set a start date, and the whole audience receives dated steps together — a teaser on the 15th, the announcement on the 18th, a reminder on the 22nd.
—Nobody is enrolled in a series, and there is no per-contact clock: everyone is always on the same step.
—Build one in Sequences, on the new **Fixed date (Series)** tab. Same editor, same blocks as any sequence.
—Space the steps with ordinary **wait blocks**, in hours or days, exactly as in a sequence.
—Give a step a **send time** to fix the moment in the day — or leave it empty and the step goes out as soon as the wait has elapsed. A send time never moves a step earlier: if it has already passed, the step goes out the next day, and the editor says so.
—Move the whole series by changing its start date alone. No step needs rewriting.
—Each sending step goes out as its own campaign, named `<series name> · step N`, created on the day it is due.
—A step can act on a whole audience at once instead of writing to it: add a tag, remove a tag, or call a webhook with the batch.
—Target a step at the people who reacted to an earlier one — those it reached, those who opened it, or those who clicked in it. The screen names the step it refers to.
—If a step cannot go out — not enough balance, a domain no longer verified — the series pauses at that step and tells you which one and why, instead of failing silently.
Deliverability
—A **spam risk report** on a campaign, before you send it: an editorial read of the subject, the preview text and the body, plus the counts filters actually weigh — HTML weight, number of links and distinct domains, unsubscribe link, postal address, and the words you repeat.
—Eight editorial signals, in two families: how it is written (clickbait subject, artificial urgency, unsupported claims, and above all a subject that does not match the content), and what it is about (adult content, gambling, a phishing-like tone, crypto solicitation).
—Every signal is shown as a probability, never as a verdict — "probable, 81%", not "your subject is clickbait" — and the report says when it is itself unsure.
—A level for the campaign and for each of its three elements. The header takes the worst, and names the element that pulled it up so the two never contradict each other on screen.
—It is advice, never a gate: nothing is written into the campaign, and no result has ever stopped a send.
—Each run spends one analysis credit; a run that fails is refunded.
Campaigns
—A new **Series** tab in the campaign list shows the steps that have not gone out yet, with the date each one is due. It answers the question the calendar already answered and the list did not.
—An upcoming step is a forecast, not a campaign: it carries no actions, and clicking it takes you to its series, where the dates are set.
Email
—A new email step in a sequence now starts from a ready-made template instead of a blank page — presentable as it is, with the unsubscribe link already in place.
Documentation
—A new page, **How a series works**, and a clear answer to the question the three words raise: what a campaign, a sequence and a series each are, and when each one is the right tool — with a screenshot of each canvas side by side.
—A new page on the **spam risk report**: what it looks at, what a probability means, and the three things it cannot tell you.
—Contextual help on the campaign and sequence screens opens that explanation without leaving the page.
v1.4.0
Collect subscribers without writing a line of code.
Sign-up pages
—Publish a hosted sign-up page for any list — a real web address you can share, with no code, no embed script and no API key to hand out.
—Pick a design from a catalogue of fifteen templates, from a plain centred card to a full-colour split screen, a four-cell grid or an oversized headline. Or paste your own HTML.
—Set the page in a few named fields: hero title, subtitle, button label, success message. It is not a page builder — there is nothing to drag.
—Collect the email address, and optionally a first and last name.
—Choose what happens after someone signs up: show a message on the page, or redirect them to an address of your own.
—Keep pages as drafts until you are ready; a draft page is not served.
—Publishing is off until you turn it on, organisation-wide. Turn it off and every sign-up page stops being served immediately.
—Your existing double opt-in setting applies: if you require confirmation, sign-ups from a page get the same confirmation email as anywhere else.
—Every page carries your postal address, and the “Sent with AgentsMail” line — remove that shortcode from the HTML and it is gone.
—Duplicate a page to start a variant from an existing one.
Audience
—Contacts who arrive through a sign-up page are recorded with `signup_form` as their source, so you can tell them apart from imports and API additions.
API
—New endpoints to create, read, update and delete sign-up pages, and to read the published template catalogue.
v1.3.0
Sent campaigns get a public home, and a pause button.
Campaigns
—Read any sent campaign again from its stats page, exactly as it went out, without reopening an editor.
—Turn on “Publish sent campaigns” in your settings to give every sent campaign a public web address you can share. Turning it off makes those addresses disappear immediately.
—Pause a scheduled campaign without losing its time slot, then resume it — or, if the time has passed, pick a new one.
—Cancel a campaign that is already sending, and get the unused emails back.
—Scheduling is refused up front when your balance does not cover the audience, with the figures shown rather than a passing notification.
—The calendar now works on a phone, with a list view and a view picker.
Audience
—Contacts manage their own first name, last name and topic choices from a private link — and can come back on a topic they had refused.
—Manage a contact’s topic opt-outs from their detail page, and resubscribe them when they ask.
—Re-enroll a contact in a sequence they have already completed.
—See who finished a sequence, step by step.
Email
—Write the preview text that appears next to your subject line in the inbox, on campaigns as well as on sequence steps, with a character counter as you type. The ten catalogue templates carry it, and it never shows up in the plain-text version.
—Press Enter twice in the visual editor to leave a real blank line — it now survives saving, reloading and the recipient’s inbox, whichever template you started from.
—Add images faster: optional compression before upload, a queue with a preview, and a keep-or-drop decision per file.
Reporting
—Receive a daily report of everything your campaigns sent, at the hour you choose.
—Hourly campaign statistics are anchored on when a send started, so the curve matches what happened.
API
—Manage editorial topics through the API: list, create, rename and delete. Campaigns and sequence steps report the topic they belong to.
—Upload, list and delete media library files through the API.
Billing
—Buy the emails you are missing when a send exceeds your plan, without changing plan.
—A custom email allowance granted to your organization is now credited again every period, on top of your plan — previously it was granted only once.
Under the hood
—Interrupted campaign sends resume on their own, and sends are paced to stay within the sending limits of the platform.
—Reservations left behind by an interrupted send are arbitrated instead of holding your balance.
v1.2.0
Campaign planning now has a calendar of its own.
Campaigns
—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.