— Use cases
What teams build with SMSAPI
A few of the most common ways developers and business teams put SMS, WhatsApp, and voice to work in India — each with the channels it uses and the compliance it needs.
Choose a use case
— Use case
Order & delivery notifications
Keep customers updated from shipped to doorstep.
— Use case
Abandoned-cart recovery
Bring back a stalled checkout with a timely nudge.
— Use case
Appointment reminders
Cut no-shows with confirm-and-remind sequences.
— Use case
Two-factor authentication
Stop account takeover with a second factor.
— Use case
Email to SMS
Let any system reach a phone from an email.
— Channels
Match the channel to the job
- Codes and security alerts go by OTP SMS on the transactional route, with a voice call as the fallback when an SMS doesn't arrive.
- Order and delivery updates work well on WhatsApp, where a tracking link or button fits, with SMS for customers who aren't on it.
- Reminders suit SMS or WhatsApp, and a voice call for people who don't read text messages.
- Offers and campaigns go on the promotional SMS route or as WhatsApp marketing messages, to people who have opted in.
— Before you send
What every use case needs
Each type of message needs its own DLT template, registered in the right category, before it can go out. An abandoned-cart nudge is promotional; an order confirmation is transactional. Getting the category right is the most common reason a template passes or fails.
You also need a way to know what happened. Every message sent through the SMS API returns a delivery status by webhook, so your system can retry, switch channel or stop, instead of guessing.