Recover abandoned carts before intent disappears.
Sent turns abandoned carts into timely, personalized SMS journeys that bring shoppers back to checkout and help recover lost revenue.
A customer was ready to buy. Then the journey stopped.
Around 70% of online carts are abandoned. Email reminders are often missed, and every delay makes it harder to bring the shopper back.
Purchase intent fades quickly
The longer a cart sits untouched, the less likely the shopper is to return with the same intent to purchase.
Email is easy to miss
Recovery emails compete with a crowded inbox and may not be seen during the most important recovery window.
Generic reminders get ignored
Without the cart details, a useful offer, or a direct path back, customers have little reason to finish checking out.
Meet Sent: cart recovery that knows when to act.
From abandoned cart to recovered order
Sent receives the cart event, waits for the right moment, personalizes the message, and sends the shopper directly back to checkout.
Everything needed to bring the shopper back.
Sent handles the trigger, timing, personalization and follow-up while your team stays focused on the customer experience.
Trigger while intent is high
Automatically trigger a recovery SMS within minutes of abandonment, while the customer is still thinking about the purchase.
Make every message personal
Add the customer’s name, exact cart items, product images and personalized discount codes.
Remove checkout friction
Bring customers directly back to their saved cart with a clear, one-click checkout link.
Follow up without over-messaging
Build multi-step sequences with smart scheduling and frequency caps instead of relying on one reminder.
Improve every recovery journey.
Use customer behavior and campaign performance to improve when messages send, what they say and how much revenue they recover.
Recover revenue without losing customer trust.
Sent supports opt-in enforcement, country-specific messaging rules, content validation and automatic handling of customer opt-outs.
API keys stay server-side, webhook events are signed, and every recovery send is made from your own authenticated systems.
Queued, sent, delivered, clicked and checked out are reported against one message ID, so support can see exactly what the shopper received.
One API. Every channel.
Contact SalesFrequently 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.