Three calls every store already wishes it could make.
COD returns, wrong addresses and failed deliveries all have the same fix: a short, polite phone call before the parcel moves. That's the whole product.
COD confirmation
Called within minutes of the order.
- A confirmed yes before the parcel is packed
- Cancellations caught, with the reason recorded
- Prepaid switch offered when it ships sooner — never pushed
- “Call me later” honoured, and retried once
Address check
Read back and corrected on the call.
- Flat number, landmark, pincode confirmed aloud
- Corrections written straight back to the order
- Preferred delivery slot: morning or evening
- The wrong flat is caught before the courier is
Failed-delivery follow-up
Instead of a second silent attempt.
- Ask what happened, in the customer's words
- Agree a retry day and time
- Flag the ones that should be cancelled
- Every outcome written back, nothing lost
Confirmed, corrected, and back in your system.
Short and plain — your customer is not a guest at a wedding. The order is confirmed, the flat number fixed, the slot agreed, and the order card updates as it happens.
Illustrative — the product is not live yet.
“Confirm kar dein?” — in Hinglish.हिन्दी.English.
Per store, or per customer from the order's language. Nothing is fixed in the script — the opening line and questions are set from the dashboard.
Sized by orders a month. Priced when it's ready.
Tell us your volume and the one problem that hurts most. Early-access stores get the first weeks free in return for honest feedback.
Small store
Instagram sellers · one-person D2C
- COD confirmation on every order
- Address read-back and correction
- Daily sheet of outcomes
Growing brand
Where COD returns start to hurt
- Everything in Small store
- Delivery-slot preference
- Failed-delivery follow-up calls
- Prepaid switch offered on the call
Scale
Multiple brands · courier integrations
- Everything in Growing brand
- Order feed and write-back by API
- Outcomes shaped for your courier panel
Before you send us an order list.
When will it be live?+
The wedding product is live and the same engine runs this. We're building the order-specific parts — order feeds, write-back, the courier side. Early-access stores are called with us in the room before anything runs unattended.
Will customers find a call annoying?+
A COD confirmation is a call customers already expect from the courier — ours just comes sooner, in their language, and under a minute. It introduces itself as an automated call on behalf of your store, by name.
What if the customer doesn't pick up?+
One retry a few hours later, inside the hours you set. After that the order is marked unconfirmed in your sheet, so you decide — ship anyway, or hold.
How do orders get in and results get out?+
At first, a CSV export from your store and a daily sheet back. Order feeds and write-back by API are planned for the Scale tier.
What happens to customer data?+
Transcripts are kept only for the retention period you set, then deleted. Customer lists are yours — never reused, shared or sold.
Need calls for a wedding or an event?
That part of Shubh is running today — invitations, attendance, headcount, in Hindi and English.
Weddings & events →Tell us about your store.
Opens WhatsApp with your details written out. We'll reply when there's a date, and sooner if your volume fits the first batch.