An agency launched a client's website a year ago. Since then, the client has emailed the project manager, messaged the designer directly and called the office about a broken form, a font that looks wrong, a request for a new page and a question about how to change a photo. None of it went through a proper process. Some of it was billed. Most was not.
Many agencies that build websites become unofficial support desks for everything they have ever launched. Redesigning how support works protects both the team and the client relationship.
How support creeps in
It starts with goodwill. A client asks a quick question after launch, and someone answers. Then another. Soon the agency has dozens of past clients, each with a direct line to someone on the team. Requests interrupt project work, deadlines slip, and nobody tracks how much time support actually takes. Deadline pressure is covered in timeline questions from clients who needed it yesterday, and support interruptions make it worse.
The problems with ad hoc support
- Requests arrive without the information needed to diagnose them
- There is no priority, so a typo and a broken checkout are treated the same
- The same how-to questions are answered again and again
- Time spent is not tracked or billed
- Clients do not know what is covered and what is not
A redesigned support process
1. One route in. Give clients a single support route, rather than individual team members' emails.
2. Capture the details. For each request, capture the website, a description, the page affected, when it started and screenshots if possible.
3. Triage by urgency. Separate "site is down" from "can you change this photo".
4. Answer how-to questions from documentation. Many requests are about using the site: editing a page, adding a blog post, changing an image. These can be answered from a help page.
5. Link to support plans. Make clear which requests are included in a support plan and which are billable changes.
6. Report back. Tell clients what was done and when.
Where an assistant helps
SpideyChat for agencies can be trained on your support documentation and client guides. It answers common how-to questions immediately and creates tickets for issues that need a developer, with the details captured. Clients get help faster, and the team only handles what genuinely needs them.
Onboarding documentation from the start of a project, covered in onboarding new agency clients without endless emails, becomes the basis of the support guide.
Lessons from property management
Property managers face the same mix of routine questions and urgent problems from tenants. They separate maintenance from sales for the same reason, as covered in tenant maintenance questions that should not clog sales and AI receptionist for property management.
Turning support into revenue
A clear support process makes support plans easier to sell. Clients who see a proper route, fast responses and a record of what was done are more willing to pay for it. Support becomes a service rather than a drain.
Measuring support time
Track how many requests come in each month, how long they take and which clients send the most. Many agencies are surprised by the result. A handful of clients may account for most of the support time, often without a plan that covers it. That information makes renewal and pricing conversations much easier, because both sides can see what the support actually involves.
Getting started
Write a short support guide for clients, set up one route in and start capturing requests properly. See how tickets and handover work on the features page, or try SpideyChat with your own documentation.