For every customer who writes in, twenty had the same problem and said nothing.
I've never had a single support problem solved by AI. Not one. Not even a trivial one. And the fact that I have to fight through a bot just to reach a human is its own kind of insult.
This is what most companies now consider an upgrade.
You've shipped your product. Tickets are rolling in. Same questions, similar complaints. It feels like busywork pulling you away from building. So you start eyeing automation, a chatbot, canned responses, maybe a full AI layer.
Everyone does this. It's the first thing founders automate. I'd make it the last.
What the Spreadsheet Doesn't Show
The ROI of a support chatbot looks clean: fewer hours on tickets, faster resolution times, lower cost per interaction.
But every support ticket carries two things. The question on the surface, and the intelligence underneath. "How do I export my data?" is a question. The fact that twenty people asked it this month is intelligence. It means your export flow is invisible, confusing, or buried. That's your next product priority, handed to you for free.
Analytics tell you what happened. Support tells you why.
I've done support across a courier service, a food delivery platform, a marketing agency, and software products (dating service, coupon platform, publishing, etc.). The industries couldn't be more different. The pattern in the queue was always the same: customers tell you what's wrong on the surface, and underneath ten similar complaints sits a structural problem your metrics never surfaced. The specific complaints change with every business. The diagnostic pattern doesn't.
And the visible queue is just the tip. For every customer who writes in, roughly twenty had the same problem and didn't bother.² The issue you're seeing is twenty times bigger than it looks.
When you automate support, you're building a wall between yourself and the most honest feedback loop your product has.
AI Made It Worse
Before AI support, bad support was at least recognizably bad. You waited on hold, you got a scripted answer, you knew you were dealing with a system that didn't care.
Now bad support wears a mask. The chatbot sounds helpful. It asks clarifying questions. It radiates confidence. And it solves nothing. You end up in a loop, rephrasing the same problem three different ways, hoping the machine will finally understand what you need.
Most companies have made the bot a gatekeeper. You can't reach a human without first proving to an algorithm that your problem is real enough. An obstacle course with a customer service logo on it.
That's the customer's experience. From the operator side, it's worse.
The bot resolves tickets without you ever reading them. It classifies problems into categories that sound neat on a report but lose all the texture.
A frustrated user who would have written "I keep clicking the blue button and nothing happens" gets silently routed to "UI Bug - Resolved." You see a clean dashboard. You never learn that "the blue button" is actually your onboarding flow, and five people hit the same wall this week.
The bot doesn't just frustrate your customers. It makes you think everything is fine.
Rescued Customers Are Your Loudest Advocates
A customer who had a problem and was helped by a real human often becomes a stronger advocate than one who never had a problem at all.
Service researchers call this the service recovery paradox.¹ When someone hits a wall and a real person helps them through it, something shifts. They move from "this product works" to "these people care." The second feeling is the one they tell friends about.
Think about the last time you had a genuinely great support experience. You probably still remember the company. Now think about the last product that just worked fine. You probably can't name it.
Chewy sends handwritten sympathy cards when a customer's pet dies. A thousand hand-painted pet portraits every week. When Anna Brose tweeted about receiving flowers after her dog passed, it got over 600,000 likes. One moment of care that reached more people than most ad campaigns ever will.
Satisfied customers are silent. Rescued customers are loud. And that loudness is worth more than most ad budgets (which says a lot about ad budgets, but that's a topic on its own). A real user saying "I had a problem and they fixed it in ten minutes" carries more weight than your entire landing page (better still, put it on your landing page).
You cannot manufacture that with a chatbot.
Sit in the Queue
Founders doing support personally is one of those known success secrets everyone nods at and almost nobody follows. It keeps showing up on lists. It keeps being ignored. Because it feels like a step backward when you're supposed to be the CEO.
Jason Fried at Basecamp calls it "Everyone on Support" and rotates every employee through the queue, founders included. The reasoning is simple: stop hearing from users directly and you start building for an imaginary customer.
In my own ventures, when I have enough control over the operation, the approach is simple:
- Founders do support first. Always. No exceptions until the volume genuinely exceeds your capacity.
- When you hire for it, the instructions are short. Listen to the customer until they finish. Actually try to help them. And if you can't, help them understand why, even if the reason is company policy. We regularly part ways with clients who aren't a good fit, and we tell them why honestly.
That's it. In most markets, for at least the past fifty years, this is enough to become the best support in your category. The bar is that low.
But.
There's a trap in this, and it's worth knowing going in. The people who write support tickets are self-selected. They care enough to complain, or they're invested enough to ask for help. They're valuable. They're also not the whole picture.
The twenty who didn't write in? Some of them worked around the problem. Some of them are tolerating it. And some of them already left, with no ticket, no complaint, no signal.
The satisfied customers who have nothing to say are one kind of silence. The dissatisfied ones who gave up on you are another.
Sitting in the queue is necessary. But the people who reach out are always a biased sample.
Support tells you where the friction is for people who are still trying. It tells you nothing about the people who already stopped.
The mechanical parts (password resets, order tracking, basic FAQ) can and should be streamlined eventually (but not when you start). Everything else, every edge case, every frustrated user whose ticket doesn't match a template, keep that human. Those messy tickets reveal where your product's mental model diverges from your users'. That gap is where the real improvements live.
An AI agent may resolve the ticket. A human will hear the subtext.
The Product That Listens
Support is where your product talks back to you. Every other channel (analytics, surveys, interviews) gives you a filtered, delayed, partial picture. Support is raw, immediate, and honest.
The founders who understand this mine the queue. They read tickets the way a trader reads the tape, looking for signals everyone else is filtering out. But they also watch the exits: the users who go quiet, the trials that end without a word, the accounts that slowly stop logging in.
Your support inbox is a competitive advantage. The silence around it is a warning. Pay attention to both.
Rabbit Hole
If you're optimizing metrics instead of understanding your customers, you might be measuring yourself into irrelevance: Every Metric Is Green, the Customer Is Lost.
The most reliable demand signals come from what people do, not what they say: The Critical Demand Signals Nobody Talks About.
And if your signups look promising but nobody converts, your support queue might tell you why before your funnel does: Your Signups Are Lying to You.
- The service recovery paradox, first described by McCollough and Bharadwaj in 1992, shows that customers who experience a failure followed by strong recovery can end up more satisfied than those who never had a problem. Subsequent research has yielded mixed results, but the effect appears strongest when the failure is modest and the recovery feels personal and immediate.
- TARP (Technical Assistance Research Programs) found that for every customer who complains, 26 others remain silent. The piece uses "roughly twenty" as a conservative round number. Source: John A. Goodman and Steve Newman, "Basic Facts on Customer Complaint Behavior and the Impact of Service on the Bottom Line," Competitive Advantage (ASQ Service Quality Division), June 1999.