What help desk outsourcing actually involves
Help desk outsourcing is the practice of hiring an external team to operate either an internal IT help desk (employee-facing: password resets, VPN issues, laptop provisioning, SaaS access, printer and Wi-Fi tickets) or a customer-facing tech support help desk (product help, account issues, integration debugging). The outsourced team logs in to the buyer's existing ticketing platform (Zendesk, Freshdesk, ServiceNow, Jira Service Management), follows the documented runbooks, and works against published SLAs for first response time (FRT), mean time to resolution (MTTR), first contact resolution (FCR), and CSAT. The buyer keeps the ticketing system, the asset inventory, the knowledge base, and the Tier 3 escalation path.
The mechanics in practice. The buyer provisions the outsourced agents as named users inside its own Zendesk, Freshdesk, ServiceNow, or Jira Service Management instance. The agents log in to the buyer's ticketing system, not a vendor wrapper. They pick up tickets from the same queues the in-house team uses, route by intent and tier, respond within the buyer's documented runbook, and escalate to a defined Tier 3 owner when the ticket exceeds scope. Runbooks, the internal knowledge base, an asset inventory map (for IT help desks), and an escalation playbook ride along on day one.
What outsourcing does not mean. It does not mean handing the employee or customer relationship to a black-box vendor that emails a weekly CSAT chart. The buyer keeps the ticketing platform, the asset data, the customer or employee list, the runbook, and the Tier 3 escalation. The outsourced team is an extension of headcount inside the buyer's own tooling. The buyer sees every ticket, every macro, every escalation, in real time. The difference vs in-house is the labor location and the hourly rate, not the operating control.
Internal IT help desk vs customer-facing help desk: the operating difference
A help desk is two operating models in one phrase. Most buyers asking about help desk outsourcing are picturing one of the two, but the vendor needs to be clear which one is in scope before the RFP goes out. The difference matters for agent profile, training corpus, ticketing platform, and SLA structure.
The internal IT help desk. Supports the company's own employees. Typical ticket mix: password resets and MFA issues, VPN and SSO problems, laptop and device provisioning, SaaS account access requests, printer and conference room AV tickets, employee onboarding and offboarding workflows, and basic endpoint troubleshooting. Usually runs inside ServiceNow or Jira Service Management against an asset inventory. The SLA emphasis is on FCR (first contact resolution) because every minute an employee is locked out is a minute of lost internal productivity. The agent profile leans toward an IT generalist with platform fluency and asset awareness. For how we staff this model, see our outsourced IT help desk.
The customer-facing tech support help desk. Supports the company's external paying customers. Typical ticket mix: install and onboarding issues, account and billing questions, integration debugging, product how-to, and bug reports that filter back to the engineering team. Usually runs inside Zendesk or Freshdesk against a product knowledge base. The SLA emphasis is on CSAT and time to resolution because every customer ticket is a renewal-risk signal and a brand-perception event. The agent profile leans toward product fluency, tone discipline, and integration-map awareness. For this model, see customer help desk outsourcing.
The two help desks share intake, triage, documented procedures and escalation, but the required skills and access differ. Scope the work before choosing an agent profile. The customer-facing pattern overlaps SaaS customer support outsourcing and the broader customer support outsourcing guide.
The Tiered Help Desk Operating Model: 6 layers
The Tiered Help Desk Operating Model is a six-part planning checklist. Use it to define the work, systems, reporting and coverage your program needs. CFG confirms the supported tasks and required training during scoping; these layers are not universal platform features. See the Transparent BPO Stack for reporting questions.
1. Tier 1 ticket intake and triage
Define the ticket categories, priority rules, required intake fields and first-response targets. If automation is included, test its routing against representative examples and give agents a way to correct errors.
2. Tier 2 escalation with platform knowledge
Identify the product and platform knowledge needed beyond the Tier 1 runbook. Confirm the assigned team can perform the agreed tasks inside your ticketing instance with role-scoped permissions and documented escalation.
3. Tier 3 senior specialist routing
Keep specialist decisions with the appropriately authorized owner, such as the buyer's engineering team or licensed professional. Define what the outsourced team may investigate and what must be handed off, with the information required for that handoff.
4. Real-time SLA dashboards
Agree definitions and targets for first response time, resolution time, first-contact resolution, customer satisfaction and backlog. Confirm the reporting source, update interval and owner of each alert. Reporting may use the buyer's ticketing system or another agreed view.
5. Knowledge base + AI agent orchestration
Provide approved runbooks and knowledge articles, name the owner of each, and define how updates reach the team. Evaluate routing or drafting automation separately, with human review and clear limits on its use.
6. After-hours and 24/7 coverage
Specify working hours, time zone, holidays, expected volume and shift handoffs. After-hours or round-the-clock coverage requires an agreed staffing plan; it is not included automatically with a single agent.
Cost math: in-house help desk vs outsourced help desk
Compare the cost of the same workload and coverage. Use your actual internal wage, employment costs, tooling and management costs alongside the vendor's written quote. The illustration below uses CFG's dedicated rate range and assumed hours; it is not an observed customer saving.
| Example | Hours assumption | At $13 to 19/hour |
|---|---|---|
| One agent, monthly | 160 billed hours | $2,080 to 3,040 |
| Five agents, monthly | 800 billed hours total | $10,400 to 15,200 |
| Five agents, annual | 9,600 billed hours total | $124,800 to 182,400 |
At an illustrative 160 billed hours per month, one dedicated agent at $13 to $19 per hour costs $2,080 to $3,040. Five agents at that same schedule cost $10,400 to $15,200 monthly. Actual billed hours, staffing, coverage and additional work follow the agreed plan. Ticket volume alone does not establish the seats required.
Platform integrations and tooling fluency
Confirm the exact platform and task set during evaluation. The following are examples of ticketing systems a buyer may use; listing a platform here does not assert a certified partnership, a prebuilt integration or that every CFG agent is already trained on it.
- Zendesk. Review the buyer's queues, macros, views, roles and escalation process.
- Freshdesk. Confirm the workflow, approved replies, routing rules and access permissions.
- ServiceNow. Scope the permitted IT service tasks and required approvals in the buyer's instance.
- Jira Service Management. Review request types, queues, runbooks and the handoff to the buyer's technical team.
Training scope should be explicit. Review representative tickets, workflows, access requirements and escalation boundaries before staffing the desk. Agree platform-specific training and readiness checks for the assigned agents. The SaaS customer support outsourcing guide provides a related scoping checklist.
When NOT to outsource help desk
Consider keeping the work in-house or using a smaller support arrangement in these cases.
Specialist work dominates the queue. If most tickets need source-code debugging, privileged system changes or restricted professional decisions, retain a suitably authorized specialist team. Define a narrower intake and triage role before outsourcing. See the services hub for scoping.
Low or irregular volume. Compare the management and training effort with the workload. A part-time arrangement, shared service or internal generalist may fit better than a dedicated seat. There is no universal ticket-count threshold: handling time, coverage, complexity and response targets matter.
Takeaway. A workable help desk scope needs approved runbooks, a defined escalation boundary, measurable response expectations and enough work to justify the staffing plan. Validate those assumptions before launch.
Vendor evaluation: 9 questions to ask a help desk BPO
Use the questions below to review the proposed team, workflow and reporting. Ask for relevant examples and record the agreed answers and limitations in the scope.
The Help Desk Outsourcing RFP Checklist (CC BY 4.0, copy freely)
- What training and readiness checks does our scope require? Agree a realistic ramp plan for the assigned team and platform.
- Can agents perform our exact tasks in our ticketing system? Review role-scoped access and escalation boundaries.
- How will tickets be classified and routed? Demonstrate the rules and how errors are corrected.
- What response and resolution targets will apply? Define business hours, priorities, measurement and escalation.
- How will customer satisfaction be measured? Confirm survey coverage and how feedback reaches the team.
- What coverage and handoffs are included? Specify hours, time zone, holidays and staffing.
- How are tickets reviewed for quality? Confirm sampling or automation, rubric, exceptions and human review. Keep ticket QA separate from call scoring.
- What security requirements can the program meet? Verify evidence for relevant access controls, retention and contractual requirements; do not infer certification.
- Can we see a relevant demonstration? Confirm what is available, its scope and any access conditions.
Pair this checklist with the CFG RFP Builder to document the help desk scope and evaluation criteria. Republish the nine-question checklist freely under CC BY 4.0 with attribution.
How CFG runs the help desk
CFG dedicated support desks cost $13 to $19 per hour depending on scope. Confirm the tasks, platform training, coverage, escalation and reporting before launch. AI-assisted call scoring on Scored and Open desks applies to calls on our line; it is not a promise to score every help desk ticket.
- Task scope. Agree intake, approved responses, permitted actions and specialist escalation.
- Platform access. Use named, role-scoped accounts and approved runbooks in the agreed system.
- Quality review. Define the ticket review process separately from AI-assisted call scoring. Call scoring on Scored and Open desks applies to calls on our line.
- Reporting. Agree the measures, source systems, update intervals and buyer access.
- Coverage. Select staffing for the required hours, workload and holidays.
- Pilot. Start with one agent at the normal desk rate, with the scope and readiness requirements agreed before launch.
Use the operating checklist to compare the proposed service with your requirements. Agree which tasks agents can complete, when they must escalate, and how performance will be reviewed.
Frequently Asked Questions
What does help desk outsourcing actually involve?
Help desk outsourcing is the practice of hiring an external team to operate either an internal IT help desk (employee-facing: password resets, VPN, laptop provisioning, SaaS access) or a customer-facing tech support help desk (product help, account issues, integration debugging) inside the buyer's existing ticketing platform (Zendesk, Freshdesk, ServiceNow, Jira Service Management). The outsourced team follows documented runbooks and works against published SLAs for MTTR, FCR, FRT, and CSAT. The buyer keeps the ticketing system, the asset inventory, the knowledge base, and the Tier 3 escalation path.
What is the difference between internal IT help desk and customer-facing help desk?
An internal IT help desk supports employees with approved access, device and software tasks. A customer-facing help desk supports product users with account, billing and product questions. They may share intake and escalation processes, but need different training, permissions and specialist support.
What is the Tiered Help Desk Operating Model?
The six planning areas are intake and triage, deeper support tasks, specialist escalation, performance reporting, knowledge maintenance and coverage. The required capabilities and service targets should be agreed for the specific program.
When should a company NOT outsource help desk?
Keep specialist or restricted decisions with appropriately authorized staff. Also compare the management effort with the workload before buying a dedicated seat. Low-volume programs may suit a smaller service; there is no universal ticket-count threshold.
How much does outsourced help desk cost vs in-house?
Use your own internal costs for the comparison. CFG dedicated desks cost $13 to $19 per hour depending on scope. At an assumed 160 billed hours monthly, that is $2,080 to $3,040 per agent, or $10,400 to $15,200 for five. These are illustrative calculations, not a guaranteed saving or minimum commitment.
What questions should a buyer ask a help desk BPO?
Ask about agent readiness, your exact platform, routing rules, response and resolution targets, satisfaction measurement, coverage, ticket QA, security requirements and a relevant demonstration. Define ticket QA separately from call scoring. Use the CFG RFP Builder to document the service requirements.
Run the 9-question help desk check on CFG
A help desk scoped to your tickets, systems and coverage.
Define the ticket types, required skills, coverage and reporting before you choose a desk. CFG dedicated agents cost $13 to $19 per hour. A pilot can start with one agent at the normal desk rate. Target launch is seven business days after kickoff, subject to approved scope, training materials, system access and staffing readiness. Explore our services hub.
Already scoped it? Get my 24-hour quote.