How agencies run branded support for every client, without per seat fees

Agencies have a support problem that classic help desks were not designed for: you are not one brand with one inbox, you are ten brands with ten inboxes, and none of those brands is the help desk vendor's.

Here is the playbook we see working, and how Vicket implements it.

The agency support problem

Every client project ships, and then questions start. The usual answers all hurt:

• Shared inbox per client: ten inboxes, zero overview, things fall through.
• One help desk account per client: ten subscriptions, ten configurations, ten logins for your team.
• One shared help desk: one brand bleed disaster. Client A sees a tool branded for your agency, or worse, for the vendor.

What you actually want is a matrix: one operational view for your team, one isolated and fully branded surface per client.

One dashboard, many brands

The structural answer is multi tenancy with sites as the unit of branding:

• Each client is a site with its own domain allowlist, its own API key, its own email routing and its own templates.
• Your agents work in one dashboard, with team scoping so the people on the Client A account only see Client A tickets.
• Each client's users open tickets on the client's own site, in pages that match the client's design, with no third brand in sight.

In Vicket this is the default shape: sites isolate clients, teams scope visibility, and every customer facing surface is white label on every plan.

Pricing that does not punish growth

Per agent pricing is built for companies with one support team. For agencies it compounds badly: every new hire multiplies across every client account you operate.

Flat plans with limits on sites and volume map much better to how agencies actually grow. Adding your eleventh client should be a checkbox, not a procurement discussion. Compare how that maps to your roster on the pricing page.

Setting up a client portal in practice

The repeatable per client recipe takes minutes once your account exists:

1. Create a site for the client, allow their domain.
2. Run npx @vicket/create-support in the client's codebase, paste the site key.
3. Design the ticket templates for that client: a retainer request form is not a bug report.
4. Publish the help center articles that deflect their recurring questions.
5. Wire a workflow: route urgent tickets to the right team, notify the account manager.

Repeat per client. Your team still lives in one dashboard; each client lives in their own branded world.

The compounding payoff

The first client portal saves you an inbox. The tenth saves you an operations role. Because every client runs on the same engine, improvements compound: a better template, a smarter workflow, a clearer article structure rolls out to the next client for free.

If this maps to your roster, start with a free account and set up your first client site today. For the deeper integration story, read how to add support to a SaaS in minutes, the mechanics are identical per client.