Sending a promotional Bulk SMS campaign to a number on the National DND Registry risks a TRAI penalty and can get your sender ID blocked — which stops every campaign, not just the one that triggered it. MetaReach's Bulk SMS platform checks the DND status of every number automatically before your campaign sends, so this isn't a step you have to remember.
Bulk SMS campaigns typically send to large, list-sourced audiences where DND status hasn't necessarily been checked recently. A single flagged campaign can trigger sender-ID suspension, which halts transactional and OTP messages on the same ID too if categories aren't properly separated at the DLT level — see our DLT registration guide for how sender-ID and template registration work together with DND compliance.
DND filtering applies only to promotional Bulk SMS. Transactional SMS — OTPs, order and delivery updates, account alerts — is exempt and reaches every registered number. Campaigns that mix promotional content into a transactional template risk both a DND violation and a TRAI content-mismatch flag, regardless of the recipient's DND status.
Don't route promotional content through a transactional template to "get around" DND filtering — TRAI's content-template matching can flag this independently of DND status, and it risks both categories of messaging on the same sender ID.
Every recipient list uploaded for a promotional campaign is checked against the current NDNC Registry before sending, and DND-registered numbers are excluded from that send automatically. For a closer look at the filtering technology itself, see dnd-filter.php; to check a single number before adding it to a list, see dnd-number-checker.php.
DND filtering runs automatically on every promotional Bulk SMS campaign sent through MetaReach — no separate scrubbing step, no extra tool to manage.
From startups to enterprises — brands that grow with MetaReach
