Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.
Conrad Lunderstedt
A buyer guide to IT help desk outsourcing: what an outside desk takes over, how per-ticket, per-user and per-agent pricing compare, SLA and ownership terms, security checks, questions for providers, and how MSPs use partners for after-hours and overflow.
Updated: October 2026
Your users need a password reset at 7am, a laptop fixed before a 9am pitch and an answer when the VPN drops on a Sunday. An outside team can take that front line, cover hours your own staff can't, and give your technicians their project time back. This guide to IT help desk outsourcing covers what to hand off, how providers price it, what belongs in the contract, and how MSPs use the same model for their own queues.
Support work splits into tiers by how much skill and access a fix needs. Tier 1 is the first contact: password resets, account unlocks, MFA re-enrollment, mailbox and printer issues, and "how do I" questions. Tier 2 is deeper troubleshooting that needs admin rights or remote access, like a failed application install or a sync that won't finish. Tier 3 is engineering: servers, network changes, vendor escalations and anything that changes how the environment is built.
An outsourced help desk usually takes tier 1 in full and tier 2 by agreement. Tier 3 stays with whoever owns the infrastructure, which is your internal team or your MSP. The cleaner that line is on day one, the fewer tickets bounce between teams.
Coverage is the second dial. Providers sell business hours, extended hours, after-hours only, or 24x7 outsourced IT support. After-hours is the easiest piece to hand off, because nothing in your daytime setup has to change.
Channels are the third. Phone, email, chat and a self-service portal can each be outsourced on their own. Choosing to outsource email support first is a common way to start: email tickets don't need an instant answer, so a provider in another time zone can work them overnight and your team starts the morning with a shorter queue.
Location is the fourth. Onshore teams cost more and share your users' time zone and public holidays. Offshore teams cost less and cover your night with their day, which is why follow-the-sun 24/7 desks are usually spread across regions. Nearshore sits between the two. Ask where each tier sits, because a provider can run tier 1 in one country and escalations in another, and make sure data residency rules in your industry allow it.
Help desk and service desk get used interchangeably in quotes. A help desk fixes things that broke. A service desk also handles requests and changes, like new starters, software installs and access approvals, usually following ITIL processes. Our help desk explainer covers the difference in detail.
So when you compare service desk outsourcing companies, check what "service desk" means in each quote. Some include request fulfillment and change approvals. Others mean a bigger ticket queue with the same tier 1 scope. If you plan to outsource IT service desk work, list the request types you expect the provider to complete end to end, and who approves each one.
Four pricing models cover nearly every quote. The figures below are published prices or published benchmarks, checked in October 2026.
| Model | How it bills | Published figure | Fits when | Watch for |
|---|---|---|---|---|
| Per ticket | Each ticket or contact handled | Sherweb lists per-ticket plans without public rates; MetricNet puts an in-house analyst-assisted contact at $20.61 (2023) | Low or uneven volume | Reopened tickets billed twice, a loose definition of "ticket" |
| Per user | Flat monthly fee per supported user | $35 to $60 per user a month for help-desk-only plans (typical quotes, October 2026) | Steady headcount | A few heavy users driving most of the volume |
| Per dedicated agent | Fixed monthly fee per engineer | 31West publishes $1,999 to $2,499 per tier 1 engineer a month | High volume, and you want named people who learn your setup | One engineer covers one shift, not 24 hours |
| Per hour or block | Hourly rate or a prepaid bucket of hours | $75 to $150 an hour for general break-fix work | Very small teams with few tickets | A block that runs out during an incident |
The per-ticket benchmark is the most useful yardstick in the table. MetricNet's 2023 benchmark summary puts the average cost of an analyst-assisted service desk contact at $20.61, with a median of $16.50. A desktop support ticket, where a technician works on the device itself, averaged $114.96. That gap is the business case for solving more at tier 1, whoever staffs it.
Per-user figures come from a different place. Our outsourced IT support guide puts help-desk-only plans at $35 to $60 per user a month, against $130 to $200 for fully managed IT. Those are typical quotes by scope, not a rate card.
For market context, Kaseya's 2023 Global MSP Benchmark found the most common per-user band for managed plans was $50 to $100 a month, chosen by 22% of MSPs. A help-desk-only quote near the top of that band buys less than a managed plan at the same price, so line up scope before you compare totals.
Quotes in different models only compare once you run them through your own numbers. You need two: supported users and tickets per month, both from your ticketing system.
Per-ticket pricing beats per-user pricing when your tickets per user per month sit below the per-user price divided by the per-ticket price. Take two hypothetical quotes: $45 per user a month, or $20 per ticket. The break-even is 2.25 tickets per user a month. A 60-person company logging 90 tickets a month runs at 1.5 per user, so per ticket wins at $1,800 against $2,700. Double the volume to 180 tickets and the answer flips: $3,600 per ticket against the same $2,700.
A dedicated agent enters the picture when volume is steady and high enough to keep one person busy for a shift. At that point you're paying for a named person who learns your environment, and the per-ticket math stops mattering. Ask each provider how many tickets a month one of its agents handles for clients like you, and test the answer against your own peak weeks.
Run the same exercise for after-hours. If nights bring two tickets a week, a per-ticket after-hours plan or an on-call rota is cheaper than a 24/7 contract. If nights bring a steady flow, you're in shift territory.
One help desk technician costs about $96,471 a year loaded. That starts from the BLS May 2025 median pay of $61,860 for computer user support specialists, adds 43% for benefits and payroll taxes from the BLS employer cost survey, then tools and recruiting.
That person is paid for about 2,080 hours a year. A queue that's open around the clock needs 8,760. Covering 24/7 in-house takes about 4.2 people before anyone takes a vacation, roughly $405,000 a year at the same loaded cost.
That's where outsourcing earns its fee: you pay for the hours you need instead of building shifts. The full in-house cost model, with break-even points by headcount, sits in the outsourced IT support guide linked above, so this post doesn't repeat it.
The contract decides whether an outsourced help desk works like part of your team or like a mailbox you can't see into. Six areas carry most of the weight.
Service levels by priority come first. A usable SLA sets response and resolution targets for each priority, P1 to P4, with each priority defined in your terms: "the CEO can't send email" is not the same ticket as "one user's printer is jammed." It says how targets are measured, how often you see the report, and what happens on a miss, usually service credits plus an exit right for repeated misses. Our SLA guide walks through the clauses.
The escalation path is next. Write down what the provider fixes alone, what it hands back, and to whom. Name the after-hours contact for P1s and the time limit before a ticket has to move up. A provider that escalates on time costs you less than one that spends a night on a tier 3 problem it can't fix.
Then the ticketing system. Some providers work inside your tool and others bring their own. Either can work, but the ticket history is yours. Get a full export of tickets, notes and attachments in a standard format, on request and at exit.
The knowledge base works the same way. Every article the provider writes about your environment during the contract should belong to you, stored in your system or exported monthly. Otherwise the documentation leaves when the provider does.
Data access needs its own clause. Provider technicians should sign in with named accounts and MFA, never a shared admin login. Access should match what each tier needs, be logged, and be removed the day a technician leaves your account. If you handle health or payment data, add the matching terms, such as a HIPAA business associate agreement.
Exit terms close the list: notice period, transition help and data return, all agreed before day one. It's the cheapest clause to negotiate while everyone is still friendly.
A help desk can reset passwords and move MFA to a new phone, which makes it a target. CISA's Scattered Spider advisory, last revised in July 2025, describes attackers calling IT help desks while posing as employees to get passwords reset and MFA moved to devices they control. That risk exists whether the desk is yours or a provider's, and it's one of the first things to settle in an outsourcing deal.
Write the identity check into the contract. Before a password reset or an MFA change, the technician verifies the caller through something an attacker can't get from LinkedIn: a callback to the number on file, a code pushed to the existing device, or a manager's approval in the ticket. High-risk accounts like admins, finance and executives get a stricter path, and the provider follows it even when the caller is in a hurry.
Ask how the provider trains for this, too. A desk that measures its people only on speed will feel pressure to skip the check. A desk that logs every verification step in the ticket gives you an audit trail when something looks off.
The rest is access hygiene: named accounts, MFA for every technician, least privilege per tier, session logging on remote access, and same-day removal when someone leaves. None of it costs extra to ask for before signing.
Run every shortlisted provider through the same checklist, and ask for the answers in writing.
The answers to questions five, six and seven tell you how hard it will be to leave. For MSP contracts in general, our list of questions to ask an MSP goes deeper on pricing and lock-in terms.
Fully in-house fits when your systems are specialized, your users need someone at their desk, or your data rules limit third-party access. You get people who know the environment in depth. You also carry the shifts, the training and the turnover.
Fully outsourced fits small companies with standard SaaS stacks and no IT staff. You get coverage hours and a team that has seen your problem at other clients. In exchange, the quality depends on your documentation and your contract.
Hybrid is where a lot of growing companies land. An internal IT lead owns strategy, vendors, security decisions and executive support. The provider takes tier 1, after-hours and overflow. The internal lead keeps the knowledge base current and the provider works from it, which is the same split as co-managed IT, narrowed to the help desk.
Some things stay in-house under any model: security decisions, approvals for privileged access, vendor negotiations, and anything that needs someone to walk the building.
The move also runs the other way. Bonita Payton's walkthrough of bringing a service desk back in-house from an MSP doubles as a list of what to document before you hand one out:
MSPs face the same coverage math, with clients watching the SLA. A small MSP that wants to sell 24/7 support has two ways to staff it: a rota of its own technicians, or a partner that covers nights and overflow.
White-label help desk partners answer as your company, work in your PSA and follow your SLA. ConnectWise sells this inside its Integrated Expert Services, and independent providers sell it on its own. Three setups come up again and again:
The r/msp thread that ranks first on Google for this topic opens with owners who see support as their main product and keep it in-house. Further down, others describe hiring instead, testing a partner on one client, and checking which PSAs a partner supports:
The after-hours case is where the coverage math bites hardest. A five-person MSP with a 54-seat client asking for 24x7x365 support laid out exactly that choice on r/msp, and the replies weigh extra hires against an outside partner:
The provider questions above all apply, plus three for MSPs. Does the partner work inside your PSA? Will it sign your clients' security terms? Who owns the client relationship when a partner technician talks to your client? Margin matters too: if you bill clients per user and the partner bills you per ticket, one noisy client can eat the margin on the account. Our MSP pricing guide covers how to price support so the partner's cost fits inside it.
Richard Tubb's TubbTalk episode with Jason Kemsley of Uptime Solutions, a provider of outsourced help desk and NOC services to MSPs, covers when to outsource, when not to, and how to take the first step:
AI agents now take part of tier 1 as well. They triage incoming tickets, pull device details and run pre-approved fixes, so the technician who picks up a ticket starts with context instead of a blank form. That's added capacity: the same team, in-house or partner, handles more tickets and spends its time on the ones that need judgment. Our guide to AI ticket triage shows how that works in a queue.
OpenFrame, Flamingo's open, AI-native infrastructure layer for IT and security, runs its Fae and Mingo agents inline with tickets and devices, at $1 per device with a 14-day free trial (see pricing).
A new team can only fix what it can look up. The handoff is mostly a documentation project, and it pays off even if you never outsource.
Start with the knowledge base. Pull the last 90 days of tickets, rank the request types by volume, and write a step-by-step fix for each of the top ones before go-live. Keep it where the provider's technicians will look first, in one place, not split across a wiki, a shared drive and a PDF.
That last point is where handoffs slip. An MSP owner reviewing providers on r/msp in 2026 described escalations marked "cannot find documentation" even though client cheat sheets existed, because technicians checked one page and stopped there. The replies land on the same fix: SOPs, a clear ticket taxonomy and someone who owns QA before anything goes out the door.
Write runbooks for anything with risk. Account unlock rules, who can approve access, what counts as a P1 and who gets called at 2am all belong in writing, not in one technician's head.
Set up access per technician and test it before day one. A provider that spends its first week waiting for credentials is burning your onboarding window.
Run a shadow period. The provider watches your queue first, then works it while your team reviews, then takes it over. Agree the length in the contract, long enough to cover a month-end and a patch cycle.
Review weekly for the first month. Look at reopened tickets, escalations, SLA misses and user feedback. A reopened ticket usually points to a missing or wrong article, so fix the article, not just the ticket.
SLA reports tell you whether the provider answered on time. They don't tell you whether users got their problem solved. Track a short set of numbers monthly, and agree the definitions in the contract so both sides count the same way.
First contact resolution shows how often a ticket is closed on the first touch, with no escalation and no callback. It's the clearest view of whether tier 1 has the access and documentation it needs, which makes it a fair number to put in a contract.
Escalation rate shows how much work comes back to your team. A rate that climbs after go-live usually points to gaps in the knowledge base, so check the articles first.
Reopen rate catches tickets closed too early. Reopens are the cleanest signal of a tier 1 fix that didn't hold.
User satisfaction closes the loop. A one-question survey on closed tickets, read alongside the comments, shows problems the other numbers miss, like a technician who's polite but slow, or a script that frustrates power users.
Backlog age is the last one. A small queue of old tickets says more about service than a big queue of new ones.
Our IT metrics guide covers how to pull and benchmark these from your own queue, whoever staffs it.
Start with your own ticket data: volume by hour, by channel and by tier. It tells you whether you need after-hours cover, overflow help or a full tier 1 team, and which pricing model fits that volume. Then write the contract around ownership, so the tickets, the knowledge base and the credentials stay yours whoever answers the phone.
For the wider budget picture, read our breakdown of small business IT costs.
If you'd rather keep the queue in-house, our roundup of help desk software for small teams is the next stop.
Solution Architect
I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.
Still deciding?
Ask Mingo answers from our docs and customer stories.
Still deciding?
Ask Mingo answers from our docs and customer stories.