Key Takeaways
- whatsapp sms gateway searches explained running both without confusion: run chat and SMS as separate adapters with separate credentials.
- Do not route OTP through chat “because marketing already uses it.”
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. SMS lane still needs BYO Android + airtime.
- Shared CRM events can fan out — never share API keys across channels.
- Free is 300 SMS lifetime; paid from $19/month.
Two lanes, one customer
Teams that must run chat and SMS should treat them as parallel adapters. Service pricing is based on device count and total SMS sent through the gateway. See when SMS still wins for channel fit. SMS API: Developer Center.
Confusion starts when one “notify” function picks a channel at random. Encode the channel in the event name — order.shipped.sms vs order.shipped.chat.
What goes where
| Event | SMS lane | Chat lane |
|---|---|---|
| Login OTP | Primary | Avoid unless product requires |
| Order shipped | Short status OK | Richer tracking thread OK |
| Promo blast | Consent + STOP required | Template + opt-in required |
| Support reply | Limited | Usually better UX |
Ops without mixing secrets
Separate env keys, dashboards, and on-call runbooks. Android SIM ops (battery, airtime) never appear in chat vendor consoles. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Both-channels checklist
- Explicit event→channel map.
- Separate credentials and rate limits.
- OTP primary channel documented.
- Consent scopes per channel.
- BYO Android + operator credit for SMS.
Next steps
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- device and SMS volume pricingPlans and allowances
- Twilio vs Android SMS gatewayCloud vs own-SIM cost model
- Android SMS gateway product guideDefinition, product, and how to buy
- SMS API documentationLive endpoint reference
