Agree the client-facing name and communication rules separately from the staffing model and price.
The scope taxonomy
Five dimensions define any help desk offer. An offer that leaves one undefined is not yet comparable with anything.
Tiers - by task list, not by label
L1, L2 and L3 mean different things at every provider. Replace labels with a written catalogue: password resets, account unlocks, MFA issues, how-to questions, known-error fixes, standard software troubleshooting, hardware triage, escalated diagnostics, change work. The handoff line is wherever your catalogue says it is - and the provider's price assumes their catalogue, not yours, until you align them.
Tasks - what may actually be touched
Identity and Microsoft 365 administration, endpoint software, printers and peripherals, dispatch scheduling, documentation writing. Each is separately in or out. Never infer a task from a tier name.
Channels - staffed versus monitored
Phone, email, portal, chat, SMS: for each, is it staffed (a human answers live) or monitored (queued for later)? Over which hours? A "phone support included" line can mean either. Check channel staffing separately for after-hours coverage - nights and weekends have their own page below.
Queue ownership - whose system is the truth
Tickets in your PSA with provider access, or in the provider's system with exports? This decides client visibility, your audit ability, quality sampling and what exit looks like. The Benchmark365 and Sherweb comparison shows different working-queue arrangements. Specify who owns updates, approvals and the ticket history, including exports when the service ends.
Client experience - who the client sees
Does the client ever interact with provider staff, and if so under whose identity? This is the dimension that splits the outsourced decision from the white-label one: outsourcing moves the work; white-label additionally manages what the client perceives.
What you keep regardless of model
- Client ownership - your MSAs, your promises, your renewals.
- Escalation acceptance - a named path from the provider back into your team.
- Security governance - access reviews, credential policy, audit log review; the desk touches client identities daily, so caller-verification procedure and least-privilege access are yours to demand and verify.
- Quality judgment - sampling tickets against your rubric, not the provider's summary.
What providers publish
Only 6 of the 32 providers publish a minimum and 10 publish a notice period in the company-level disclosure study. A published charging basis may still omit the rate or billing period. Request the scope, minimum, notice and complete fee schedule for the service you choose.
Choose your route
Three desk scenarios and their retained owners
| Need | Service boundary | MSP responsibility to retain |
|---|---|---|
| Overflow during a peak | Agreed intake threshold and transferred queue | Demand definition, fallback capacity and unresolved escalation |
| Branded after-hours contact | Identity checks, permitted fixes and morning acceptance | Client commitment, business approval and escalation owner |
| Replacement of a daily desk queue | Tier/application scope, staffing and quality control | Service accountability, review and major change authority |
A recruitment or staffing purchase adds people to a buyer-managed process. A managed desk purchase requires a defined service outcome. An AI tool can assist a workflow but does not itself accept the human service obligations above. Use the desk versus staff augmentation guide to allocate supervision before comparing prices. White Label Service Desk and 31West describe desks that answer under your brand; ScienceSoft separates L1 and L1-L2 options.