Building Delivery Trust with ETA Transparency During Peak Hours
Three Swiggy features that make peak-hour delivery estimates honest instead of optimistic
✳The problem they went after
Working professionals and frequent Swiggy users stop trusting the app during peak hours, when optimistic ETAs prove wrong and nothing explains why. The fallout is missed meals, negative reviews, fewer repeat orders, and support ticket volume. The root cause is not the delay itself. It is the gap between what users were told and what happened, plus the silence once things change.
✳What they actually did
Three solutions score highest under RICE. An ETA Confidence Indicator labels each restaurant's estimate High Confidence, Medium, or Volatile using real-time variance data, so users can choose reliably rather than find out after ordering. A Peak Demand Badge appears at checkout before confirmation, setting expectations ahead of the commitment. Real-Time Delay Explanation Cards push updates mid-delivery that separate restaurant delays from rider congestion and multi-drop routing.
✳What you can take from it
Worth stealing
- Confidence labels driven by real-time ETA variance
- Expectations set at checkout, before the commitment
- Delay cards name the cause: restaurant, rider, or routing
- Guardrails on drop-off and compensation credit burn
Read this if
PMs in delivery or logistics where ETA accuracy drives retention
The transferable bitEach feature carries its own measure, confidence label adoption and repeat order rate, post-checkout cancellation rate, delay-affected CSAT, so none can hide behind the others. Guardrails on checkout drop-off and compensation credit burn name the obvious risk, that honesty about delays suppresses orders or runs up auto-credit cost.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
