Hours and ceilings
Nothing leaves outside your sending window or over your daily limit. Set it for the workspace and tighten it per number or campaign.
HomeFeaturesSafety and consent
Safety and consent
The rules that stop a bad afternoon.
The expensive mistakes in bulk messaging are not technical. They are a promotion sent at two in the morning, a message to somebody who asked you to stop, and a number that gets restricted because it behaved like a machine. Birsend’s guardrails sit in front of every path out, not just the campaign screen.
- Every path
- campaigns, inbox, API, agents
- Narrow only
- each layer tightens, never widens
- Evidence
- kept for every consent change
What you get
Sending limits, an opt-in requirement, automatic STOP handling and a content filter — applied to every path out, including your own scripts.
One switch stops everything
Pause sending for the whole workspace until a date you pick. Campaigns, replies and API calls all stop at the same line.
Opt-in, enforced
Require consent before anybody can be messaged and Birsend refuses the rest — at the campaign, in the inbox, and through the API.
STOP is handled for you
A customer asking to be left alone is opted out the moment they say so, before any automatic reply gets the chance to greet them.
Consent you can prove
Every change is filed as evidence — what happened, from where, and when. “Show me why you messaged them” has an answer.
A word filter you control
Block what must never leave your number, allow the words a filter would otherwise catch, and read back everything it stopped.
How it works
01
One gate, not one per screen
Every outgoing message goes through the same check, whichever door it came from — a campaign, somebody typing in the inbox, your own software on the API, or an AI agent. A key is a door, not an exemption.
- Workspace hours, narrowed by the number, narrowed by the campaign
- Daily caps per number and per campaign, with the smallest one winning
- Blocked contacts and opted-out contacts are refused absolutely
02
Consent as evidence, not as a checkbox
Opting somebody in records where that consent came from and when. Opting out is stored as its own fact rather than as an absence, so somebody ticking a box again later cannot quietly undo a request to stop.
- “They never told us” and “they told us to stop” are different states
- STOP-style replies are read before any automatic rule runs
- The whole trail is on the contact, next to what they were sent
03
A filter you can see through
The content filter is readable by everybody who can open the workspace, not just by admins — because the first question after a message disappears is “which word”, and a filter people cannot inspect is one they stop trusting.
- Your own blocked list, plus an allow list for words a filter would over-catch
- Everything it stopped is logged with the reason and the matched word
- Applied to automatic replies too, which are the path with nobody watching
What it does not do
The honest list. We would rather you found this here than three weeks into a trial.
- Sending windows are judged in UTC for now, because a workspace has no timezone field yet.
- Consent is recorded and enforced; Birsend does not collect it for you. Getting the opt-in is your process.
- The word filter matches words, not intent. It is a guardrail, not a compliance department.
Questions
Does the API bypass these rules?
No. That is the point of putting them in one place. A key issued to your own software sends under the same hours, caps, consent requirement and word filter as a person clicking send.
What if I need to stop everything right now?
Pause sending for the workspace. It takes effect within a minute on anything already running, and every other path refuses immediately.
See it on your own number.
Fourteen days free, no credit card. Connect a number, send one campaign, and judge the reports for yourself.