Content Rules

Add your organisation's own list of words and phrases that should never leave your account, and see a record of everything a screen has stopped.

Two layers

Every message whoot. sends is checked twice before it reaches the carrier.

The platform screen is always on and is the same for everybody. It refuses fraud, phishing and the categories carriers block outright. You cannot switch it off, and it is not configurable — it is part of keeping the numbers we all share deliverable.
Your rules sit on top and are entirely yours: a competitor's name, a phrase your legal team has asked people to stop using, terminology that belongs to a different service.

Rules live in Messaging → Settings → Content rules. Anybody who can send sees why a message was refused; only an administrator can change the rules, because a rule stops other people's messages and is a policy decision rather than a preference.

Block or warn

Block refuses the message. The sender cannot override it.
Warn flags it in the composer and lets the sender decide. Good for house style, where you want a nudge rather than a wall.

Writing a rule

Rules are plain words and phrases, matched without regard to capitals. There is one special character — * — which stands for anything in between:

payday loan       matches "apply for a payday loan today"
claim*prize       matches "claim your prize" and "claim prize"
cash              with whole words on, does NOT match "cashier"

Whole words only is on by default, and usually what you want. Turning it off makes a rule match anywhere inside a word, which catches more and surprises people more.

Regular expressions are deliberately not accepted. They are hard to debug from a settings screen, and a badly written one could stall your own sending.

Explaining a refusal

The message to the sender is shown instead of the rule itself. It lets you explain the policy without publishing the list of terms:

Word or phrase:      free gift
Message to sender:   Marketing language needs sign-off from Comms first — ask in #comms.

Testing before you save

Paste a real message into the test box and whoot. shows you exactly which of your rules it would trigger, using the same check that runs at send time. Worth doing before adding a rule to a busy account — a rule that is broader than you intended is easier to spot here than in a support ticket.

What was stopped

Underneath the rules is a log of messages a screen has refused: when, which layer stopped it, which rule matched, and a short excerpt so you can recognise the message. It exports to CSV.

The full message is never stored — only a short excerpt around the match. A message is often blocked precisely because of what it contains, and an audit log is a poor place to keep it.