How agencies resell AI support to clients
Evoriqa Team · June 16, 2026 · 5 min read

"Can you add AI to our support?" is the request landing in every agency inbox right now. Saying yes used to mean standing up infrastructure you didn't want to own and couldn't bill cleanly. White-label reselling removes that problem: you deliver the whole platform under your own brand and run it as a service. This post is about running that service: scoping the work, onboarding a client, owning the relationship, and reviewing it each month. If you want the technical build steps instead (reseller plan, branding, custom domain, email), the reseller setup guide covers those end to end.
What you're actually selling
It isn't a login. A client can buy a chatbot builder anywhere. What an agency sells is the work around it: choosing what the agent should know, wiring it to the channels the client already uses, checking the answers before customers see them, and keeping all of that current as the business changes. The platform is the tool. The service is the scoping, the review, and the monthly upkeep. That is also what makes it recurring instead of a one-off build. The white-label solution for agencies is built around that split: your clients get a branded product, you keep the relationship and the judgment.
Scope the knowledge before you price
Before you quote anything, find out where the client's answers live. That inventory decides how much work onboarding is, which decides how you price it. Walk the sources with them:
- The public site: product and service pages, hours, locations, policies
- Documents that never made it onto the site: PDFs, price lists, policy files, internal FAQs
- The questions their team answers by hand every day, which rarely exist in writing anywhere
- Structured lookups the agent could make on request, like order status or a booking calendar
Evoriqa answers only from the sources you give it, traces every answer back to them, and flags the gaps where it had nothing to answer from. A client with a tidy help center is a light onboarding. A client whose knowledge lives in three people's heads is a heavier one. You should price that difference in rather than absorb it.
What onboarding week one looks like
A first week has a predictable shape:
- 1Kick off. Confirm the channels the client wants covered and the handful of questions that matter most to get right.
- 2Gather and load. Crawl the site, upload the documents, and paste in the answers that only existed verbally. Opening on an industry template gives you a tuned persona and a starter FAQ instead of a blank workspace.
- 3Review before launch. Test the agent against real questions in the workspace and fix the answers that read thin or wrong. Nothing goes public until it sounds the way the client would want it to.
- 4Connect and embed. Turn on the channels (website widget, WhatsApp, email, and the rest) and wire up any actions the client needs, like booking an appointment or looking up an order. If you build client sites on GoHighLevel, the embed is one paste into the site's body tracking code.
- 5Hand over or hold. Decide with the client whether their team gets logins to help run it or whether you keep it fully managed and report on it.
Week one ends with a working agent on the client's site, answering from their material, on the channels their customers already use.
Who owns the client relationship
You do, and the product is built so it stays that way. Each client gets an isolated workspace under your organization, branded as yours, on a domain you control. Their login carries your name, not ours; their emails come from your sender; their billing view says the service is managed by their provider, because you are the provider. They never see Evoriqa, and they never see what the platform costs you.
That means escalations, change requests, and the monthly conversation all route to you. You decide whether a client's team can log in to edit knowledge or whether every change passes through yours. Either way the client's relationship is with your agency, which is the whole reason the work is worth owning.
Pricing structure: retainer, per-seat, or usage
The platform bills you a flat reseller fee with a pooled credit allowance; how you charge each client is your call. Three structures are worth weighing:
| Structure | How you bill | Fits |
|---|---|---|
| Retainer add-on | An uplift on the care plan you already invoice | Clients you bill monthly already |
| Per-seat or flat monthly | A fixed fee for the workspace, upkeep, and a monthly report | Clients where support is the whole engagement |
| Usage-based | A base fee plus a step tied to conversation volume | Clients with spiky or seasonal demand |
A retainer line for steady work, with usage-based terms held back for clients whose volume is genuinely unpredictable, is the combination that survives contact with a real client list. Whichever you pick, you are pricing your service — the scoping, review, and upkeep — not reselling credits at cost. To check a structure against a real client mix, the agency ROI calculator does the arithmetic for you.
What to review each month
The monthly review is where a resold agent turns into a renewed contract. Each cycle, look at:
- Resolution and deflection: how many conversations the agent handled without a human
- Knowledge gaps: the questions it couldn't answer, which become your list of content to add
- Credit consumption against the cap: whether the client is trending toward their ceiling
- Anything that changed in the business: new hours, a new product, a policy the agent doesn't know yet
- CSAT and the handful of conversations worth reading in full
Turn that into a short report the client actually reads. It shows the work, surfaces the next thing to improve, and gives you a natural moment to suggest a bigger plan when a client has outgrown theirs.
Keeping one noisy client from eating the month
All your clients draw AI usage from one pooled allowance, so one account's bad week can't be allowed to spend everyone's month. The control is a per-client monthly spend cap, set on every workspace. A runaway integration, a viral post, or a botched campaign hits that cap instead of the shared pool.
When a client reaches their cap, their assistant pauses for new visitors with a friendly message while human handoff keeps working, so nothing silently breaks. The client sees a neutral "contact your provider" note — never a word about pools or credits — and that's your cue to top them up and, usually, move them to a larger plan. The cap enforces the discipline for you, so a single noisy client becomes a conversation about upgrading rather than a surprise on your own bill.
Start with one client
You don't need a full roster to begin. Scope one client you already manage, onboard them in a week, and let the monthly review prove the service before you package it more widely. When you're ready to formalize it, the agency program lays out the console, credit pooling, and packaging in full. When you're ready, create your account, pick a reseller plan from the dashboard, and build that first branded workspace.