Courier marks 'consignee refused'; customer swears nobody came. Both can't be true — and the seller eats the RTO either way. The fake-refusal problem is real, the fixes exist, and OTP-verified delivery is the structural answer.
Why fake refusals happen
Rider metrics reward completion percentage — marking 'refused' closes the attempt without delivering. Or the delivery was genuinely attempted at a bad time and refusal was easier than retry. Either way, the remark isn't always the customer's decision.
The customer-verification step
Before accepting a refusal NDR, verify — WhatsApp the customer 'the courier marked refused — did you refuse?' Half the time the answer is 'nobody came' and the NDR is a fake refusal that re-attempts successfully.
The OTP-verified delivery fix
Request OTP-verified delivery on valuable orders — the shipment can't mark delivered or refused cleanly without the customer's OTP. The feature exists on most carriers; it's the structural answer to 'the rider said you refused'.
The pattern data
Track fake-refusal frequency per carrier and per area — a lane with chronic 'customer refused' complaints that customers deny is a courier-behaviour problem, not a customer problem. Escalate with the pattern.
Pakka Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Verify refusals with customers
'Did you actually refuse?' rescues half.
Request OTP-verified delivery
The refusal-proof delivery mode exists.
Track fake-refusals by lane
Pattern data is escalation ammunition.
Escalate repeat-offender hubs
The rider-metric problem is the hub's problem.
