Don't make customers file a complaint, walk them through it
When a delivery goes wrong, the worst thing you can show is a blank 'describe your issue' box. You'll lose the signal exactly when you need it most.
When something goes wrong with a delivery, the worst possible thing you can put in front of an upset customer is an empty text box that says “describe your issue.”
It feels fair and open. It is actually a trap, for both of you. The customer, already annoyed, now has homework: articulate the problem, in writing, well enough for a stranger to act on. Most won’t. They’ll type “bad” or “terrible service” or nothing at all, and close the app. You’ve taken the one moment they were willing to tell you something and spent it asking them to do your categorization for free. The signal you most needed arrives as mush, or doesn’t arrive.
The blank box optimizes for the wrong person
A free-text box is easy to build, which is exactly why it’s everywhere. It optimizes for the developer’s afternoon, not the upset customer’s ten seconds. And it quietly throws away structure you could have had for nothing.
The ride-hailing apps worked this out long ago, and I just borrowed it. When a trip goes bad, they don’t hand you a void. They walk you through it: was it late, was the item damaged, was it the wrong order, was the driver rude? You tap. You’re done. Behind one or two taps the complaint arrives already sorted into a category your team can act on, with a rating attached.
- Guide, don’t interrogate. Offer the handful of things that actually go wrong, in plain words, as tappable options.
- Categorized at the source. The customer’s tap is the triage. Nobody on your side has to read mush and guess which bucket it belongs in.
- Pair it with a rating. A number turns scattered unhappiness into something you can sort, trend, and prioritize.
Structure is a gift to both sides
A blank box asks the angriest person you have to do your data entry. Guide them instead, and the complaint arrives ready to fix.
On the customer’s side, guided feedback respects that they’re upset and short on patience: a few taps, not an essay. On your side, it lands in a queue already labeled, with a rating and a clear way to act. You can see that “late” is spiking this week, or that one route generates all the “wrong item” reports, because the data came in structured instead of as a thousand unique sentences.
There’s a version of openness that’s really just laziness wearing a halo. “We let customers tell us anything” sounds generous. In practice it shoves the hardest work, naming the problem, onto the person least equipped to do it in that moment. The kinder and smarter thing is to do that work for them, ahead of time, and let a tap carry the meaning. Make it easy to complain well, and you’ll actually hear what’s wrong.