Report · 1 September 2026
Email campaigns, explained: one email, written once, sent once
Some news cannot wait for a schedule. The exhibition got a date. The workshop opened for booking. The price changes on Friday. That is what an email campaign is for: one email, written once, sent once, to the people who asked to hear from you.
Most email tools treat this as a design problem and hand you a template editor. The harder problems are the ones they leave to you: who may lawfully receive the email, whether the thing you approved is the thing that gets sent, and what stands between a tired click and a message to the wrong two thousand people. This piece explains how bernard answers those, in order. There is a four minute film of the same story above, shot on a real site.
A campaign is not a journey
Your site sends two kinds of email, and they are different machines.
A journey is a standing rule. Someone buys, the thank-you goes out. Someone subscribes, the welcome goes out. You approve the words once, switch the rule on, and it runs by itself from then on.
A campaign is the opposite shape: a single email at a moment you pick. News is a campaign. Welcomes are journeys. Keeping the two separate matters, because the safety a campaign needs, a named audience, an exact count, a final quote, would be pure friction on an automatic thank-you, and the set-and-forget nature of a journey would be reckless for news.
Who can hear from you
A campaign only ever goes to people with a real yes on record: your buyers, your students, and the sign-ups who ticked the consent box on a form and then pressed the button in their confirmation email. The tick alone is not the yes. The click is the yes, and the exact wording each person agreed to is kept as evidence.
Ask who a campaign could go to and Bernard counts each audience for you, live. The count is honest in a specific way: it is the people who can lawfully receive the email today, not everyone whose address you happen to hold. If your contact book says forty and your audience says twelve, the gap is not a fault. It is the difference between a record and a permission.
The draft, and the templates
Tell Bernard what is happening in one sentence and back comes an email in your voice, written from what it knows of your site. Edit it, ask for another go, or put it aside. Saving a draft sends nothing at all. And if you have not given it the facts, the date, the venue, the link, it asks rather than inventing them.
If you send the same sort of note every month, keep a reusable template: the shape of the email with named blanks for the details that change. Bernard shows you an example with the blanks filled in with clearly labelled sample details, so what you approve is what readers will actually see, not a form full of holes. Two things a template is not: it is not a mailing list, and it is not permission to send. Every version has a fingerprint you approve before it is saved, and a campaign made from a template takes its own snapshot, so editing the template later never rewrites something you already sent.
The quote
This is the part most tools skip, and it is the reason a bernard campaign is hard to regret. Before anything sends, you are shown a quote: the exact email, rendered the same way it will be delivered, its version, and exactly how many people it goes to, with the audience named. Nothing leaves until you approve that quote. If one word or one eligible recipient changes while you are deciding, the old approval is refused and you are quoted again.
Most tools just send. Bernard stops.
The honest edges
Two more things, said plainly because they are the kind of thing owners find out the hard way elsewhere. There is a monthly sending allowance, there to protect your sending reputation; a campaign that would go over it is declined whole, never trimmed to a random slice of your list. And once an email has genuinely left for delivery, it cannot be pulled back, so Bernard tells you honestly what has already gone rather than pretending a recall exists.
The other half of this story is how those people got onto your list in the first place: the forms, the contact book, and the categories a named form creates. That is its own piece, with its own film.
Questions people ask
- What is the difference between an email campaign and automatic emails?
- A campaign is one email, written once, sent once, at a moment you choose: the exhibition got a date, the course opened, the price changes on Friday. Automatic emails are standing rules that fire on their own when something happens, like a welcome when someone subscribes or a thank-you when someone buys. News is a campaign; welcomes are journeys.
- Who can I send a marketing email to?
- Only people with a real yes on record: your buyers, your students, and the sign-ups who ticked the consent box and then pressed the button in their confirmation email. Bernard counts each audience live before you choose one, and the number you see is the number it sends to. Contacts without a yes stay in your book and out of the send.
- Can the email go out by accident while I am drafting it?
- No. Writing, saving, previewing and sending are separate steps. Before anything leaves, you are shown a quote naming the exact email, its version and the exact number of people it goes to, and nothing sends until you approve that quote. If a word or a recipient changes while you decide, the old approval is refused and you are quoted again.
- Do I have to write the email myself?
- You can, but you do not have to. Tell Bernard what is happening in one sentence and it drafts the email in your voice, from what it knows of your site. You edit it, ask for another go, or put it aside. If you send the same kind of note regularly, keep a reusable template with named blanks for the details that change.
- Is there a limit on how much I can send?
- Yes, a monthly allowance, and it exists to protect you: inboxes learn to treat senders who blast too much as noise. A send that would go over the allowance is declined whole rather than emailing a random half of your list. Welcome and thank-you emails do not count against it.