We call your buyer, resolve the reason code, and write the fix back to your courier before the SLA closes.
Built by engineers from
Part of immersion programme by
Powered by startup programmes
23 of every 100 parcels come back
Sources: GoKwik · Shipway FY25 · Unicommerce 2026
Every returned parcel passes through exactly two moments where a conversation can still change what happens to it.
Contact rates halve after the first half hour. We call while the purchase is still in the buyer's head.
We re-attempt on the pickup windows when Indian mobiles actually connect. If every attempt fails, your rule decides.
Delivery was attempted and failed. The courier hands you a reason code and 24 to 48 hours to answer it.
Six codes cover almost every failure. Each one has a conversation that resolves it, and the agent runs that conversation.
The corrected address and the new slot reach the rider, not just your dashboard. Inside the courier's own response window.
A reason code is a question nobody answers.
“Kal shaam 6 se 8 ke beech aap ghar par rahenge?”
Will you be home tomorrow between 6 and 8pm?
An illustration of the conversation, not a recording of a customer.
“Yeh office address hai ya ghar ka? Office hai to lunch ke baad bhej dein?”
Is this an office address or your home? If it is an office, shall we send it after lunch?
An illustration of the conversation, not a recording of a customer.
“Building ka landmark aur floor bata denge? Ek alternate number bhi le lein?”
Could you tell me the building's landmark and floor? May I also take an alternate number?
An illustration of the conversation, not a recording of a customer.
“Abhi cash arrange karna mushkil ho to payment link bhej doon? Delivery kal ho jaayegi.”
If arranging cash is difficult right now, shall I send a payment link? Delivery will happen tomorrow.
An illustration of the conversation, not a recording of a customer.
“Kal koi delivery ke liye aaya tha? Nahi aaya, theek hai, main dobara bhijwata hoon.”
Did anyone come to deliver yesterday? Nobody came, understood, I will have it sent again.
An illustration of the conversation, not a recording of a customer.
“Koi dikkat hui thi order mein? Batayein, dekhte hain kya kar sakte hain.”
Was there a problem with the order? Tell me, and we will see what we can do.
An illustration of the conversation, not a recording of a customer.
“Hello, this is Apriori. Your order could not be delivered yesterday. The courier says the address is incomplete. Could you tell me your building's landmark? … Noted. Shall we send it tomorrow between 6 and 8pm?”
Illustrative call. A real example of what the agent does on an incomplete-address reason code, not a recording of a customer.
Code-switched Hindi and English on a noisy line, regional accents, traffic behind the buyer.
Checks the corrected address against the pin code before it commits the reschedule.
Writes the new slot and address into Shiprocket, inside the courier's own response window.
A press-one bot can confirm an order. It cannot ask why you refused the parcel.
A corrected address that dies in a dashboard is worth nothing. We write back to the courier.
Every line above is being checked against a live call before it stands as a specification. Ask us to demonstrate any of them.
Stores and couriers we write back to
Connected in a day. Courier write-back wired the same week. Ask about another courier
Ask us what is connected today and what is a week of work, and we will tell you which is which.
Every call is recorded and transcribed. Every outcome is logged. Every instruction we send your courier is timestamped. Open any order and read the whole story.
Give us your failed deliveries for two weeks. We’ll call them, fix them, and show you every call we made.
20-minute call · no integration needed to start