Three channels, one connection model
SMS, email and WhatsApp each connect to an account you already hold. What differs between them is not whether they work — it is which channel-level capabilities they carry.
SMS channel
Self-service connections to your own CPaaS account, with routing, per-number pacing, opt-out suppression and segment accounting running on top.
Email and WhatsApp
Both connect the same way as SMS: you pick a provider, link an account you already hold, and send from the console or the API.
- The same console connection flow as SMS, and a documented send API per channel.
- Delivery events normalized into the same statuses as SMS wherever the provider reports them back — Resend on email and Meta on WhatsApp today.
- A metadata-only message log, so you keep the record without keeping the content.
- Sent from your own provider account — your negotiated pricing and your invoice stay yours.
Channel-level capabilities. Routing and automatic failover, per-number pacing and segment accounting are provided on the SMS channel. Delivery receipts are normalized wherever the provider reports delivery back, and opt-out suppression is applied to marketing sends on every channel — the automatic STOP-keyword path is the SMS one. On email and WhatsApp the layer covers connecting, sending and recording the outcome.
Other channels
If you need something beyond SMS, email and WhatsApp, tell us what you are trying to do — the shape of the request genuinely affects which provider adapter we build next.