Every page ranking for help desk outsourcing was written by somebody selling it, and none of them shows you what the decision does to your own profit and loss statement (P&L). In a managed service provider (MSP), the firm that runs information technology (IT) for other businesses, labour is the number that decides whether you make money, and level one (L1) support is where most of that labour sits. Two arguments dominate, and neither is arithmetic: offshore labour saves you a fortune, or support is the product so you never touch it.
I run growth for MSPs, and I have sat inside the accrual P&L of a managed IT client of mine watching gross margin move tens of points on the labour line alone. So this covers what an in-house desk costs fully loaded, real 2026 price bands, the white label question, artificial intelligence (AI) as the third option, when not to do it, and how to run the evaluation. I also trace the three statistics this industry repeats without a source.
What help desk outsourcing actually is, and the four ways MSPs buy it
Help desk outsourcing means paying a third party to staff and run some or all of your first-line user support: password resets, Microsoft 365 problems, printer and connectivity tickets, onboarding and offboarding. Scope runs from after-hours cover only, through overflow, to full L1, to L1 plus level two (L2).
Sort the market this way before you take a single sales call, because a per-agent quote from a ticket queue and a day rate from a staffing firm are not comparable numbers.
| Model | Who manages the technicians | What you are actually buying |
|---|---|---|
| White label / business process outsourcing (BPO) queue | The vendor | Resolved tickets from a shared queue, answered under your brand |
| Direct staffing | You | Named staff you manage, with the vendor handling recruitment, human resources (HR) compliance, payroll, benefits and office space for a flat monthly fee per head and no markup on salary |
| Placement | You | A vetted technician working inside your own tools and processes on a flat day rate |
| Managed specialist seats | Shared | One bundled monthly figure covering pay, training, supervision and quality assurance (QA) |
Model choice, not country, drives most of what happens to quality later.
What an in-house level one desk really costs you
MSPs typically understate their own labour cost by 20 to 40 percent. A technician nominally on $90,000 often carries a fully burdened cost of $130,000 to $145,000 once burden, holiday, meetings and non-billable time are counted. So most help desk outsourcing decisions start from a baseline that is wrong by a third before the first quote lands.
Build the number properly. These are United States (US) figures.
| Component | 2026 figure | Source |
|---|---|---|
| Base salary, generic help desk technician | $45,106 to $55,406, midpoint about $50,000 | Kore1 consensus of Salary.com, Indeed, ZipRecruiter and PayScale |
| Base salary, MSP-specific technician | $66,116 average, $53,058 to $83,050 range | Kore1 |
| Fully loaded multiplier | 1.25x to 1.7x base; benefits alone are about 29.8 percent of total compensation | Scale Army |
| Fully loaded cost, generic L1 | roughly $62,500 to $85,000 a year | the rows above |
That band comes off the generic $50,000 base. Run the same multiplier on the MSP-specific base and it moves to roughly $83,000 to $112,000, the number to use if your technicians can actually fix things.
Now convert it into something comparable to a vendor invoice. Tickets per technician per month benchmark anywhere from 30 to 198 across organisations, so a raw ticket comparison is meaningless without normalising for complexity.
One real outsourced help desk runs 37 staff on 3,000 tickets a month across 180 MSP clients, roughly 81 tickets per technician per month. Do the division at that throughput and an $85,000 loaded technician costs about $87 a ticket. An offshore seat does not.
I read one of these every month, and the P&L is blunter than any benchmark. A managed IT client of mine runs fully loaded support labour at roughly $40 per user per month. Gross margin on the recurring line falls about 30 points once that labour loads in, and the accrual P&L sits close to breakeven. The headline margin on a managed services contract and the margin after service delivery labour are two different businesses, and only one of them pays you.
Set that against the industry. The average MSP does about $142,000 of revenue per employee and top performers clear $200,000. Healthy managed services gross margin runs 50 to 60 percent on recurring revenue with the top quartile above 60, and best-in-class providers have held 19 percent or better adjusted earnings before interest, taxes, depreciation and amortisation (EBITDA) for six straight years. If your recurring margin lands well under that band after labour, you have found your problem, and it is not the tool stack.
Help desk outsourcing pricing: per user, per ticket, per agent
Almost nobody in this category publishes a rate card. The gate is itself information: pricing is set per deal, against what the vendor thinks your alternative costs. Here is everything that is public.
| Pricing model | What is public | Where it comes from |
|---|---|---|
| Per hour | Roughly $8 to $60 an hour depending on agent location; skills and compliance are secondary drivers | Giva |
| Per user per month, offshore | Typically $20 to $50 per user per month, so a 100-employee client runs $2,000 to $5,000 a month | KDCI |
| Per device per month, onshore | $20 per desktop, $125 per server, $30 per network device for 24x7x365 US-based network operations centre (NOC) and help desk monitoring | Corserva, published rates |
| Per technician day rate | Flat day rate per technician, no recruitment fee, 30-day trial | Support Adventure |
| Bundled managed seat | Pay, training, supervision, QA and monitoring in one figure; at three or more seats the management fee folds into the rate | LTVplus, no public figure |
| Flexible per-unit | Per user, per server, per workstation and full-time equivalent (FTE) options, plus a public true-cost calculator | GMS Live Expert, no published rates |
| Quote only | Priced through the sales process | ConnectWise Expert Services |
One trap before you model anything. The $1.50 to $3.50 per managed endpoint per month figure quoted for ConnectWise is remote monitoring and management (RMM) software, not staffed labour. Mistake it for a labour rate and your model is wrong by an order of magnitude.
Which model is safe depends on how you sell. You bill per user per month, so per-user outsourced pricing matches your revenue shape and per-ticket does not. Per ticket pays the vendor more precisely when your environments are least standardised, which is when volume is highest and margin already worst. Per agent or FTE pricing bills the vendor's capacity rather than your chaos, and it is what I would sign first, because it caps the downside while you learn your real ticket rate against what you charge.
A loaded US technician at $62,500 to $85,000 against a $20 to $50 offshore seat is where the arbitrage looks obvious. The next two sections are where it stops.
Onshore, nearshore, offshore: what changes besides the price
Ask the end client what an offshore help desk feels like. In one complaint circulating in competitor marketing, an MSP moved support overseas and the account contact the client knew by name became an anonymous queue reading scripts. Help desk, billing and equipment ordering degraded at once.
The same pitch adds hours on hold, then somebody in a different timezone with no context about your business, which it calls the top reason businesses switch providers. That is the margin decision seen from the other side of the ticket.
Philippines cost of living runs roughly 50 percent below Western nations, the real basis for the price gap. It is not a durable saving on its own.
James Vickery ran his own Australian MSP almost entirely offshore for five years, then spun the model out as a private-label service. His version: you save two-thirds on salary, then add a layer of management, a layer of training, and a layer of re-recruitment when the person leaves. "It's not cheaper." That is a man describing the model he sells.
The structural problem is turnover. Traditional BPO and call centre outsourcing runs 80 to 120 percent annual staff churn, according to a former MSP owner who ran it before switching approaches. That model was built for huge-scale, low-skill, repetitive telecom-style tickets. MSP work is niche, high-skill and different from one stack to the next.
Churn eats the knowledge of the client environment that makes L1 fast. Geography is not the mechanism. The motive is not what you would guess either: Peter Billing of TGT Global says nine out of ten MSPs who approach him come for growth and talent access rather than cost savings, and the biggest barrier is owner control-aversion.
White label help desk for MSPs: your PSA decides the shortlist
Apply one filter before you look at a single price. "We use GMS, they're pretty good," writes one owner on r/msp. "The caveat with all these services is they only play well with certain PSAs, so you might find one you like, only to find out they don't fit in your stack." That one question, professional services automation (PSA) fit, removes half the market and saves you a month of discovery calls.
A white label help desk means the outsourced technicians answer as your brand, under your service level agreement (SLA), inside your ticketing system. The integration that matters is bidirectional. GMS Live Expert publishes two-way ticket sync with Autotask, ConnectWise, Kaseya, Zendesk and Salesforce. A one-way feed leaves you reconciling two systems of record and destroys the time and billing data you price the next contract from, so treat PSA fit as a hard gate rather than a tooling preference.
ConnectWise Expert Services is the native option if you already live in that stack, and it is quote-only. Benchmark 365 is the private-label route, built by a former MSP owner who ran the model on his own book first.
Then check the billing unit against your own. You sell per user per month on a contract that assumes a ticket rate, so a white label desk billed per ticket hands your volume risk straight back to your P&L. Take 81 tickets per technician per month as the anchor. When one badly standardised client doubles their ticket rate, an internal desk absorbs it inside a fixed salary, and a per-ticket vendor invoices you for it in a month when your revenue from that client has not moved.
The uncomfortable part is disclosure. Some MSPs never tell their clients, betting on lock-in and switching friction to hold the account. Bad trade. Clients work it out, usually mid-outage, and the churn follows the discovery rather than the decision.
Three numbers this industry repeats that do not survive a check
Three statistics do most of the work in help desk outsourcing sales pitches.
"55 percent of help desk processes are outsourced." Traces to one source: the Computer Economics (Avasant Research) 2023 IT Outsourcing Statistics Report. What it found: among organisations that already outsource their service desk, an average 55 percent of operations goes to third parties, the largest share of any IT function. It is not a claim that 55 percent of IT organisations outsource, and every citation I checked leads back to it.
"Up to 70 percent cheaper offshore." Near verbatim across vendor sites, pinned to Philippines cost of living. The rebuttal comes from inside the industry. The chief executive officer (CEO) of an offshore staffing firm, a 16-year former MSP owner who ran the BPO model, calls the save-70-percent brochures "nonsense" and says the durable saving comes from management quality, not wage arbitrage.
"Outsourcing cuts operational costs 30 to 40 percent." Cited to unspecified studies with no primary source. Same for the 20 percent churn spike after full outsourcing, directionally credible but sourced to unnamed forum discussion, and for the $50,000 to $200,000 of annual recurring revenue (ARR) lost per churned midmarket client, real money but a vendor's own number.
None of this means outsourcing does not save money. It means the only numbers worth modelling are yours.
The third option: AI at the front of the queue
Build versus outsource assumes a human answers the ticket. The cheapest L1 ticket is the one nobody works. Every vendor selling ticket deflection quotes a number, and the numbers sit three times apart.
Start with what is public and priced. Thread's AI Essentials tier for MSPs lists at $19 per licence per month and covers auto-prioritisation, auto-categorisation, auto-recap, auto-time-entry and sentiment analysis. It is one of the only published price points in the category, which tells you how early this market is. Pia handles the downstream half, zero-touch automation inside the PSA for onboarding, password resets and permissions.
Here is the spread.
- Vendor case study, Thread with Pia: 50 to 70 percent lower cost per routine ticket, up to 80 percent faster resolution, three to five times more tier one and two technician capacity.
- Vendor claim, Neels.ai: more than 40 percent of L1 tickets resolved end to end within four weeks.
- Independent review estimate: mature AI triage deployments deflect 25 to 35 percent of L1 volume without human intervention, with Thread resolving 10 to 25 percent fully autonomously.
I have commercial relationships with some vendors named in this piece, so read the vendor figures as vendor figures and the independent range as your planning number. The honest 2026 framing is partial deflection, not L1 replacement, which is roughly where agentic service desk tooling sits today.
Andreessen Horowitz (a16z) led a Series A into Treeline, an AI-enabled IT services provider, citing that more than 80 percent of US businesses outsource IT to MSPs. Capital is funding the AI-native version of the thing you are about to buy.
The counterweight comes from the staffing side: AI is starting to bite at L1 specifically, while level two and level three (L3) placements have not yet seen displacement. So make it a contract term. Do not sign three years of full L1 outsourcing at today's volumes without a volume-reduction clause.
When not to outsource your help desk
"No, just no," wrote one owner in that same r/msp thread, to 27 upvotes. "We pride ourselves on this as support is the single most valuable thing I sell. If I wasn't good at support, I wouldn't have a business." That is not sentimentality. For a lot of MSPs the queue is the entire differentiator, because the tools are the same ones everyone else resells.
Craig Willard, who wrote Profit by Design, names the mechanism better than the margin argument. "Helpdesk is not just ticket resolution. It's proximity." Churn signals, upsell signals and aging-hardware signals all surface on the front line first. Outsource the front line and you have outsourced your early warning system, and you are building what he calls a disconnected MSP.
His diagnostic is blunter still: "Most MSPs don't have a labor crisis. They have a discipline crisis." Before you price a single vendor, answer four questions. Is the environment standardised, are refresh cycles enforced, are users running with admin credentials, and are patches applied proactively?
If the architecture is chaotic, outsourcing does not fix the chaos, it distributes it. And if your pricing cannot fund a properly paid, benefited technician at a healthy margin, outsourcing is patching a pricing problem.
The solo shop version splits three ways. Intentional solo: do not outsource long term, because proximity is your value proposition. Growth-track solo: outsource as a temporary bridge while you restructure pricing to afford the hire. Avoidance-driven solo: outsourcing will not cure a fear of hiring.
Keep one eye on the exit. Differentiated service quality and low churn are what an acquirer underwrites. That anecdotal 20 percent churn spike after full outsourcing, if it turns up in your book, is a valuation event rather than a service ticket.
How to run the evaluation: pilot, metrics and contract terms
Step 1. Scope it tactically, and borrow the wet read. Willard takes the model from hospital radiology: the overnight reading stabilises the patient, the specialist writes the final report in the morning. Outsourced capacity covers after-hours and overflow only, and the outsourced technician stabilises and documents rather than closing the ticket. Your team reviews it next business day, confirms the client is happy and owns the resolution. Outsource the wet read, not the final report.
Step 2. Ramp small on purpose. Technology Elite tells new clients to start with two staff, technical roles first, not ten or twenty. Use the small team to get the management cadence and communication right. Their average client team is five staff, range two to 29, and standing up your own offshore entity does not pay below roughly 25 people.
Step 3. Measure what degrades, not what flatters. Premium outsourced tiers target 75 to 80 percent first contact resolution (FCR), basic tiers only 60 to 70 percent, so tier and management drive FCR, not outsourcing itself. Baseline your own FCR, customer satisfaction (CSAT) and escalation rate before the pilot or you have nothing to compare against. Two guardrails: best-in-class resolution averages around 30 minutes, and no technician carries more than 20 active tickets, because past that they stop updating them.
Step 4. Write the contract for experience, not uptime. SLA terms measure response and resolution times, and a vendor can hit all of them while your clients have a worse year. Add experience level agreement (XLA) terms: CSAT floors, an escalation-rate ceiling, named-technician continuity, documentation standards, and the volume-reduction clause. And write the exit: notice period, ticket-history export, no lock-in past 12 months.
Labour decides your margin. IT help desk outsourcing is a margin decision, made with your own cost-to-serve per user in front of you rather than a vendor's savings calculator. Whatever you sign, keep the final resolution and the client relationship in-house.
Questions MSP owners ask me about help desk outsourcing
Roughly $8 to $60 an hour depending on agent location. Offshore runs $20 to $50 per user per month, so a 100-seat client lands around $2,000 to $5,000 a month. One of the few US providers publishing rates charges $20 per desktop a month for monitoring.
Usually on the wage line, not always on the total. A US level one technician costs roughly $62,500 to $85,000 fully loaded, and MSPs typically understate their labour cost by 20 to 40 percent. Offshore savings shrink once you add management, training and re-recruitment, which is why practitioners who have run both call the 70 percent claim marketing.
A third-party desk whose technicians answer as your brand, under your SLA, in your ticketing system. The constraint is integration: most vendors support only certain PSA platforms, so confirm bidirectional ticket sync before you compare prices. It is the filter that removes half the market.
Per user, if you sell per user. It matches your revenue shape and leaves volume risk with the vendor. Per ticket pays the vendor more precisely when your environments are unstandardised and margin is already worst. Per agent pricing bills capacity rather than chaos.
It can, and the mechanism is staff churn, not geography. Traditional BPO desks run 80 to 120 percent annual turnover, destroying knowledge of a client's environment. Keep it tactical, baseline your resolution and satisfaction scores first, and never let an outsourced ticket close without internal review.
Not yet, but it dents it. Independent estimates put mature AI triage at 25 to 35 percent of level one volume deflected without a human, against vendor claims of 40 to 70 percent. Treat it as partial deflection, and do not sign a long contract at today's volumes.
Salary and loaded-cost figures come from 2026 salary aggregators and MSP benchmarks; the two estimates disagree, so you have both. Pricing is whatever vendors publish, and gated pricing is flagged, not guessed. The client P&L is anonymised and rounded. I hold commercial relationships with some vendors named here and have ranked none.