Transactional and promotional
Two jobs, one channel. Fire a single OTP-adjacent alert or order update to one number via the API, or blast a Diwali offer to a whole segment — both templated with merge tags like {{name}} and {{order_id}}.
SMS marketing & transactional
The one inbox everyone checks — SMS that gets read.
Not everyone installs your app or opens email — but a text message gets read within minutes, no app and no data connection required. Send order confirmations, delivery updates, payment reminders, and promos that land — from the same dashboard, audience, and automations as your push and email.
One audience, every channel
Reuse the exact segments you already built for push and email. No re-importing lists, no separate SMS silo drifting out of sync — the same customer, reached on whichever channel they answer.
STOP and opt-out built in
When someone replies STOP, they are opted out automatically and the change shows up in your hosted preference center. No manual list scrubbing, no accidental sends to people who asked you to stop.
Bring your own provider
Plug in Gupshup, MSG91, Twilio, or another gateway with your own API keys (that is what BYOK means). You keep the per-SMS rates you negotiated and your registered sender IDs — we just drive the sending.
DLT-ready for India
Indian SMS runs on DLT — the TRAI-mandated registry where you pre-register your sender ID and message templates. Bring those registered headers and templates; we route them compliantly through your provider and honour STOP automatically. The registration stays yours; the plumbing is ours.
Delivery you can see
Track sent, delivered, and failed for every message, with the failure reason spelled out — DND-blocked, invalid number, template mismatch — surfaced in channel deliverability monitoring so you can fix it fast.
Automations and fallback
Trigger an SMS from any journey — cart abandoned, payment due, shipment out for delivery — or use it as an engagement-aware fallback when a push goes unread. Available on every paid plan.
The channel that reaches the other 90%.
A keypad phone, a patchy network, an uninstalled app — none of it stops an SMS. That is why a text sits in the same inbox as the bank alert and the OTP, and why it gets read minutes after it lands. ReachBell sends through the provider you already use and unifies delivery tracking, opt-outs, and segments with the rest of your channels, so SMS is one more lever in the same playbook — not a separate tool to babysit.
- Transactional and promotional — single API sends and segment campaigns
- Bring your own provider (Gupshup, MSG91, Twilio) — your keys, your rates
- DLT-ready — use your TRAI-registered sender IDs and templates
- Two-way STOP and opt-out honoured automatically
- Merge tags like {{name}} and {{order_id}} for per-recipient copy
- Delivery and failure tracking, with reasons, in one dashboard
- Built in India — INR billing, GST invoices
Order confirmed ✅
Track it anytime — reply STOP to opt out.
Flash sale: 40% off today
Shop now → your link here
Delivered · SMS + WhatsApp
How it works
Live in an afternoon.
No SDK wrestling, no DevOps tickets — most teams finish setup before their chai goes cold.
Connect your provider
Paste your SMS provider keys (Gupshup, MSG91, Twilio, or another) and your DLT-registered sender ID into the dashboard. No new contract, no number to provision.
Pick your audience and write
Choose a saved segment or upload a number list, then draft your message with merge tags so every recipient gets their own name, order ID, or amount.
Send and track
Fire transactional sends through the API in real time, or schedule a campaign — then watch delivered and failed states roll in live, reason by reason.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
What is the difference between transactional and promotional SMS?
Transactional SMS carries information a customer is expecting — an order confirmation, a delivery update, a payment reminder, an OTP-adjacent alert. Promotional SMS is marketing: offers, launches, win-back nudges. The distinction matters in India because they use different DLT template categories and routing, and promotional sends respect DND (Do Not Disturb) preferences. ReachBell handles both from the same project: single-recipient transactional sends through the API, and promotional campaigns to whole segments, each with its own tracking.
What is a sender ID, and can I use mine?
A sender ID is the short six-character header a text appears to come from — like MyShop instead of a phone number. In India it has to be registered on DLT before you can send. ReachBell uses the registered sender IDs you already have with your provider, so your messages keep arriving under your brand name, not a random number.
What does an SMS through ReachBell actually look like?
Exactly like the texts you already send — your sender ID, your DLT template. A transactional one might read: "Hi Aarav, your order #4821 is out for delivery and will arrive today. Track: …". A promotional one: "MyShop: Monsoon sale is live — flat 30% off ends Sunday. Shop now: … Reply STOP to opt out." Merge tags fill in the name, order ID, or amount per recipient.
How do opt-outs and STOP work?
When a recipient replies STOP, ReachBell processes it automatically: they are opted out of SMS and the change is reflected in your hosted preference center. No spreadsheet to scrub, no risk of texting someone who already asked you to stop — you stay compliant by default.
Do I need my own SMS provider, and how does routing work?
Yes — SMS is bring-your-own-provider (BYOK). You connect Gupshup, MSG91, Twilio, or another gateway with your own API keys. ReachBell routes each send through your provider, so you keep the per-SMS rates you negotiated and your registered sender IDs, while we handle sending, templating, segmentation, retries, and delivery tracking. If you change providers later, you swap the keys — your audiences and journeys stay put.
Why bring my own provider instead of buying SMS from ReachBell?
Because Indian SMS pricing and DLT registration are things you set up once with a gateway and then reuse everywhere. BYOK means you are not paying a markup or re-registering templates — your existing Gupshup or MSG91 account does the carrier work, and ReachBell adds the audience, automation, and tracking layer on top.
Is it DLT and TRAI compliant for India?
ReachBell is built for India and works with Indian gateways like Gupshup and MSG91, so your DLT-registered sender IDs and templates flow straight through. DLT and TRAI registration stays in your name with your provider — that is by design, since the registry ties templates to your business. We route those approved templates compliantly and honour STOP automatically. Billing is in INR with GST invoices.