ConvoHut
Ecommerce use case

They looked four times and left. Say something.

Most stores only react once something reaches the cart. But a shopper who views the same product four times in one session has already told you what they want — they just have not committed. That gap is where browse abandonment journeys work.

Free PDF. No email required.

At a glance

TriggerRepeated product views, no cart after 4 hours
GoalRestart the product conversation
Primary KPIProduct return rate
Messages1–2
Estimated setup timeUnder 20 minutes

What is browse abandonment?

Browse abandonment is when a shopper views products with clear intent — repeated views, long sessions, category depth — but leaves without adding anything to their cart. A browse abandonment journey follows up on that behaviour, usually with product context and an open question rather than an offer.

Key takeaways

  • Browsing intent is weaker than cart intent, so the message should be more helpful and less commercial.
  • Filter by intent depth, not just any product view, or you will message everyone.
  • Recommendation works better than urgency at this stage of consideration.
  • Suppress anyone already in a cart or post-purchase journey.

Why this leaks revenue today

01

The signal is invisible to most tools

Email platforms see opens and clicks. They rarely see that someone returned to the same product page three times in an evening.

02

Retargeting ads shout at everyone

You pay again for attention you already had, and the shopper sees a banner instead of an answer.

03

Nobody asks the obvious question

Something stopped them before the cart. A follow-up that asks outperforms one that pushes.

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.

Product viewed 3+ timesSession over 90 seconds on a productNo cart created in 4 hoursKnown contact with WhatsApp consent

What has to be connected

Browsing eventsWhich products and categories, how often, how recently
Customer historyPrevious orders, average order value, category preference
CatalogueRelated products, stock status and price for a useful recommendation
Suppression listAnyone already in a cart, post-purchase or support conversation

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

Product viewed 3+ times

Delay

Wait 4 hours

Condition

No cart created

Message

Send helpful follow-up

Then it branches on what the customer does

Asks about the product

AI answers from catalogue and policy

Wants alternatives

Journey sends two related products

No reply

Journey ends — no second push

Goal: Adds to cart or purchases — journey stops

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.

4 hours

Helpful, not commercial. At browse stage the shopper has not committed, so an offer reads as pressure.

Saw you were looking at the {product}. Anything you want to know before you decide?

48 hours

Reframes from one product to a choice. Often the original product was simply wrong, not too expensive.

If the {product} was not quite right, these two are the closest alternatives: {links}

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.

Saw you were looking at the walnut desk. Anything you want to know before you decide?
Is it big enough for two monitors?
It's 140cm wide, so two 27-inch monitors fit comfortably with room for a laptop stand.
Do you have it in oak?
Yes — same dimensions, in stock. Here's the oak version.

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.

Product return rate

Customers who come back to the product page after the message.

Assisted revenue

Orders that occurred after the journey, inside the agreed window.

Reply rate

The strongest early signal that the message was welcome rather than intrusive.

Suppression accuracy

How often someone was messaged who should not have been.

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 and events

    Product view events need to reach ConvoHut, which usually means the storefront pixel or app connection.

  2. 2

    2. Set the intent threshold

    Three views in a session is a sensible starting point. Lower it and you will message browsers with no real intent.

  3. 3

    3. Build the suppression rules

    Exclude anyone with an open cart, a recent order or an active support thread.

  4. 4

    4. Write one helpful message

    No discount, no urgency. Ask a question you can actually answer.

  5. 5

    5. Launch to one category first

    Prove the message works on your highest-margin category before you widen it.

Then tune it

Raise the threshold before you lower it

If reply rates are poor, you are usually messaging people who were never that interested.

Test question versus recommendation

Some catalogues convert better on 'anything you want to know', others on 'here are two alternatives'.

Cap the journey at one message

Browse intent does not justify a sequence. A second message is a test, not a default.

Questions this raises

How is this different from abandoned cart?

Cart abandonment follows a commitment. Browse abandonment follows interest. The intent is weaker, so the message should be more helpful and much less frequent.

Won't this feel like I'm watching them?

It can, if the message is worded as surveillance. Reference the product, not the behaviour: 'saw you were looking at the walnut desk' reads fine, 'you viewed this three times' does not.

What data do I need for this to work?

Product view events tied to a known contact. Without identity resolution you cannot message the browser, which is why this journey usually runs on logged-in or previously-known customers.

Should I include a discount?

Generally no. At browse stage there is rarely a price objection to answer, and a discount trains customers to hesitate deliberately.

How many messages should this journey send?

One, sometimes two. If a browse abandonment journey runs to three or four messages, it has stopped being helpful.

Does it work for considered purchases?

It works better. Longer consideration cycles produce more repeat views and more genuine questions, which is exactly what a two-way channel is for.

Related use cases

Free download

The Browse abandonment 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.

Browse abandonment 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