
How to rebuild trust with a customer who just received a flawed device
Express Replacement — a next-day device replacement experience designed to resolve delayed responses and rebuild customer trust, reaching 87-89% customer satisfaction rate.
Category
E-commerce feature
Dates
Dec 2024 - Oct 2025
Market
France
Role
Product Designer
CONTEXT
The worst first impression
Customers order a refurbished device expecting one thing above all: that it works the day it arrives. Some don't — a flawed screen, a battery that won't hold charge, a device that fails to power on. For a small share of orders, day one is the day everything breaks.
This is a fragile moment for trust. The customer didn't do anything wrong, the product failed them immediately, and the traditional process asked them to wait through uncertainty on top of that. Express Replacement was our answer: instead of an open-ended support case, let the customer request a replacement immediately — shipped next-day — while keeping the flawed original in hand until the new device arrives.
I designed the end-to-end experience: the customer-facing journey flows, and the complex agent-side task flows that make the next-day promise operationally possible.
DISCOVERY
Learn from the people who handle it every day
A next-day replacement flow isn't a pure design problem — it sits on top of logistics, inventory, payments, and customer service operations. Before touching a single screen, I conducted cross-functional stakeholder interviews to build domain knowledge:
Customer service agents — what customers actually say and fear when they report a fraud device, and where escalations come from.
Logistics & inventory — what "next-day" really costs, and how replacement stock is managed
Payments & risk — what the business is exposed to if a customer keeps two devices and never returns the original
Two findings shaped everything that followed:
The anxiety wasn't the flaw itself — it was not knowing what happens next. Customers could accept that a device shipped defective; what they couldn't accept was an open-ended wait with no visibility into when it would be resolved.
Sending a replacement before the original comes back is a real cost exposure. For a moment, the business is shipping a second device while the first — still its asset — sits with the customer. Without a mechanism to guarantee its return, "keep using yours while we send a new one" is financially risky at scale.
DEEP DIVE
Reassurance vs. business exposure
This was the central tension of the project, and it pulled in opposite directions on every screen:
THE CUSTOMER NEEDS
THE BUSINESS NEEDS
A working device fast, no extended wait
The original device recovered before writing it off
To feel like the mistake isn't theirs to fix
A guarantee that covers the device fee if it isn't returned
A simple, low-effort request
Enough detail on the flaw to process without back-and-forth
To keep something usable in the meantime
Finite replacement inventory allocated responsibly
HMW reduce customer anxiety during the replacement delivery process — while managing business constraints like logistics, inventory, and CS escalation?
Entry point — position it as the fastest way out
When a customer reports a device issue, they see their options side by side. Express Replacement is labeled "Fastest solution", with the promise stated in plain terms: keep using the original while a replacement ships, then send the original back once the new one arrives. Live chat remains available — the feature is an offer, never a wall.
Explainer — honesty upfront as reassurance
Return preparation — a guided task, not a chore
Documenting the issue, reframed as speeding things up
Photos and a short description of the flaw aren't a checkpoint the customer has to clear — they're what let an agent process the request without a back-and-forth. Framing it as "help us get this right the first time" turns a form into a way for the customer to feel the process moving, not stalling.


The credit card check, reframed as a formality
This was the requirement most likely to feel adversarial, so it needed the most careful framing: customers confirm a valid credit card as a guarantee — not a charge. They're only billed the original device's fee if they miss the return deadline. The copy makes this explicit and sequential: "No charge to your account… you may see a €0 charge to check your card is valid. You'll only be charged if the original isn't returned in time." Stated this way, it reads as the standard cost of a fast, flexible option — not as the business questioning the customer's honesty.
Confirmation — "You're all set"
The final screen answers the only question that matters: what happens now? A concrete delivery window for the replacement, a printable return label and proof of purchase, and a visible path to more help. The customer leaves the flow with documents in hand and zero open questions — which is exactly what keeps them out of the CS queue.
RESULTS
Adopted as the preferred resolution path
67–70%
adoption rate among eligible customers
€27K
GMV generated per day — orders saved from refunds
87–89%
overall STAR, from customers whose device didn't work on arrival
LEARNINGS
What this project taught me
01
Domain knowledge is a design deliverable.
The stakeholder interviews weren't preparation for the design — they were the design. The return-deposit mechanism only became explainable, not alarming, once I understood exactly why the business needed it.
02
Reassurance is content design.
The flow's screens are ordinary e-commerce patterns; what rebuilt trust was the words — reasons attached to requirements, and "what happens next" on every step.
03
A guarantee explained is a formality; a guarantee unexplained is an accusation.
Same credit card check, same deadline — the only variable that mattered was whether the customer understood why it existed before they hit it.
