Convert
Back-in-stock ping with cross-sell
The size your customer wanted is back — tell them before a competitor sells them theirs.
What it does
A customer asked for something you didn't have. They wanted it enough to ask — and when it quietly returns to stock, most retailers say nothing, so the demand leaks to whoever has it on the shelf today. The agent remembers exactly who asked and for what variant, pings them the moment inventory returns, and attaches the one companion product that genuinely fits the purchase. The same agent that answers "where's my order?" is one sentence away from "the size you wanted is back in stock — want me to ship it?"
How it works
- 1Trigger. the inventory feed flags a restocked SKU. The agent matches it against everyone who showed intent: customers who asked in a support conversation, joined a waitlist, or repeatedly hit the out-of-stock page.
- 2Decision. persistent customer memory supplies the exact variant and size they wanted. The agent checks consent and channel preference, applies frequency caps, picks a fitting cross-sell from purchase history and catalog affinity, and the judge gates the message before anything is sent.
- 3Action. a short message goes out on WhatsApp, SMS, or push — naming the exact item and variant, with a secure checkout hand-off link so the customer completes payment in your hosted checkout. The send goes through your own channels; you keep owning them.
- 4Follow-through. if the item sells out again before the send, the outreach is cancelled rather than delivered stale. Replies are handled in-conversation, outcomes are written back, and every recovered order is attributed to the ping.
Configuration
How the agent is wired for this use case.
inventory_restocked event from the OMS/inventory feed, matched against everyone who showed intent for that SKU (support request, waitlist sign-up, repeated out-of-stock page views).- Inventory/OMS feed · detect the restocked SKU and confirm it is still in stock before send
- Customer memory store · recall the exact variant and size each interested customer wanted
- Product catalog · pick a fitting cross-sell from purchase history and catalog affinity
- Commerce platform · reserve stock, build the cart, and generate the secure hosted-checkout hand-off link
- Messaging channel · send the opted-in ping and handle replies in-conversation
What you need
The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.
Signals
inventory_restocked events, out-of-stock page views, waitlist sign-ups, support conversations containing item requests
Data
customer–product interest with variant and size, purchase history for cross-sell selection, consent state and preferred channel
Guardrails
opt-in consent per channel, frequency caps, judge review of every unprompted message, automatic cancellation if stock runs out again before send
Metrics it moves
- conversion-rateup: the message lands on declared intent, with the exact variant the customer already wanted.
- recovered-revenueup: demand that would have leaked to a competitor comes back as attributed orders.
- attach-rateup: the combo suggestion rides on a purchase the customer was already going to make.
Related use cases
See it on your own customer journey
Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.
Book a demo