Most brands hear "cart recovery" and think it's handled. There's a flow. It fires when someone abandons checkout. The box is checked.
That box was never the point. The flow fires on a timer, whatever the shopper does or doesn't do next. It can't read a reply. It can't answer an objection. It can't hold a conversation. Conversation is the mechanism that recovers revenue, not the reminder.
What a flow does
A standard cart recovery flow is three emails, maybe an SMS mixed in, spaced out over a set schedule. Email one at an hour. Email two at a day. Email three with a discount, three days out.
The schedule doesn't know anything about the shopper. It doesn't stop, adapt, or check for a reply before sending the next message. It fires on the clock it was built to fire on, regardless of what happens on the other end.
A reply might land in a shared inbox somewhere. Whether anyone sees it in time is a staffing question, not a product feature, and most brands aren't watching that inbox in real time. Either way, the automated sequence doesn't know the difference. It sends message two on schedule whether the shopper already got an answer, got a bad one, or got nothing at all.
This works fine when the shopper's problem is forgetting. A reminder solves forgetting. Forgetting isn't why 70% of carts get abandoned, though. Hesitation is, and hesitation carries a question with it, not a gap in memory.
Why the gap stays invisible
Most teams don't see this problem because they're not measuring the thing that would reveal it. Open rate and click rate both look fine on a standard flow. SMS opens run north of 90%. Email opens sit in the 20-30% range, treated as normal because that's what email has always done.
Neither number says anything about whether the shopper who had a question got it answered. The metric that would catch that is reply rate, and it rarely gets the same attention as open rate or click rate, because the automated sequence isn't built to act on a reply either way. A reply can sit in an inbox, technically trackable, and still never change what happens next. The gap sits underneath a dashboard that looks healthy, and it costs revenue nobody's watching for.
What happens when a shopper replies anyway
Some shoppers reply to the flow even though it was never built to listen.
A shopper adds a sweater to her cart, gets to shipping, and stalls. Your SMS fires: "still thinking about your order?" She texts back: "why is shipping $18?"
That reply lands somewhere, but nothing in the flow is built to notice it. Message two fires on schedule the next day anyway, same script, no acknowledgment she said anything. She doesn't buy, and the reason isn't a lack of interest. The one question standing between her and checkout sat unanswered while the schedule kept moving, and the tool kept talking past her instead of to her.
The same thing happens with sizing questions. "Does this run small?" gets asked all the time on apparel checkouts, and a scheduled flow has no way to catch it, let alone answer it correctly for that specific product. The next message fires on schedule, question or no question.
That reply was the entire opportunity. A flow has no mechanism to catch it.
Where the incremental recovery comes from
Conversational recovery works differently because it's built around the reply, not the schedule. A shopper hesitates, the message goes out, and if she responds, someone or something reads it and answers the real question. Shipping cost, sizing, return policy, whatever it is.
That's also why discount codes end up doing so much of the heavy lifting in a scheduled flow. When a tool can't identify the objection, a discount is the only lever left. It's a guess wearing an incentive as cover. A conversation doesn't need to guess, so it doesn't need to default to margin to close the gap.
Response rates on real two-way SMS run 45-60%. That number doesn't exist for one-way blasts or email, because one-way channels aren't built to be replied to. On top of a flow that's already running, a conversational layer that answers what shoppers ask typically recovers another 10-15% of what would've been lost.
Where this fits next to what you're already running
None of this calls for ripping out existing flows. Email still catches shoppers who never gave you a phone number. Welcome series, campaigns, non-cart automations all keep doing what they already do well.
The gap sits specifically at the checkout moment, in the reply. A conversational layer runs alongside the flow, targeting SMS-consented shoppers who abandon checkout, and picks up where the schedule runs out of ability to respond. It's additive. The flow keeps running. What changes is that it stops being the only thing standing between a hesitant shopper and an answered question.
The actual test
If you're not sure whether what you're running is a flow or a conversation, there's a simple test. Reply to it. Ask a real question, the way a shopper would.
If nothing happens, that's the gap, and it's not a small one. It's the difference between reminding someone their cart exists and closing the sale.
Curious what that gap is costing you?
Run a Revenue Proof →