Skip to content
Multi-channel

SMS channel

Twilio + Telnyx + Bandwidth A2P 10DLC with STOP keyword auto-DNC.

The SMS channel sends through an A2P 10DLC-registered number on Twilio, Telnyx or Bandwidth. Sequences are TCPA-gated before send, and inbound STOP keywords are detected automatically — the first opt-out adds that recipient to the DNC list across every channel, not only SMS.

What you get
  • ·Twilio · Telnyx · Bandwidth A2P 10DLC support
  • ·RFC 8058-style STOP / UNSUBSCRIBE keyword detection
  • ·Auto-DNC across every channel on opt-out
  • ·Per-number daily and hourly caps + quiet hours
  • ·TCPA-compliant by default — never the operator’s job
  • ·Two-way: replies land in Unibox alongside email
SMS dispatcher · last 24h
India · DLT
SCRUB-PE registered
Header + template approved
US · 10DLC
Brand verified · A2P
TCR registration current
Today’s dispatch
09:14+91 98xxxdelivered₹0.18
09:14+1 415xxxdelivered$0.0079
09:13+44 77xxxSTOP$0.0000
09:13+91 98xxxdelivered₹0.18
09:12+1 212xxxdelivered$0.0079
2,341
Delivered
3
STOP-blocked
$18.40
Cost (24h)
The problem

Why most cold SMS gets blocked at the carrier

Carriers in the US (10DLC) and India (TRAI DLT) expect business SMS senders and message bodies to be registered before they deliver them, and that registration is done with your provider, not in Autocloz. An opt-out that is not honoured straight away is a TCPA problem in the US.

  • Delivery rate dropped below 60% on a number that worked yesterday
  • STOP came in but the next outbound still went out (lawsuit risk)
  • Carrier suspended the number with no warning
  • TCPA complaint letter from a state AG
250
SMS a day on Free
1,500 Growth · 7,500 Pro · 50,000 Scale
STOP
auto-DNC across channels
single keyword opts the recipient out everywhere
8
opt-out keywords
STOP, STOPALL, UNSUBSCRIBE, CANCEL, QUIT, END…
BYO
provider account
your own Twilio, Telnyx, Bandwidth or MSG91 keys
How it works

The detail.

10DLC is not optional — and we know it

Registering a 10DLC brand and campaign happens with your provider, and Autocloz does not check that registration before sending. What it does check is launch: a campaign with SMS steps and no active SMS sender is blocked, and one with no active SMS template in the workspace is warned.

STOP detection — a hard rule, not a heuristic

Every inbound SMS runs through detect_opt_out() with the carrier-recognised STOP keyword set. A match writes a DNC row immediately, tagged with the wildcard channel * so the next outbound outbound to that recipient — on email, LinkedIn, WhatsApp, or call — is also blocked.

Replies feel like a real conversation

Two-way SMS lands in the Unibox alongside email and WhatsApp, AI-tagged for intent, with the lead's full timeline one click away. Reply from the keyboard; the dispatcher honours the per-account cap.

Providers

Bring your own — or pick from the supported set.

Twilio
Global · SMS from your own account
Telnyx
Global · 10DLC + toll-free
Bandwidth
US-first · SMS and voice
MSG91
India · DLT Sender ID + Flow ID
Anti-ban rules

The rules that keep your account alive.

Every rule below is enforced before any outbound action. The compliance gate either passes or it doesn’t dispatch.

  • Block launch when SMS steps have no active SMS sender
    Why: The pre-launch check stops a campaign whose SMS steps have no active sender, so the campaign never starts running.
  • Cap every SMS sender per hour and per day
    Why: A new sender starts at 10 messages an hour and 50 a day; a capped sender is skipped for the next one, or the step waits.
  • Auto-DNC on STOP / UNSUBSCRIBE / CANCEL / QUIT / END / OPTOUT
    Why: These are carrier-recognised opt-out keywords; honouring all of them is required, not optional.
  • Cross-channel DNC propagation
    Why: If a recipient says STOP on SMS, they cannot legally be contacted on WhatsApp (same TCPA framework). Autocloz writes the wildcard '*' DNC row automatically.
  • Quiet hours on every SMS sender, in the sender's timezone
    Why: New SMS senders get a night-time window read in the timezone saved on the sender, so set it to where your recipients are.
Sample sequence

A real sequence using this channel — day by day.

  1. Day 0
    Email + SMS opener combo
    SMS arrives 30s after email open · 'just sent you a note' framing
  2. Day 2
    SMS reminder
    Only if email_event.opened == false · short, value-first
  3. Day 5
    WhatsApp escalation
    If still no reply · same template-gated rules apply
  4. Day 7
    Final SMS with breakup
    'Last note from me' framing; high reply rate
  5. Day 9
    Re-engage 30d later
    Auto-snoozed; surfaces if any channel fires intent
A STOP from a prospect on any channel instantly suppresses them across all five — cross-channel DNC enforcement is built into the core, not bolted on.
Compliance lead enforcing cross-channel DNC · Illustrative scenario
FAQ

Specific to this feature.

Do I need 10DLC registration to send SMS in the US?

+

Yes — US carriers expect A2P SMS from a registered 10DLC brand and campaign. You register with Twilio, Telnyx or Bandwidth; Autocloz does not check that registration, so confirm it in the provider's console first.

What about India DLT?

+

TRAI requires DLT registration of your entity, header and templates, done outside Autocloz. An MSG91 sender will not send without its DLT Sender ID and Flow ID; other providers are not checked.

Will replying STOP really opt the recipient out everywhere?

+

Yes — STOP writes a DNC row with channel='*' (wildcard), so the next outbound on email, WhatsApp, call, or LinkedIn is also blocked. This is the legally safe default.

Can I send marketing SMS in India?

+

Yes, through a DLT-registered entity and approved template. Autocloz applies no IST filter of its own: quiet hours use the sender's timezone, so set Asia/Kolkata on senders texting India.

Pairs well with