Every repeated question is a product defect wearing a costume. Treat the ticket list as a roadmap.
Support at an early startup is two things at once: helping customers, and the highest-quality product feedback channel you have.
The scaling approach is to categorise tickets and remove the causes, rather than to answer faster.
Because support volume that grows linearly with customers eventually consumes the company. If 100 customers generate 60 tickets a month, 1,000 customers generate 600 — which is a full-time team answering the same questions.
And because founders should do support early. It is the fastest way to know what is genuinely wrong with the product, and it is the thing most reliably delegated too soon.
A month of tickets, categorised:
Category — Volume — Real cause
'How do I import my drivers?' — 22 — The import button is below the fold
'Why did it schedule this way?' — 14 — No explanation shown in the UI
Billing questions — 9 — No invoice history page
Password resets — 7 — Reset email in spam
Genuine varied questions — 8 — —
52 of 60 tickets have a product cause. Moving one button removes 22 tickets a month permanently. Adding an explanation line removes 14.
The instinct is to hire someone to answer 60 tickets. The better move is to spend three days on the top two causes and reduce it to about 24, then reassess.
Every repeated question is a product defect. The ticket list is the most honest roadmap you will ever be given, and it is free.
First-time founders often optimise response time rather than ticket volume. Answering the same question quickly forty times is worse than answering it zero times.
The second mistake: delegating support before understanding the patterns. Do it yourself until you can predict what the next ticket will be — that is when you have learned what support has to teach you.
The third: not tagging tickets. Without categories you cannot see the pattern, and the pattern is the entire value.
Even roughly. Without categories you cannot see the pattern, and the pattern is the point.
Sorted by volume. The top two are your product roadmap for the week.
A help article is a workaround for a confusing product. Sometimes correct, usually second best.
For questions that will genuinely always exist, a saved reply is fine and fast.
That is the point at which you have extracted the learning and can hand it over.
Total rising with growth is expected. Tickets per customer rising is a warning.
From your first customer. The categorisation habit matters more as you grow.
Do not build a support system for twelve customers. Email is fine; the tagging habit is what matters.
Apply this to your own startup in My Full Journey (free account).