We Review Every Support Ticket as a Team Every Friday

Philip Rehberger Feb 21, 2026 2 min read

Even the "stupid questions." Especially the stupid questions. Here's why.

We Review Every Support Ticket as a Team Every Friday

We review every support ticket as a team every Friday.

Even the "stupid questions."

Especially the stupid questions.

Why we started:

We used to categorize tickets: → Bugs (important, fix them) → Feature requests (track them) → User confusion (send docs link)

That last category was our blind spot.

We dismissed user confusion as a documentation problem. "They just didn't read the guide."

But confused users aren't the problem. Confusing products are.

The shift:

Now every Friday, we pull up that week's tickets. All of them.

We ask: "Why did this person have to contact us?"

Not to blame them. To understand what we could improve.

What we've found:

Last month: 12 tickets asking the same question about file uploads.

Old us: Write better docs about file uploads.

New us: The file upload UI is confusing. Let's redesign it.

We didn't document our way out. We designed our way out.

The results:

→ Support tickets down 40% over 6 months → Same questions stop recurring → Everyone on the team understands user pain → Product decisions are informed by real feedback

The mindset:

Your customers are telling you how to improve.

Every ticket is a gift. Every confused user is showing you where your product failed them.

You just have to listen.

What's the last thing you improved based on customer feedback?

#CustomerExperience #ProductDevelopment #SoftwareDevelopment #LessonsLearned

Share this article

Related Articles

Need help with your project?

Let's discuss how we can help you build reliable software.