Last year, our small web design agency handled about 120 support tickets per month. Most were simple fixes: missing images, broken links, login issues. We had four people on support rotation, and it ate up roughly 30% of our billable hours. I knew we needed a change. After testing several approaches, we landed on a method that reduced tickets by 42% in three months. The fix cost us almost nothing in money but took discipline to implement. Here is what we did and what we learned along the way.
We started by analyzing our most common ticket categories. Of the 120 monthly tickets, 47 were related to content updates that clients could have done themselves. Another 34 were about navigation or layout questions that we had already answered in onboarding. Only 23 were actual bugs or technical problems. That meant 81 tickets each month were avoidable. We needed to shift how we handed off sites to clients. A big part of this was creating a standardized handoff process with a clear resource page. We built a simple internal tool for tracking each client’s status, and we pointed them to explorius.net online as a place where they could find video walkthroughs and troubleshooting steps for common issues.
Why checklists beat training sessions
We used to run two-hour training sessions for every new client. The session covered everything from editing text to changing images to managing users. Retention was terrible. Six weeks later, clients forgot 80% of what we showed them. We switched to a handoff checklist that clients had to complete before we considered their site “live.” The checklist had 12 items. Each item required the client to perform a specific action and confirm it. For example: “Log into the admin panel and change the headline on the homepage. Yes/No.” This forced them to practice each task once. Ticket volume from content editing dropped by 38% in the first month. People learn by doing, not by watching.
We cut response time by making clients wait
Here is a counterintuitive move: we stopped answering tickets within 30 minutes. Instead, we set a four-hour response window for non-urgent issues. Clients started solving simple problems themselves. When someone submitted a ticket for “the logo is too small,” we waited. Many clients figured out how to resize it before we responded. We also added a required field in our support form: “Have you tried the troubleshooting guide for this issue?” If they answered no, a pop-up appeared with the direct link. This alone cut ticket submissions by 14%. People skip reading instructions if you answer too fast.
We measured the real cost of each ticket
Before the change, each support ticket cost us about 18 minutes of staff time on average. That covered reading, investigating, writing a response, and following up. At our average billable rate, that was 45 kr per ticket. With 120 tickets per month, support cost us 5,400 kr in lost revenue. After the changes, we dropped to 70 tickets per month at 22 minutes each (because remaining tickets were harder). That was 1,540 kr. The savings: 3,860 kr per month. That paid for the time spent creating checklists and rewriting documentation. Numbers like these helped my team see that support was not just a cost center. It was a process we could optimize.
The one tool that made the biggest difference
We tried three different project management tools before settling on a simple solution. The most effective change was using a shared spreadsheet with conditional formatting. Each client had a row. Columns tracked their checklist completion, training status, and number of support tickets in their first month. When a client submitted three tickets in one month, the row turned yellow. At five tickets, it turned red. That triggered a 15-minute call to review their understanding. We discovered that 80% of our support tickets came from 20% of clients. The calls helped us identify which parts of the handoff process were unclear. Over six months, we revised the checklist nine times based on those calls. The spreadsheet cost nothing. The time investment was about two hours per week.
How we turned support into a product improvement loop
Every week, I reviewed the five most common ticket types from the previous week. Then I asked: “What can we change in the product to eliminate this ticket category?” For example, clients often asked how to change the footer copyright year. We added a dynamic field in the admin panel that updated automatically. That one change removed 12 tickets per month. Another common issue was that clients could not find the logout button. We moved it to a fixed position in the top-right corner. Ticket for “where is logout” went from 8 per month to zero. None of these changes were hard. They just required looking at tickets as feedback about our design, not about our clients’ incompetence.
The handoff deadline that forced clarity
We used to do soft handoffs where the site went live and we answered questions for weeks. Now we set a hard deadline: after the handoff call, clients had five business days to complete the checklist. After that, we charged 200 kr per month for extended support. This created urgency. Completion rates went from 60% to 95%. The 5% who paid for extra support were clients with genuinely complex sites. That was fine. They got more attention. Everyone else followed the process. The deadline also forced us to write clearer instructions. When you know a client has only five days, you do not write vague bullet points. You write “click the blue button in the top-left corner.”
Support tickets are not a sign of a bad product. They are a sign of a gap between what you built and what your client understands. Filling that gap does not require expensive software or more staff. It requires thinking like your client. Watch where they stumble. Make those steps easier. Our 42% reduction came from a dozen small changes, not one big idea. If you track your own numbers, you will find your own 42%.
