Start a Klaviyo Restock or Win-Back Flow From a WhatsApp Chat
Yes. AeroChat works directly with Klaviyo. When a shopper asks about a sold-out product, or a customer who has not ordered in months gets back in touch, AeroChat records an event on their Klaviyo profile, such as Chat Restock Request or Chat Return Visit. Events can start flows, so the restock or win-back flow you build in Klaviyo picks them up.
This recipe connects chat moments to Klaviyo flows for stores on WooCommerce or Wix, where Klaviyo’s built-in back in stock setup may not cover your catalog. On Shopify, Klaviyo’s own back in stock alerts work directly: see back in stock alerts for Shopify stores. Part of connecting Klaviyo to WhatsApp and AI chat.
What happens today
A shopper asks on WhatsApp when a sold-out size will be back. Someone says “soon” and the request is lost. A customer who last ordered in the spring messages to ask about a new product, and nobody notices they had lapsed. Klaviyo has the flows to follow up on both, but nothing tells Klaviyo the conversation happened.
The flow that works
- A shopper asks about a product that is out of stock, or a customer gets in touch whose last order was a while ago.
- AeroChat checks the product’s stock, or the customer’s last order date, in your store.
- For a restock request, it asks whether they would like to hear when the item is back, and by which channel, and gets a clear yes.
- It records an event on the customer’s Klaviyo profile with the product, the variant or the last order date as properties.
- Your Klaviyo flow, triggered by that event, takes it from there: a restock segment you email when the stock lands, or your win-back series.
What it looks like on WhatsApp
Customer: Will the merino crew in navy, size L, be back? (example)
AeroChat: The merino crew in navy, size L, is sold out right now. Would you like an email when it’s back? The charcoal is in stock in L if you’d rather not wait.
Customer: I’ll wait for navy. Email me at tom@example.com.
AeroChat: Done. We’ll let you know at tom@example.com when it’s back.
In Klaviyo: a Chat Restock Request event (example) is added to Tom’s profile with the product, the color, the size and email as the channel. Your restock segment includes him.
Customer: Hi, do you still make the olive oil soap? (example)
AeroChat: We do, and it’s in stock. The 3-bar pack is $24. Would you like to order?
In Klaviyo: the customer’s last order was 7 months ago, so a Chat Return Visit event (example) is added to their profile. Your win-back flow, set to start on that event, picks them up.
The recipe
Copy this into AeroChat
Follow these steps in two situations.
- When a shopper asks about a product or a size that is out of stock: confirm the exact variant and check its stock in our store. If it is out of stock, say so and ask whether they would like to hear when it is back, by email or text. Suggest one in-stock alternative if there is one.
- Only after a clear yes, find or create their Klaviyo profile with their email or phone number, and create the event Chat Restock Request (example) with the product name, product ID, variant and channel as properties. Confirm what the alert is for in one line. Never give a restock date unless it is in our knowledge base.
- When a known customer gets in touch, find their last order in our store. If it was more than 120 days ago (example), create the event Chat Return Visit (example) on their Klaviyo profile, with the last order date and the topic they asked about as properties. Do not tell the customer about the event. Just help them with their question.
An event never changes anyone’s consent, and Klaviyo’s sending rules still apply to every message our flows send. Reply in the customer’s language.
Change the event names and the 120-day window to match the flows you build before you paste it.
What to connect
- Klaviyo. An owner, admin or manager creates a private API key under Settings, API keys, with write access to events and profiles. Paste it in when AeroChat asks.
- Your Klaviyo flows. Build a flow triggered by each event. For restocks, a segment of people with a Chat Restock Request for a product, which you email when it is back. For win-back, your usual win-back series, triggered by Chat Return Visit.
- Your store. WooCommerce or Wix, built in. Connect it in the AeroChat dashboard so AeroChat can check stock and order history. For WooCommerce order history, add a REST API key with read access to orders.
Klaviyo documents that events can trigger flows in its events API reference.
After you paste the recipe, AeroChat builds the workflow as a draft and shows a checklist: connect Klaviyo, add your knowledge base if the recipe uses one, then switch it on. If it built the connection from Klaviyo’s public documentation, the checklist asks you to check it once against the current docs.
Using a different system? If it has a public API, it connects to AeroChat the same way: describe what you want, paste in its key, and it runs.
Can’t find your tool? Message us in the chat on this page and we’ll tell you how it connects.
What you still decide
- What your restock and win-back flows send, and when.
- How long since the last order counts as lapsed.
- Whether AeroChat offers an in-stock alternative, and which ones.
The result to expect
Restock requests made in chat end up in Klaviyo with the exact variant, ready for your restock email. Lapsed customers who get in touch start your win-back flow without anyone on your team spotting them.
Measure it with your own numbers: restock requests and return visits recorded from chat per month, and orders from the flows they started.
See also: stock and back-in-stock questions for WooCommerce.
Works on every chat channel
This workflow runs the same way on WhatsApp, Instagram, Facebook Messenger, Telegram, the chat on your store and email, with the same Klaviyo connection behind it. See what each channel does on the Klaviyo integration page.
Send your first chat event to Klaviyo
Paste the recipe, add your Klaviyo key, and ask your own chat about a size you have run out of.