E-commerce: cash-on-delivery confirmations only work if the customer answers
A retailer confirms every cash-on-delivery order by phone before shipping. When customers stopped answering, returns climbed. The reason was on the screen of the phone.
The call that decides whether the parcel ships
For a retailer selling mostly cash-on-delivery, the confirmation call is the main protection against fake and mistaken orders. A short call, “is this you, is the address right?”, saves a lot of return shipping. Orders that can’t be confirmed wait, and orders that wait get cancelled.
Over a couple of months the share of confirmations that connected got worse and worse. The call volume was the same. Returns went up, and the team kept blaming the courier.
Looking at the other end of the call
Someone finally asked what a customer sees. A test on a few handsets showed that the retailer’s main confirmation line was labelled as spam on one popular app, and another number from the pool showed a generic name belonging to a long-gone reseller. For the customer, it looked like one more robocall about a delivery.
A weekly sweep and a paper trail
The team put every confirmation number into a weekly campaign. Each run records what the number shows and captures a screenshot, so there is something to look at rather than a feeling that “the calls seem worse lately”.
- Lines that showed warnings were rested or replaced before the weekend peak.
- The screenshots went to the provider when a number needed cleaning up.
- Confirmation rates recovered, and the team stopped arguing with the courier.
It also changed how the retailer buys numbers. They now ask a provider for a trial batch and check it first, which has already saved them from at least one bad block.
Industry: e-commerce · Use case: cash-on-delivery order confirmation · Team: customer support and logistics
If this is your team
A cash-on-delivery business lives on the confirmation call, and the confirmation call lives on the first second of the ring. Run a free caller ID check on every line in the confirmation pool, on the carriers your customers actually use, and read the result the way the customer does: no name, wrong name or a spam warning all mean the order is not getting confirmed. Replace the worst lines first; even one burned block in rotation drags the whole pool’s answer rate down.
Then make the check part of onboarding for any new number range and repeat it on a schedule, because reputation labels appear without notice. Retailers who also send an order-confirmation SMS should time that message by route as well; the fintech OTP story shows how a route can quietly add minutes while reporting delivered.
Seeing the same thing on your own numbers?