# How do I manage support for multiple clients in one place?

You manage support for multiple clients in one place by giving each client its own workspace under one login: separate inbox, knowledge base, branding and email identity, with your team switching between them. Pricing is flat per workspace, so a client growing does not change your cost, and white-label on paid plans keeps your name on the front.

Last updated: October 2026

## Why this happens

An agency that built the sites ends up supporting them. Questions arrive in five inboxes, two Slack connections and a shared spreadsheet, and the person who knows client A's refund policy is on holiday when client A's customer asks.

Shared tools leak. One inbox for all clients means one wrong reply-to, one article quoted to the wrong customer, one AI that has read every client's policies. Separation is not a luxury; it is what keeps the retainers.

The shape that works is one workspace per client, fully separate, and one login for your team across them.

## Steps

1. **Create a workspace per client.** Each has its own inbox, knowledge base, board, branding and email identity. Nothing is shared between them, including the AI's knowledge.
2. **Install on whatever the client is built on.** WordPress, Shopify, Wix, Framer and Craft have native plugins or apps; everything else takes one script tag. Minutes per site, not a project.
3. **Publish each client's answers in their own workspace.** Their policies, their FAQ, their tone. The AI in that workspace answers from those articles and only those, so client A's answer can never surface for client B.
4. **Give your team one login.** Members join the workspaces they work on and switch between them. Tickets have owners, so handover during holidays is reading the queue, not asking around.
5. **White-label the paid workspaces.** The client's logo and colours, their own help-center domain, replies from their email domain, no DeskCrew badge. The client sees their support desk, run by you.

## Facts, with sources

| Fact | Value | Source |
| --- | --- | --- |
| DeskCrew for agencies | A separate workspace per client under one login, flat pricing per workspace, white-label on paid plans | [DeskCrew for agencies](https://deskcrew.io/for/agencies), October 2026 |
| Companies that never answered a customer service email, in a test of 1,000 | 62% | [SuperOffice customer service benchmark](https://www.superoffice.com/blog/customer-service-benchmark/), updated March 2023 |
| Service leaders who say at least a fifth of their tickets are repetitive but easy | 80% | [DigitalGenius and Canam Research survey, via DestinationCRM](https://www.destinationcrm.com/Articles/CRM-Insights/CRM-Blog/Repetitive-Tickets-Are-Prevalent-in-Customer-Service-Survey-Finds-127256.aspx), September 2018 |
| DeskCrew Pro | $29 a month flat for the workspace: email-to-ticket, 150 AI answers, white-label | [DeskCrew pricing](https://deskcrew.io/pricing), October 2026 |

## What to expect

**White-label is per paid workspace.** A client on the free plan gets a working desk with a DeskCrew badge. Removing the badge, the custom help-center domain and sending from the client's domain are Pro, at $29 a month for that workspace.

**Separation means no shared knowledge base.** Two clients with the same question each need the article in their own workspace. That is the price of never quoting one client to another, and it is the right price.

**Reseller terms are a conversation.** Volume pricing, dedicated onboarding and reseller white-label for client brands sit on the Agency plan, which is custom rather than self-serve.

## FAQ

### Can I manage multiple client helpdesks from one account?

Yes. Each client gets its own workspace: separate inbox, knowledge base, board, branding and email identity. Your team members join the workspaces they work on and switch between them from one login. A ticket in one workspace is invisible from another, so a mistaken reply to the wrong client's customer is not possible.

### How does pricing work across clients?

Flat per workspace, not per seat and not per ticket, so a support retainer can be priced predictably. A client's traffic growing does not change what you pay. Free workspaces are fine for small clients or trials; Pro at $29 a month per workspace adds email-to-ticket, more AI answers and white-label.

### Can we white-label it for clients?

On paid plans, yes: the client's logo and colours, their own help-center domain, replies sent from their email domain, and no DeskCrew badge on the widget. The client sees a support desk under their own brand, run by you. Reseller white-label across many client brands, with volume pricing, is the Agency plan.

### Can the AI answer for each client separately?

Yes, and only separately. Each workspace has its own knowledge base and its own AI, which answers from that workspace's published articles and nothing else. It has never read another client's policies, so it cannot quote them. Drafts for tickets wait in that workspace's approval queue until your team sends them.

### How do we hand a client over when they leave or grow?

The workspace is theirs in all but login: their articles, their history, their branding. Add their own staff as members, remove yours, and the desk carries on without a migration. If they grow into their own support team, nothing has to be rebuilt, which is a better exit than most tools offer.

## Related

- [DeskCrew for agencies](https://deskcrew.io/for/agencies)
- [WordPress helpdesk plugin](https://deskcrew.io/integrations/wordpress)
- [Pricing](https://deskcrew.io/pricing)
- [Run support without sitting in a tab](https://deskcrew.io/how-to/run-support-without-sitting-in-a-tab)

---
Source: https://deskcrew.io/how-to/manage-multiple-client-helpdesks