ConvoHut
Ecommerce use case

Recover carts while the customer still wants to buy.

A cart left behind is not a lost customer. It is a customer who hit a question, a doubt or a distraction between the product page and the payment page. ConvoHut reopens that moment as a conversation instead of a reminder.

Free PDF. No email required.

At a glance

TriggerCart created, no purchase after 20 minutes
GoalRecover the purchase
Primary KPIRecovered revenue
Messages2–3
Estimated setup timeUnder 15 minutes

What is WhatsApp abandoned cart recovery?

WhatsApp abandoned cart recovery detects when a shopper leaves items in their cart without buying, then starts a personalised WhatsApp message shortly after. Unlike an email reminder, the customer can reply — so the objection that stopped the purchase gets answered in the same thread.

Key takeaways

  • The trigger should be the customer's behaviour, not your send schedule.
  • Most abandoned carts stop on an unanswered question, not on price.
  • A message the customer can reply to converts better than one they cannot.
  • Agree the attribution window before launch, or the numbers mean nothing.

Why this leaks revenue today

01

You already paid for the intent

Acquisition cost is spent the moment they reach checkout. A cart that goes unanswered wastes the most expensive traffic you buy.

02

The reminder arrives too late

Batched sends reach a customer hours later, when the moment and the context have both gone.

03

Nobody finds out why they stopped

A one-way reminder cannot ask. So the same objection stops the next hundred shoppers too.

The signal ConvoHut acts on

The journey only starts when all of these are true. Getting the entry conditions right matters more than the message.

Checkout startedNo purchase after 20 minutesContactable on WhatsAppCart value above threshold

What has to be connected

Cart contentsProducts, variants, quantities and total value
Customer recordName, purchase history, lifetime value, segment
CatalogueImages, sizing, stock and policy context for replies
ConsentA valid WhatsApp opt-in and the channel the customer expects

The journey

Built once, then it runs unattended. Every branch has a defined outcome, and the journey stops the moment the goal is met.

Trigger

Cart abandoned

Delay

Wait 20 minutes

Condition

Cart value > threshold

Message

Send personalised WhatsApp

Then it branches on what the customer does

Asks a question

AI answers inside your rules

Clicks through

Straight to a prefilled checkout

No reply

Second message at 24 hours

Goal: Purchase — journey stops immediately

A journey without a stop condition is a journey that gets your number blocked.

The messages, and why each one exists

Starting points, not scripts. You rewrite them in your own voice and approve every message before it goes live.

20 minutes

Opens as a question, not a demand. Gives the customer an easy way to reply with the real objection.

Still thinking about the {product}? Happy to answer anything before you decide.

24 hours

Names the two most common objections so the customer only has to confirm one.

No rush on the {product} — just checking whether sizing or delivery was the sticking point.

72 hours

Ends cleanly. A journey that will not stop is the fastest way to get blocked.

Last note from us. Your cart is still saved here if you want it: {link}

What it looks like to the customer

This is the part a broadcast tool cannot do. The customer replies, the question gets answered from real data, and the journey continues — in one thread.

If the AI reaches the edge of what it has been approved to answer, it escalates to your team with the full history attached. The customer sees one continuous conversation.

Still thinking about the black jacket?
Does it run small?
It has a regular fit. If you're between sizes we'd go one up. Want me to send the size guide?
Yes please
Here it is. Your cart's still saved — this link takes you straight back to it.

Illustrative conversation. Not a customer transcript.

What to measure

Pick one primary metric before launch and agree how it is calculated. Everything else is secondary.

Recovered revenue

Orders placed after entering the journey, inside the attribution window you agree.

Cart recovery rate

Journey entries that end in a purchase.

Reply rate

How many customers actually engage rather than just receive.

Revenue per conversation

Attributed revenue divided by conversations started.

How we keep this honest. The attribution window is agreed before launch. Direct and influenced conversions are reported separately. Where volume allows we hold out a control group. We do not claim every order that happens after a message.

Set it up

  1. 1

    1. Connect your store

    Authorise Shopify so ConvoHut can read carts, orders and customers.

  2. 2

    2. Import the playbook

    Start from the Abandoned Cart playbook rather than a blank canvas.

  3. 3

    3. Set your wait time

    Twenty minutes is the default. Test sixty against it once you have volume.

  4. 4

    4. Edit the message

    Rewrite it so it sounds like your brand. You approve every message before it goes live.

  5. 5

    5. Turn it on

    Run a test send to an internal number, then launch to a limited audience first.

Then tune it

Test 20 minutes against 60

Shorter is not automatically better. Some categories need thinking time before a follow-up feels helpful.

Answer the objection in message one

If sizing stops most of your carts, say so in the first message instead of waiting to be asked.

Stop discounting by default

A discount answers a price objection. Most abandoned carts do not have one — and you train customers to wait.

Questions this raises

Is this just another WhatsApp sender?

No. A sender delivers a message and stops. ConvoHut triggers on behaviour, branches on the reply, answers questions inside rules you set, and stops the journey the moment the customer buys.

Can customers actually reply?

Yes, and that is the point. Replies route to an AI agent working inside your approved product and policy information, and your team can take over the same thread at any moment.

Does it work with Shopify?

Shopify is the first supported platform, and the only one at launch. Check the integrations page for the current status of everything else before you assume it exists.

How is recovered revenue measured?

You agree the conversion definition and the attribution window before launch. Direct and influenced conversions are reported separately, and where volume allows we hold out a control group.

Will this feel spammy to my customers?

It depends entirely on the trigger. A message that fires because someone abandoned a cart twenty minutes ago reads as good timing. One that fires because it is Tuesday reads as spam.

What happens if they buy before the second message?

The journey stops. A stop condition on the goal event is set by default, and you should never run a journey without one.

Related use cases

Free download

The Abandoned cart Playbook, as a PDF.

Everything on this page in a document you can send to your team or your client: entry conditions, journey logic, the messages with the reasoning behind each one, the metrics and the setup steps.

No email required. Take it and build the journey somewhere else if you want to — the logic is the useful part.

Abandoned cart Playbook

PDF · 4 pages · Version 1.0

Download the playbook See all resources

Your customers are already showing intent.

Turn those moments into automated conversations that move customers toward conversion. We work with a small group of early access customers and set the first journey up with you.

Join the waitlist