Recart is a Salesive app that tracks abandoned carts for Ola. It has a merchant dashboard, tracks signed-in shoppers, sweeps lazily on every read and runs a serverless daily sweep. It does not send recovery messages by itself: you pair it with a workflow and, for customers outside the WhatsApp window, an approved template.
What does Recart actually track?
Recart tracks carts that belong to signed-in shoppers. That is the important boundary. A shopper who adds something to a cart and never signs in is outside what the app can reliably see, so the cart you most want to recover may not appear in the dashboard at all.
The merchant dashboard lists the carts it has captured, with the shopper and the items. It is built for Ola, which means the assistant can work from the same information when a shopper comes back and asks about the thing they left behind.
Treat Recart as a record of intent, not a guarantee. A cart in the dashboard means someone signed in and did not finish. It does not tell you why, and it does not mean the shopper wants a message.
How does the sweep work?
Recart sweeps lazily on every read. When you open the dashboard, it checks for carts that need attention at that moment rather than relying on a background job that may have run hours ago. There is also a serverless daily sweep cron that catches what nobody looked at.
The practical effect is that the dashboard is fresh when you use it, and still gets a daily pass when you do not. It is not a real-time stream. If a shopper abandons a cart at 10am and you open the dashboard at 10:05am, the lazy sweep is what shows it to you.
Do not build a process that assumes every cart appears within seconds. Build one that checks the dashboard at the times you actually work, and let the daily sweep cover the rest.
How does Ola use Recart?
Ola can use Recart's tools even while the Recart interface is closed. That matters because the shopper usually comes back through a conversation, not through your dashboard. They ask whether the item is still available, or whether their cart was saved, and Ola can answer from the same record.
This is where the app earns its place. A cart record on its own is a list. A cart record the assistant can act on is a chance to finish the sale without you opening another tab.
It also means you should keep the cart data clean. If your team edits orders or clears carts manually, tell Ola what that means, or the assistant may describe a cart that no longer exists.
How do you build the recovery workflow?
Recart identifies the cart. Workflows sends the message. Those are two separate jobs, and keeping them separate is what stops the app from becoming a spam machine. You build a workflow with the trigger and action you want, then decide who should receive it.
For WhatsApp, the same window rule applies. Inside 24 hours of the shopper's last message you can send free text. Outside it, you need an approved template. Salesive lists templates live from Meta, and approval is Meta's decision, not Salesive's.
One reminder is usually enough. A short message that names the item and offers a route back to the cart does more than three messages that repeat the same thing. If you add a second step, make it a different message with a different reason, not a louder copy of the first.
Decide what happens when the shopper replies. A recovery message that invites a reply but has nobody watching the inbox is worse than no message. Route replies to a person or to Ola, and check that the handover works.
What will Recart not do?
It will not recover every cart. Signed-out shoppers, cleared carts and carts that belong to someone who never returns are all outside the result. It will not send a message without a workflow, and it will not bypass the template rule on WhatsApp.
It also will not tell you why the shopper left. Price, delivery cost, a slow page and a change of mind all look the same in a cart record. Use the message to ask, not to assume.
And it will not replace your checkout. If the checkout itself is confusing, recovery messages only bring people back to the same confusion. Fix the checkout first, then recover the carts.
A recovered cart is a second chance at a sale, not a promise that the shopper wanted one more message.
How do you measure recovery?
Compare the carts Recart records with the orders that follow. Look at the dashboard over a week, not a single day, because the daily sweep and the lazy sweep produce different rhythms. A cart that is recovered on Thursday may have been abandoned on Monday.
Do not attribute every order after a message to the message. Some shoppers were always going to come back. The useful question is whether the recovery flow changes behaviour at all, and the only honest way to answer it is to compare a period with the flow against a period without it.
Watch the unsubscribe and block rate as closely as the recovery rate. A flow that recovers a few carts and annoys everyone else is a net loss, especially on WhatsApp where a block is permanent.
Frequently asked questions
Does Recart send recovery messages on its own?
No. Recart tracks and records carts. Sending needs a workflow, and WhatsApp messages outside the 24-hour window need an approved template.
Does Recart track shoppers who are not signed in?
It tracks signed-in shoppers. A guest cart is outside what the app can reliably associate with a person.
How often does Recart update?
It sweeps lazily on every read, so the dashboard is fresh when you open it, and a serverless daily sweep runs once a day.
Can Ola use Recart when I am not in the dashboard?
Yes. Ola can use Recart's tools even while the Recart interface is closed.
Will every abandoned cart come back?
No. Recovery depends on the shopper, the message and the checkout. Recart gives you the record, not the outcome.
Recart is most useful when you treat it as one part of a flow: it records the cart, a workflow sends one honest message, and a person or Ola handles the reply. The integrations page shows how apps sit alongside the rest of Salesive, and features covers Workflows. To build the message itself, read build a WhatsApp order-confirmation workflow, and for the wider automation picture, see email campaigns that respect the do-not-email scope.