Measured against a holdout, not asserted.
Every deployment starts by leaving part of the queue untouched, so the figures below are differences rather than claims. Here is what they came to.
The same parcel, twice.
Run at a health and wellness D2C brand, on the cohort where cash and address quality were worst.
Before Apriori
The reason code lands. The in-house queue reaches the buyer after the courier's window has already closed.
With Apriori
The same code, answered in minutes, written back to Shiprocket inside the response window.
How this was measured: Measured against a holdout cohort during the pilot. The brand is named once its written permission is in hand; the figures are unchanged either way.
Recovering margin for a health and wellness D2C brand.
The challenge
The brand was shipping the bulk of its volume on cash, and RTO on its riskiest cohort had settled well above the category benchmark. An in-house tele-calling team could not clear the NDR queue inside the courier's response window. By the time they dialled, the next attempt had already failed.
What we ran
Apriori was deployed across both windows, verifying risky COD orders before dispatch, and reaching the buyer within minutes of a reason code landing, with every resolution written straight back into Shiprocket. The tele-calling team moved onto high-AOV exceptions.
Alongside the RTO result, a meaningful share of called COD buyers accepted a payment link and converted to prepaid, shortening the cash conversion cycle.
We will name this brand here the day their written permission is in hand, and not a day before. If you would like to speak to them directly, ask us and we will ask them.
Why there is only one here.
Because there is only one we can publish. A page of invented logos is the cheapest thing on the internet to produce, and everybody reading it knows what it is worth.
What we can offer instead is a holdout on your own queue for thirty days, which produces a case study about you rather than about somebody else. How the holdout works