Key takeaways
- Agencies run two kinds of support. One is your own clients asking for changes and fixes; the other is customer support on websites you run for them. Set them up separately, or both will suffer.
- Move client requests out of personal inboxes and DMs into a shared inbox with owners, statuses and a published response time. Clients care more about knowing when you'll reply than about instant replies.
- Put chat and an AI agent on client websites only when someone owns the answers. Train the AI on each client's own content and agree in writing who handles handoffs.
- Turn support into a line item. A monthly support retainer with a clear scope pays for the tools and stops "quick questions" from eating project margins.
- Tidio is our top pick for agencies that run chat on client websites, because each client gets its own project with live chat, an AI agent and an inbox, all reachable from one login.
It's late August. Half the team is back from holiday, three clients want "a few small changes" before their autumn campaigns, a fourth has messaged the founder on WhatsApp about a broken checkout, and someone's personal inbox holds a request from two weeks ago that nobody saw. Meanwhile the chat widget you installed on a client's site in spring has been forwarding visitor questions to an address no one checks.
Agencies rarely fail at the work itself. They struggle with everything around it: requests scattered across channels, no clear owner, and support that quietly eats the margin on fixed-price projects. With Q4 campaigns about to start, now is a good time to fix it. This guide shows how.
Two kinds of support, two setups
Most agencies mix up two very different jobs:
- Supporting your clients. Change requests, bug reports, "can you add this banner?", access problems, invoices. Few messages, high value, and they need tracking.
- Supporting your clients' customers. The chat on the websites you built and run. Many messages, mostly simple questions, often outside office hours.
Run them through the same channel and the high-value client request drowns in visitor chats, or the visitor chats sit unanswered. Keep them apart: a shared inbox for clients, and chat with an AI agent for each client's website.
What clients and their customers ask
| Request | Best channel | Automate? |
|---|---|---|
| "Can you change this text or image?" | Shared inbox or client portal | No, but use a request form so details arrive complete |
| "The site is down" / checkout broken | Phone or a priority email address | No. Alert the on-call person immediately |
| Access, passwords, "where do I log in?" | Shared inbox | Partly, with a saved reply and help article |
| Invoices and retainer hours | Shared inbox | Partly, with a monthly summary sent automatically |
| Visitor questions on a client's site (prices, hours, delivery) | Website chat | Yes, with an AI agent trained on that client's content |
| Leads and quote requests on a client's site | Website chat | Yes. Collect details and pass them to the client |
| Complaints from a client's customers | Website chat, then the client | No. Hand over to the client's team with context |
Step 1: Give clients one front door
Pick one route for client requests, usually a support address like support@youragency.com or a simple portal, and say it in every proposal and kick-off. Then:
- Make every request a conversation with an owner and a status. "Who's on this?" should never need asking.
- Use a short request form for changes: page URL, what to change, deadline, screenshots. It saves a round of questions every time.
- Move requests out of Slack and WhatsApp politely. Reply once with "Logged it, you'll hear from us by tomorrow", then forward it to the inbox.
Step 2: Publish response times and keep them
Clients don't need instant replies from an agency. They need to know when they'll hear back, and see it happen.
| Priority | Example | First response | Resolution target |
|---|---|---|---|
| Urgent | Site down, checkout broken | Within 1 hour, any day | Same day |
| High | Campaign landing page wrong | Same business day | 1–2 business days |
| Normal | Content changes, small tweaks | Next business day | Within the retainer schedule |
| Low | Ideas, "nice to have" | Within 2 business days | Planned into the next sprint |
Put these in your contract. Our guide to customer service SLAs covers how to choose targets you can actually keep.
Step 3: Run chat on client sites as a product
Chat on a client's website only works if someone owns the answers. Before you install it:
- Agree who answers. The client's staff during their hours, the AI agent outside them, and your team for setup and improvements.
- Train the AI on that client's content only: their website, FAQ, policies and prices. Don't reuse another client's answers.
- Set handoff rules for complaints, refunds and anything involving money, and send those conversations to the client with full context.
- Review monthly. Read unanswered questions, update the content, and send the client a short report: conversations handled, leads captured, questions the AI couldn't answer.
That monthly review is what the client pays for. It's also how you show the value of the retainer.
Never be the only person who can answer a client's customers. Your job is to set up the system and keep it accurate, not to become their night shift.
Step 4: Price support so it doesn't eat your margin
Unpriced support is the silent killer of agency margins. Three models that work:
- Support retainer: a fixed monthly fee covering a set number of hours or requests, with priorities and response times.
- Managed chat: a monthly fee per client site covering the chat tool, AI training, monthly reviews and reports.
- Pay as you go: an hourly rate for out-of-scope requests, logged against the conversation so invoicing is easy.
Whichever you choose, track time against conversations, and look every quarter at which clients cost more support than they pay for.
Data, contracts and access
- Data processing: when you run chat for a client, they are usually the controller of their customers' data and you act for them. Sign a data processing agreement and check the chat tool's terms. This isn't legal advice.
- Account ownership: where possible, put the chat account and billing in the client's name, with your agency as a team member. Offboarding becomes painless.
- Access hygiene: use individual logins, remove people when they leave, and never share passwords in chat.
Common mistakes
- Founder as help desk. Clients learn to message the boss directly, and nothing gets tracked.
- Chat with no owner. A widget nobody answers is worse than no widget.
- One inbox for everything. Visitor chats bury urgent client requests.
- Free "quick fixes". They add up to days a month and train clients to expect more.
The best support tools for agencies
We compared how well each tool handles several clients from one login, how quickly a new client site can be set up, how pricing scales across clients, and what clients themselves see.
Tidio lets an agency create a separate project for each client site, each with its own widget, settings, AI agent and inbox, and switch between them from one login. Lyro learns from that client's website and FAQ, so you can offer round-the-clock answers as part of a support retainer, and Flows cover lead capture or booking questions without custom development. It's the quickest way on this list to give a small-business client a working chat and AI setup in an afternoon.
Why we like it
- One login with a separate project per client site
- AI agent trained on each client's own content
- Departments and Flows to route chats to the right person
- Free plan to pilot with a client before they pay
Watch out for
- Each project has its own plan, so costs add up across many clients
- You're logged into one project at a time and only see that project's notifications
Front turns shared email addresses into a team inbox with assignment, comments and rules, and adds chat, SMS and social on higher plans. Its Slack integration and client portal suit agencies whose clients expect a reply from "the team", not one person.
Why we like it
- Excellent shared email with internal comments
- Slack integration and client portal
Watch out for
- Per-seat pricing with no free plan
- Not designed for AI chat on client websites
Help Scout feels like email but adds ownership, saved replies and a Docs site. The free plan covers up to five users and one inbox, which is enough for many small agencies to start, and paid plans add more inboxes for separate clients or service lines.
Why we like it
- Free plan for small teams
- Familiar email feel with a Docs site for client FAQs
Watch out for
- Extra inboxes cost more as you add clients
- Chat and social are secondary
Crisp charges a flat price per workspace instead of per seat, and its multichannel inbox covers chat, email and social. Agencies with three or more paid workspaces on the higher plans can ask for a multi-workspace rebate.
Why we like it
- Flat workspace pricing with seats included
- Wide channel coverage
Watch out for
- One workspace per client still means one bill per client
- Rebates aren't automatic and only apply to higher plans
A simple setup before Q4
With September here soon and the busiest season for many clients ahead:
- This week: create a shared support address, connect it to a shared inbox, and tell every client it's the way to reach you.
- Next week: write your response-time table into a one-page support policy and send it to clients.
- In September: pick two clients who would benefit from chat, set up a Tidio project for each, train the AI agent on their content and agree the handoff rules.
- In October: send the first monthly chat report and turn it into a retainer offer for the rest of your clients.
If your clients are mostly small businesses, see our guide to choosing an AI chatbot for a website. For more inbox options, browse the help desk category.
Frequently asked questions
How should an agency handle client support requests?
Give clients one way to reach you, usually a shared support email or portal, and turn every request into a conversation with an owner and a status. Publish a response time per priority and stick to it. Keep Slack for quick coordination, not for requests that need tracking.
Should agencies offer customer support as a service?
If you already build and run websites, yes. Many small businesses want chat and AI on their site but don't want to set it up or maintain it. A monthly retainer that covers setup, AI training, monthly reviews and a defined number of handled conversations is easy to explain and price.
Who is responsible for customer data when an agency runs chat for a client?
Usually the client is the data controller and the agency acts on its behalf, so you need a data processing agreement and the chat tool's own terms in place. Put the client's account in the client's name where possible. This isn't legal advice; check the rules where you and your clients operate.
Can one chat tool cover several client websites?
Yes. Tools like Tidio let you create a project per client site and switch between them from one login, and Crisp uses one workspace per site. Check how each tool bills multiple sites before you commit, because that is where costs grow.