Make SMS the fastest path to every customer.
Send verification codes, alerts, reminders and operational updates through the native messaging channel on every phone. Sent handles sender setup, carrier routing, compliance and delivery status behind one API.
- Urgent Alerts
- Maximum Reach
- No App Required
- Reliable Fallback
- WhatsApp Fallback
- OTP & 2FA
14,000+ developers and product teams rely on Sent for messaging
A familiar place for important customer conversations.

Nothing new to install
Reach customers through the messaging app already built into their phone. No account, download or new behavior required.

Built for urgent moments
Deliver codes, security alerts and operational updates when the value of the message depends on timing.

The next step stays clear
Keep the message concise and give customers one direct link or reply path when action is needed.
Turn product events into timely SMS.
Trigger the right message from the systems that already know what happened.

Get users through the door
Deliver one-time passwords, login verification and account-recovery codes with a clear expiration time.

Keep every order moving
Send confirmations, shipping updates and delivery exceptions as the order changes.
Confirm appointments
Let customers confirm or reschedule with a single reply, and keep the booking in step automatically.
Protect customer accounts
Alert customers to new logins, password changes and unusual account activity.
Bring customers back
Send relevant renewal, restock and re-engagement reminders without turning the channel into noise.
Short messages, built to stay predictable.
Control how content, variables, encoding and replies behave before anything reaches the carrier.

From sender setup to approved traffic.
Configure sender identities, destination countries, registration and consent controls in one workflow.

Choose your sender identity
Configure a dedicated number, short code or alphanumeric sender ID based on the destination and use case.

Register U.S. A2P messaging
Prepare and submit the brand and campaign information required for 10DLC, then follow its approval status.

Apply consent controls
Enforce opt-outs, quiet hours, destination rules and customer communication preferences before sending.
- Sender identity
- Destination countries
- 10DLC registration
- Consent controls

One request. The right carrier path.
Send SMS through one API call. Sent selects an available route, retries recoverable failures and moves between configured providers without changing your integration.
Explore the SMS API
Delivery status your product can use.
Receive queued, sent, delivered, filtered, failed and inbound-message events through webhooks, so your product always knows what happened next.
Explore webhooksThree 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.
WhatsApp
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