Service desk software for managed service providers

Many client desks, one small engineering team, and a device count that dwarfs your headcount. The three things that decide whether a helpdesk works for an MSP are isolation, the seat model and how fast an engineer can move between clients.

Isolation: what "multi-tenant" has to mean for you

Every helpdesk claims multi-tenancy. For an internal IT team it means departments. For you it means that Client A can never, under any circumstance, see a ticket, a contact, an attachment, a report row or an autocomplete suggestion belonging to Client B — and that if they ever did, your business would be over.

Here each client is a separate tenant with its own data, its own portal, its own branding and its own users. A client's help centre lives at a path of its own — yourdomain.in/clientname — rather than on a wildcard subdomain, which means no DNS record and no certificate to provision per client, and one less thing to get wrong at two in the morning when you onboard somebody urgently.

Your engineers sit above that boundary and can be given access to one client, several or all of them. A client's own staff can never cross it at all. Client help centres are also set to noindex by default, because that content belongs to your client and should not be turning up in a search for their company name unless they ask for it.

The seat model, and why per-technician matters to you

You are the clearest case for per-agent pricing. Your agent count is small, stable and known; your requester count is large, volatile and not yours. Any tool that charges per end user, per contact or per device makes your margin a function of your clients' headcount, which is the one number you do not control.

So: you pay for the engineers who answer tickets. Every contact at every client is free and unlimited. Onboarding a hundred-person client costs you nothing more than onboarding a ten-person one, and your cost per client falls as you grow rather than rising with them.

• Unlimited client tenants on every paid plan — the tenant is not the billable unit.
• Unlimited contacts and requesters inside each tenant.
• One invoice to you, in rupees with GST, never to your clients.
• No per-ticket, per-asset or per-device charge.

Moving between clients without losing your place

An MSP engineer's day is not one queue. It is a triage across eight of them, and the tool either respects that or you end up with eight browser tabs and a mistake waiting to happen. A cross-client work view shows an engineer everything assigned to them across every tenant they can see, with the client name on every row, and switching into a client is one action rather than a re-login.

The safeguard that matters just as much: every reply window shows the client and the contact prominently, because the single worst mistake an MSP engineer can make is pasting Client A's answer into Client B's ticket. We would rather the interface be slightly repetitive than let that be easy.

Reporting your clients will actually accept

The monthly report is not a nice-to-have for you, it is the artefact your contract is judged on. Each tenant's reporting is scoped to that tenant, so you can hand a client a report — or give them a login that only ever shows their own numbers — without assembling it by hand.

Volume, first-response and resolution against the targets in their contract, breaches with the reason, busiest categories, and the trend across months. Exportable as CSV so it can go into whatever your account manager puts in front of the client.

If your quarterly reviews need the asset and licence estate per client as well, that lives in SupportCentral Enterprise (https://supportcentral.in) rather than in this edition.

Practical things worth knowing before you migrate

• Import per client from CSV — contacts, open tickets and knowledge base articles — so you can move one client at a time rather than all at once on a weekend.
• Each tenant can have its own outbound address and reply-to, so mail keeps coming from the address the client already recognises.
• The API and webhooks are tenant-scoped, which is what makes it possible to wire the desk to your RMM or monitoring without a script that can accidentally cross clients.
• Your own internal desk can be one more tenant, and most MSPs find that useful.

Questions