One integration for your entire messaging stack.
Send through SMS, WhatsApp, and RCS with routing, templates, compliance, fallback, and delivery visibility handled by Sent.
14,000+ developers and product teams rely on Sent for messaging
One API for every channel
Use one consistent request for SMS, WhatsApp, and RCS. Add or switch channels without rebuilding your product.
A delivery profile, not just a phone number.
Each contact carries channel availability, validation, communication preferences, consent and delivery history giving Sent useful context before a message moves.
Sent replaced three provider integrations and the retry queue we were maintaining ourselves. We added WhatsApp in an afternoon and have not touched routing since.
Content defined by intent, not channel.
Create reusable templates with variables, media, buttons and channel-specific overrides. Sent handles formatting, validation and approval requirements for SMS, WhatsApp and RCS.
A decision engine for every send.
Sent evaluates channel availability, customer preferences, carrier health, cost and delivery performance to select the strongest path in real time.
Follow every message from request to delivery.
Track received, queued, sent, delivered, failed, and read states through one consistent message record.
Built for production from the first message.
Sent brings compliance, scalable infrastructure, and developer tools into one platform, so your team can launch faster and operate with confidence.
Compliance built in
Handle consent, opt-outs, 10DLC registration, WhatsApp templates, and country-specific messaging requirements at the platform level.
Infrastructure that keeps moving
Sent manages carrier routing, health checks, load balancing, retries, and global delivery behind one integration.
Tools developers expect
Build with REST APIs, SDKs, webhooks, reusable templates, sandbox testing, batch sends, and clear error handling.
SOC 2 Type II · GDPR · FCC Registered · NECA OCN 126L · IPES
Three channels. One consistent way to send.
Use SMS, WhatsApp, and RCS through the same API, templates, routing system, and delivery data.
SMS
Reach almost any phone with fast, reliable messages for authentication, alerts, reminders, notifications, and campaigns.
Read MoreWhatsApp
Create rich, two-way customer experiences with templates, media, conversations, and official WhatsApp Business delivery.
Read MoreRCS
Send branded messages with images, buttons, cards, and carousels, with automatic SMS fallback when RCS is unavailable.
Read More
Frequently asked questions
Sent gives you one API for SMS, WhatsApp and RCS, with routing, retries, template management, compliance handling and delivery tracking built in. You send one request and Sent decides how it reaches the customer.
Yes. Templates support locale variants, so you can define a message once per language and Sent selects the right one from the recipient profile or an explicit locale on the request.
You can pin a message to a single channel, give an ordered list of preferred channels, or let Sent Routing choose. Pinning is useful for regulated message types that must go over one specific channel.
Transactional messages such as one-time passcodes, order and delivery updates and account alerts, plus conversational and campaign messages where the channel allows it.
Sent sits behind one API and emits signed webhooks for every state change, so it drops into an existing stack without replacing your CRM, support desk or data warehouse.
Install the SDK, authenticate with your API key, then call sent.messages.send with a recipient, a template and the channels you allow. Everything after that, including routing and fallback, is handled for you.
Yes. Images, video, documents and rich cards are supported on the channels that allow them, and Sent adapts or drops the media automatically when a message falls back to a channel that does not.
Add them to the template as variables. Sent handles link shortening and per-channel attachment rules, and click events come back through the same webhooks as delivery events.
Every message exposes its full timeline: accepted, routed, sent, delivered, read and failed, with the route taken at each step. The same data is available in the dashboard and over the API.
Sent manages sender registration, template approval, opt-out handling and per-country sending rules, and blocks a send when the destination would breach them.
That is the default. One integration covers every channel you enable, and adding a new one does not require changes to your send code.
A full sandbox mirrors production behaviour, including routing decisions, failures and webhooks, so you can test fallback paths without sending a real message.
One API. Every channel.
Contact Sales