NL Flipkart
NL Flipkart
Actors Involved
Flipkart isn’t just another online store – Objective
it’s a giant marketplace where you can find
pretty much anything you can imagine. As a Product Manager of the post-
With over 80 million products across 80+ purchase experience team at
Flipkart, propose a solution to turn Customer Customer Logistics Product Seller/
categories, Flipkart boasts one of the
the post-purchase flow into a Support Partners Team Brands
widest selections in India
moment of delight and trust Actors & Constraints
Key Stats
Full screen
$35 2.5
48% ₹70,844
billion Million
Private Commission
labels from sellers
42.1% 68.4%
Many users hesitate to trust Flipkart’s Users want features like live
post-delivery support due to past delivery maps, WhatsApp support,
negative experiences or inconsistency. and return hotlines.
Interview Insights 1:1 Interview
Lack of Visibility Creates Anxiety: Users feel powerless once the order is
placed. They don’t just want to track; they crave predictability, ownership,
and reassurance.
AI Communication Breaks Trust: Many users feel ignored and disconnected
Hypothesis when support is AI-driven or lacks proactive outreach.
Poor Coordination Wastes Time: Working professionals want more control
“Post-order, users feel a lack of control and proactive care, over timing, especially for large appliances or installations.
especially for expensive items, leading to anxiety and reduced Desire for Enhanced Features: Users suggested that Flipkart should have
trust.” features like real-time tracking, rescheduling as per time availability and
whatsapp notification for enhancing the trust.
Users are facing issue with returns and customer support services Problem Framing Canva
What is the true problem?
User Persona
Flipkart customers deal with post purchase issues due to:
Name: Sanskar Shukla Age: 24 Why? Lack of real-time visibility into orders, returns, or repairs.
Occupation: Senior Executive City: Kolkata Why? No dedicated support for high-value orders, leading to slow
Goal: Wants a seamless, stress-free post-purchase and inconsistent resolutions.
experience, especially for expensive gadgets like Why? Absence of a single, transparent communication channel,
smartphones and laptops. causing trust gaps and frustration.
Pain Point: Worries about complicated return or
replacement processes if the product is defective. Who's Facing This Problem?
25-40 years old young urban professionals living in metro cities are
Name: Divyanshi Pandey Age: 25
especially affected by post-purchase issues on Flipkart.
Occupation: Service Account Manager City: Gurgaon
Goal: Needs reassurance that if something goes How do we know it is a real problem?
wrong with her high-value purchase (like premium Qualitative: Data shows many Flipkart customers are dissatisfied
fashion or appliances), it will be resolved quickly and with delayed returns, unclear product status, and slow resolutions.
professionally.
Pain Point: Finds it frustrating to deal with multiple Quantitative: Customer feedback reveals frustration over the lack of
customer support channels for a single issue. real-time tracking and dedicated support, leading to a loss of trust.
Auto command
center badge
will come Users can
view detailed
summary by
clicking here
users can
reschedule
delivery and
installation
Priority
resolution
within 3 hours users can track
real-time
location
The user adds the high-value item to New centralized page will be there Users can view the hub location and
their cart under command center option also can track real-time location
Wireframing Figma link
Users will
receive
milestones
notification Users view the
along with details of the
image of item technician
Users can
reschedule
from chats also
User can chat
as well as can
call the
technician
After clicking on Issues & escalation WhatsApp notification for every Dedicated page of installation, which
agent will respond within 3 hours milestone with attached image of item will contain details of technician
North Star Metrics: Decrease in average customer resolution time and increase in first-contact resolution rate.
Guardrail Metric: No significant increase in escalation volume or drop in customer satisfaction after implementation.
% of users who interact with at least one feature in Command Track initial user engagement with the
Center interface.
Activation CTR on proactive tips or help nudges shown within the Measure the effectiveness of prompts and
Command Center. the UX layout.
# of repeat users within 7 days of first visit to the Command Understand ongoing adoption beyond one-
Center. time use.
Adoption Distribution of users engaging with multiple modules (e.g., Gauge comfort with using self-service tools.
refunds, return, delay help).
Average time spent on Command Center per session. Assess user confidence and success in
Engagement # of issues resolved via self-service without contacting resolving queries.
customer support. Measure the usefulness of the tools in place.
% of users who resolve their issue and return to the Command Gauge long-term usefulness.
Retention Center in the future. Indicate user trust in the feature for future
- % of users who rate their resolution experience positively. problem-solving.
The solution can still have a concerns for real-time syncing and a lack of engagement.
Pitfalls
System Design
1. Information Overload:
Problem: If too many notifications (status updates,
service reminders) are pushed, users might feel spammed
and ignore the Command Center.
Mitigation:
Prioritize and personalize notifications: Only show
meaningful status changes. Use user-controlled
notification settings (frequency, type).
2. Mismatch Between Updates and Reality:
Problem: If Command Center shows real-time status but
actual ground operations (like delivery or service teams)
are delayed or wrong, trust will erode.
Mitigation:
Backend Health First, Command Center Next: Display
estimated ranges with disclaimers to set expectations.
3. Technical Glitches/Delayed Data Sync:
Problem: Real-time syncing across warehousing,
logistics, and service partners could fail or lag, making
Command Center unreliable.
Mitigation:
No Surprises. No Ghost Updates: Build Command
Center on event-based architecture (Kafka or Pub/Sub)
with fallbacks for latency. Gracefully handle stale data by
indicating last update time clearly.