Operating across multiple games: a practical guide to workspace management
When you go from one game to three, your support infrastructure needs to grow differently than your headcount.
At one game, your support infrastructure is simple. One inbox, one queue, one set of agents, one SLA policy. You know everything about everything.
At three games, you have a choice: replicate the simple structure three times, or build something that connects them.
The replication trap
Most studios choose replication. Three separate tools, three separate teams, three separate knowledge bases. It works until it doesn't. The first time you need a senior agent to cover across titles during a crisis, you discover there is no mechanism to do it. The first time you want cross-title analytics, you realise the data is incompatible.
Replication also multiplies administrative overhead at a faster rate than revenue. Every policy change has to be replicated manually. Every new agent has to be provisioned in three places. Every SLA review becomes three SLA reviews.
What workspace architecture solves
A workspace model keeps titles operationally isolated (player data, escalation paths, agent assignments are separate) while sharing infrastructure (auth, billing, AI models, analytics). You get the separation you need without the overhead you don't.
The key decisions in workspace architecture are: what is shared and what is isolated.
Shared across workspaces: agent identities, role assignments, platform-level analytics, billing, AI training corpus (if you choose to connect them).
Isolated per workspace: ticket queues, SLA policies, knowledge base content, escalation workflows, player profiles.
The shared elements are what make cross-title operations possible. The isolated elements are what make per-title accountability possible.
Staffing across workspaces
A workspace model enables flexible staffing models that aren't possible with siloed tools. An agent can have different roles in different workspaces — senior in the title they know well, viewer in a new title they're being trained on. A team lead can have read access to all workspaces for capacity planning without write access to titles outside their responsibility.
This becomes critical at the 50–100 agent scale, where you have specialists who are efficient in their domain and generalists who cover across titles during peak hours.
A practical transition path
If you are currently running siloed tools, the transition to workspaces does not require a big bang migration. Start by creating workspaces for new titles only. Import historical data into the analytics layer without migrating live operations. Consolidate authentication first — everything else follows.
The goal is a state where adding a fourth title takes one afternoon, not one month.
Ready to try CustomerOps Cloud?
Start a free 14-day trial and see how it works with your actual tickets.
No credit card required · Cancel anytime · Full access from day one