Make business messages feel verified and actionable.
Send branded RCS messages with suggestion chips, delivery and read visibility, two-way replies and automatic SMS fallback, through the same Sent API.
- Product Carousels
- Suggested Actions
- Rich Cards
- SMS Fallback
- Branded Sender
- Verified Business
14,000+ developers and product teams rely on Sent for messaging
A branded conversation customers can trust.
Recognizable from the first message
Show the approved business name, logo and verified identity instead of an unfamiliar sending number.
The next step is built in
Use suggestion chips to help customers confirm, track, reschedule or contact support immediately.
Every interaction stays visible
Follow delivery and read signals, then return replies and chip actions to the product that started the journey.
Turn notifications into next steps.
Help customers complete the next action without searching through another app or website.
Turn account alerts into decisions
Notify customers about important account activity and let them respond immediately.
Keep every order moving
Send branded order updates with immediate actions for tracking the order or changing delivery details.
Confirm appointments
Let customers confirm or reschedule directly from the conversation.
Collect useful feedback
Ask one focused question and capture the answer as a structured response.
Resolve support faster
Give customers a direct path to support or the right help content.
A clearer message with the response built in.
Use verified identity, dynamic content and suggestion chips to make the next action obvious.
From RCS Agent to approved send.
Sent coordinates the sender, carrier and message approvals required before production traffic begins.
Create the branded RCS Agent
Define the approved business name, logo and identity customers will see in the conversation.
Complete carrier approval
Work with Sent through the one-time review required to activate RCS for production sending.
Publish approved messages
Prepare text, variables and suggestion chips, then follow the message template status from the dashboard.
- Verified RCS Agent
- Carrier approval
- Message status
- Built-in opt-out
Try RCS first. Fall back without friction.
Sent checks device and carrier availability before sending. If RCS is unavailable, the same message can continue through SMS automatically.
Explore RCS delivery
Turn every read, tap and reply into a product event.
Track delivery and read states, then return suggestion-chip actions and customer replies to your product through webhooks.
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.
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.
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