Features · Sending guardrail
A brake that stops one bad send becoming a dead domain.
SendBeam watches what happens to the mail each workspace sends, and stops that workspace on its own when the results turn bad. You are told what happened and what to do next. Everything except sending keeps working, and the rest of your account is untouched.
01 · What you get
How sending guardrail work in SendBeam.
- 01 It acts before your reputation doesA list that has gone stale, an import of addresses nobody agreed to, or an automation looping on a bad segment all look the same from outside: complaints and bounces climbing. Mailbox providers respond by quietly sending your mail to spam, and that damage outlasts the campaign that caused it. SendBeam reads the same delivery results they do and stops the workspace first, so the problem ends while it is still one bad send.
- 02 One workspace, not your accountThe brake is per workspace, because that is where a bad list lives. A paused client workspace does not stop your own newsletter, and an agency does not lose every site because one of them imported a bought list. Nothing about the account, the plan or the other workspaces changes.
- 03 Only sending stopsYou can still sign in, read and edit your contacts, run exports, read everything over the API and keep your forms collecting signups. That last part matters: subscribers carry on arriving while you are paused, so the fix does not cost you the audience you were building. Campaigns already written stay as drafts rather than disappearing.
- 04 You are told, in words, immediatelyA pause sends you an email naming the workspace, what kind of problem triggered it, and what to do about it. The same explanation appears in the app rather than a bare error on your next send, so nobody has to guess why a campaign will not go out.
- 05 You can see it comingAccount insights shows every workspace’s recent delivery rates side by side, worst first, with a plain band from quiet through to paused. A workspace drifting the wrong way is visible there well before the brake is reached, which is usually enough to clean a list on your own terms.
- 06 Built for automated sendersThe case for a brake is strongest when a person is not watching each send: an AI agent, a scheduled job, a webhook-driven automation. Those can send a great deal of wrong mail quickly and confidently, and the guardrail is what bounds the damage. It applies to every sending path equally — app, API and automation — because a limit only one of them respects is not a limit.
Plans. On every plan, including Free. It is not a paid add-on: a platform that lets one tenant burn shared sending reputation is worse for everybody on it. Compare plans.
02 · How it works
From zero to live.
The steps as they appear in the dashboard today. Each one is covered in more depth in the docs linked below.
- Step 01 Send as usualNothing to switch on. Every campaign, automation and API send is already logged with its delivery outcome.
- Step 02 Watch the bandsAccount settings → Insights shows each workspace’s recent delivery health, worst first, so a problem is visible early.
- Step 03 If a workspace pauses, read the emailIt names the workspace and the kind of problem. The same message is in the app.
- Step 04 Fix the cause, not the symptomUsually an old or bought list, or a segment that is far wider than intended. Clean the list, then ask for the pause to be lifted.
- Step 05 Carry onYour contacts, drafts, automations and forms are all as you left them.
03 · Questions
Asked before choosing sending guardrail.
- What exactly makes a workspace pause?
- A sustained deterioration in what happens to the mail that workspace sends — chiefly complaints and hard bounces, judged over a recent window rather than on a single bad hour. We do not publish the exact trigger points: they are a defence, and anyone tuning a send to sit just underneath them would be doing the precise thing the brake exists to stop.
- Will one bad campaign pause me?
- Very unlikely. The judgement is made across a recent window and needs enough messages to be meaningful, so a small test or one unlucky send does not trip it. It is aimed at a pattern, not an incident.
- Does a pause affect my other workspaces?
- No. It applies to the one workspace whose results went bad. Every other workspace on the account keeps sending normally.
- Can I still use my account while paused?
- Yes, apart from sending. Sign-in, contacts, segments, exports, API reads and your signup forms all keep working, so you can diagnose and fix the problem with everything in front of you — and keep collecting subscribers while you do.
- How do I get sending switched back on?
- Fix what caused it — normally removing the addresses that are complaining or bouncing — then contact us. We would rather resume you quickly than leave you stuck; what we will not do is resume a workspace that would immediately pause again.
- Is this the same as a sending limit?
- No. Your plan’s monthly allowance and hourly ceiling are about volume. This is about outcome: you can be well inside every allowance and still be sending mail that recipients are reporting, which is the situation this stops.
More features
- Workspaces Run every site’s email from one account.One account for every site you run. A workspace per site, one plan for all of them.
- Forms Signup and contact forms that fit any site.Signup forms with double opt-in and contact forms that email you, both protected by Turnstile and an origin allow-list.
- Sending domains Every site sends from its own domain.A verified domain per site, DKIM and an aligned return path, and the CNAME records to publish.
- Automations Sequences that run themselves, per site.Trigger-based sequences per workspace: welcome series, lead magnets, tag-driven follow-ups.
- API One REST API for every workspace.A REST API per workspace for contacts, lists, segments, campaigns, forms and single transactional sends.
04 · Start
Start with the site you run today.
Free to start, no card, no trial clock. Each site keeps its own domain, list and rules; you add the next one as a workspace whenever you launch it.
Checking system status