Messaging infrastructure for your commerce platform.
Your storefront, order system, or CRM connects to Sent through one API. Your platform decides what each customer hears and when. Sent delivers it over SMS, WhatsApp, and RCS and reports back what happened.
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, customers lose track of it and the questions land on support.
Late updates lose their meaning
An order update is only useful while it is still true. A confirmation, dispatch notice, or delivery change that arrives late leaves the customer guessing.
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.
Your platform sends the events. Sent turns each one into a delivered message on the right channel and reports back what happened.
Connect your platform’s own events
Your storefront, checkout, or order system calls Sent when something changes. Sent fills the approved template with the order number, items, and tracking link your platform supplies, and delivers it.
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.
Message from your own events
Your CRM or commerce platform decides when a restock, replenishment, or loyalty message goes out. Sent delivers it under the consent rules you set.
Delivery and engagement events
Return delivery, read, reply, and click events through webhooks 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 the Sent API when something happens, such as an order being placed or shipping. Sent then delivers the message over SMS, WhatsApp, or RCS. Your systems stay the source of truth for customers and orders, and Sent reports delivery back through webhooks.
Your store does. Your platform triggers each message from its own events and data, using a template you have approved. A later message can be scheduled ahead and cancelled through the API if it is no longer needed. Sent delivers each one and reports delivery and link clicks back.
The updates customers would otherwise chase: order confirmed, shipped, out for delivery, delivered, and any problem such as a delay or failed delivery. Build them as utility templates with the order number and tracking link as variables. Keep promotional language out of them, so WhatsApp approves them as transactional messages.
SMS reaches every phone and suits short, urgent updates. WhatsApp adds product images, buttons, and two-way conversations. RCS shows your brand name and logo with tappable chips on Android. When Sent chooses the channel, it picks the best one each customer can receive, from a single template.
Sent reports delivery, read, reply, and link-click events for every message, each tied to a message ID. Clicks come from the links Sent automatically shortens and tracks. To measure sales, match those message IDs with orders in your store or analytics tool; Sent doesn't record purchases itself.
Yes, through Sender Profiles. An organization account can hold a Sender Profile for each store or brand. Each profile has its own templates, contacts, sender numbers, and compliance settings, so each store's messages carry its own identity. One organization API key can send as any of its profiles.
Yes. A single Sent API request can reach up to 1,000 recipients, and the standard rate limit is 10,000 requests per minute. Sent spreads traffic across multiple providers and monitors their health, so a busy campaign isn't held back by a single provider.