Compliance & DND
Before any message dispatches, we run eight checks against the campaign, sender, and content. Anything that fails blocks the send and surfaces a reason — nothing goes out that shouldn't.
Preflight · April reminder
campaign_8412Sender ID approved
MACKHAM · Transactional
Class match
Service update ∈ allowed classes
Suppression applied
12 unsubscribed numbers removed
DND routing
DND-compliant corridor selected
Time window
Scheduled 09:00 WAT · permitted
Prohibited content
No flagged keywords
Opt-in proof
94% coverage
Rate limit
944 within policy
Preflight
These run automatically the moment you submit a campaign. You see the results inline before you confirm dispatch.
We verify the sender is active and not revoked before any send.
The sender ID must be allowed to send this message class.
Unsubscribed numbers are removed before dispatch.
Transactional traffic routes through the DND-compliant corridor.
Marketing messages are blocked outside carrier-permitted hours.
Flagged keywords and restricted categories are caught before send.
Marketing requires documented consent at send time.
Per-workspace send rates are enforced to protect sender-ID reputation.
DND routing
DND-registered numbers can receive transactional traffic — OTPs, order alerts, appointment reminders, service notifications — via the compliant corridor. Marketing messages to DND numbers are not permitted by the carriers and are blocked at preflight.
Allowed on DND
Blocked on DND
Unsubscribe handling
Reply STOP, or a manual removal from your dashboard, adds the contact to your unsubscribe list. Preflight filters them out of every future send automatically.
Unsubscribe list
12 total · suppressed from every send+234 803 •• 2947
Reply STOP
Today, 08:42
+234 808 •• 8833
Reply STOP
Yesterday, 17:21
+234 818 •• 5529
Manual · dashboard
3 days ago
+234 705 •• 6671
Reply STOP
6 days ago
Why this matters
The preflight reads like bureaucracy on paper. In practice it's the difference between a campaign that lands and a campaign that quietly damages your sender reputation — and your wallet.
A single non-compliant send can get a sender ID flagged by a carrier. Preflight catches the class mismatch before it happens — your sender name stays usable.
DND-blocked and rejected messages still cost you if they ever leave the wallet. Preflight blocks them at the gate, so your reserve never converts into wasted segments.
Suppression, opt-in proof, prohibited content — each one filtered before dispatch instead of after. Fewer campaign retries, fewer confused support tickets from your own team.
As rules and risky categories shift, the preflight catalogue updates centrally. You don't have to remember which ban landed when — the check is always current.