2026-08-31
Running multiple product desks from one account
Agencies and portfolio founders usually need more than one help widget. Here's how DeskQ handles that without making you open five tabs.
Most agencies I know end up juggling five different help widgets because each client wants their own tone, their own knowledge base, and their own escalation rules. The usual fix is to open five different accounts. That gets expensive fast.
DeskQ takes a different route. You create one login and then spin up separate desks inside it. Each desk gets its own embed script, its own training data, and its own keyword rules. The customer on Client A's site never sees Client B's content. From your side, though, everything lands in the same ticket inbox so you don't have to keep switching browser windows.
The thing that usually trips people up is team access. In the Growth and Pro plans you can invite teammates with different permissions. One person might only answer tickets for the fintech client while another person owns the e-commerce brands. You set the seats once and the desks inherit the permissions. No extra logins, no shared passwords floating around in Slack.
I had a founder tell me last month that their old setup meant every new client meant a new Intercom workspace. They were paying for five seats across five workspaces just to keep the data separate. With DeskQ they pay for the seats they actually need and the desks stay isolated on the front end. The cost difference adds up when you're running eight or nine sites.
There's also the form studio piece. Each desk can have its own branded contact form with custom fields. One client might need a "project budget" dropdown while another just wants a simple waitlist. You build both inside the same account and drop the right embed code on each site. The submissions still route back to the shared ticket view with the right tags attached.
The hand-off flow stays the same across desks. When the AI can't answer, it shows the visitor a short intake form. That form plus the chat transcript becomes an email ticket that lands in your team's inbox. You decide which operator sees which desk's tickets through the permission settings rather than through separate inboxes.
If you're the kind of agency that white-labels everything, the widget can still match each client's brand colors and fonts. DeskQ pulls the host site's styles so you don't have to maintain separate CSS files for every project. The AI model choice is also per-desk, so a client who wants a more formal tone can run a different model than the playful SaaS brand two desks over.
One thing worth noting: the free plan only gives you a single desk. If you're testing with one client that's fine, but the moment you sign a second contract you'll probably want to move to Growth. The pricing page spells out the seat limits and desk limits for each tier.
The workflow ends up feeling closer to how most small teams actually operate. One login, one ticket list, multiple front-end experiences. You still have to write the escalation rules and train each desk on its own product docs, but at least you're not managing five separate billing cycles.