Turn every shopping moment into a reason to come back.
Connect store events to timely customer messages that recover carts, confirm orders, and encourage repeat purchases across SMS, WhatsApp, and RCS.
14,000+ developers and product teams rely on Sent for messaging
Commerce moves fast. Customer messaging often does not.
Customers move from browsing to buying to delivery in minutes or days. When messaging is late, generic, or disconnected from the order, revenue and trust disappear at the same time.
The intent window closes
A shopper can leave with a full cart and forget it just as quickly. A reminder that arrives after the buying moment has passed is only noise.
Order uncertainty becomes support volume
When confirmation, shipment, or delivery updates are missing, customers ask support for information the order system already knows.
Broad campaigns waste attention
The same promotion sent to every customer ignores browsing history, purchase stage, preferences, and the difference between urgency and relevance.
Meet Sent: the messaging layer behind the customer journey.
Support the whole purchase journey without stitching together messaging tools.
The two large cards cover revenue and post-purchase communication. The three compact cards show the supporting capabilities that make those journeys useful.
Recover high-intent shoppers
Trigger a recovery journey when checkout stops. Rebuild the cart inside the message with product details, an offer when appropriate, and a direct route back to checkout.
Turn order events into useful updates
Send confirmations, shipment progress, delivery windows, and exception alerts from the systems that already manage the order.
Bring products into the message
Use dynamic template variables, media, and channel-native actions to show the exact item or order being discussed.
Re-engage from real behavior
Use events from your CRM or commerce platform to trigger restock, replenishment, loyalty, and win-back messages.
Measure actions, not just sends
Return delivery, read, reply, click, and purchase signals to the analytics tools your team already uses.
Connect commerce events to customer action.
Connect once to the commerce stack
Trigger Sent from the storefront, checkout, order system, fulfillment provider, or CRM through one messaging API. Use webhook events to keep product, support, and analytics aligned after the send.
Give each moment the right channel and format
Use SMS for concise urgency, WhatsApp for conversational actions, and RCS for branded product experiences. Sent can choose an available path or follow the channel order your team sets.
Build customer value without spending customer trust.
Keep marketing consent separate from transactional communication, honor opt-outs, and stop blocked sends before they reach a provider.
Use approved sender profiles and reusable templates so commerce messages stay recognizable across teams and channels.
Track message IDs, delivery states, failures, and inbound responses so support can see what the customer actually received.
Frequently asked questions
Your storefront, checkout, order system, fulfilment provider, or CRM calls one Sent API endpoint when an event happens. Nothing has to be rebuilt per channel.
Yes. Recovery journeys and order lifecycle updates are the same request shape with different templates and triggers, so one integration covers both.
SMS, WhatsApp, and RCS. You can pin a journey to one channel or let Sent choose the strongest available route for each customer.
Yes. Templates carry media and channel-native actions, so a cart or an order can be shown with the item, its price, and a direct route back.
Templates take variables your systems supply — customer, cart, order, offer — so the message is built from your own data at send time rather than duplicated per segment.
Yes. A purchase event cancels the remaining steps, so a customer who has already checked out never receives the next reminder.
Yes. Inbound replies come back as events, so a question about an order can be routed to support with the order already attached.
Every message returns queued, sent, delivered, failed, and read states where the channel supports them, each against a message ID you can store with the order.
Marketing consent is kept separate from transactional communication, opt-outs are honoured across every channel, and blocked sends are stopped before they reach a provider.
Yes. Test credentials are separate from production, so a full journey can be run end to end without a message reaching a customer.