OLYMP LogoOLYMP
Contact
Guide

Tier 1 vs tier 2 support, explained

Support tiers split work by how much knowledge and access a request needs. Tier 1 answers and resolves the common requests, tier 2 investigates problems that need deeper product or system knowledge, and tier 3 changes the product itself. Getting the line between them right decides your cost per ticket and how fast customers get answers.

Plan your tiers with usCompare the tiers
IT support outsourcingIT help desk outsourcingIT customer supportSLA guide

What is the difference between tier 1 and tier 2 support?

Tier 1 support is the first point of contact: agents resolve common, documented requests such as password resets, billing and how-to questions, and log everything else completely. Tier 2 support investigates problems that need deeper product or system knowledge, logs and test environments, and passes true defects to tier 3 engineering.

Tier 0
Self-service: help centre, chatbots, status page
Tier 1
First contact, documented fixes
Tier 2
Investigation, logs, integrations
Tier 3
Engineering, usually in-house

Designing the escalation path

Escalation is where outsourced support most often slows down. Five decisions keep tickets moving.

  1. Write the scope of each tier

    List the request types each tier resolves, with examples. Anything not on a list goes to a named owner instead of bouncing between teams.

  2. Define what a complete escalation contains

    A checklist per ticket type: account, steps already taken, screenshots or logs, business impact. Tier 2 should be able to start work without asking the customer again.

  3. Set response targets per tier and priority

    Agree how quickly each tier responds to urgent, high and normal tickets, measured in your own helpdesk. Faster targets need more staff, so set them together with the staffing plan.

  4. Close the loop

    When tier 2 or 3 solves something new, the fix becomes a knowledge-base article or macro so tier 1 can solve it next time. Track how many escalations turn into documentation.

  5. Review the line every month

    Look at escalation rate, reopen rate and the ten most common escalated issues. If tier 1 escalates the same issue repeatedly, train it or document it; if tier 2 is buried in simple tickets, move the line.

The support tiers

Most companies use three or four levels. The names vary; what matters is that each level has a written scope and a clear rule for passing work on.

  • Tier 0: self-service

    Help centre articles, in-app guides, chatbots and status pages that let customers solve problems without contacting anyone. Good tier 0 content lowers tier 1 volume, so it should be written from the questions tier 1 answers most often.

  • Tier 1: first contact

    Agents who answer every incoming contact, identify the customer, solve common requests with documented steps and log the rest properly. Typical work: password resets, account and billing questions, how-to questions, known issues and order changes.

  • Tier 2: investigation

    Specialists who take problems tier 1 cannot solve with documented steps. They reproduce issues, read logs, check configurations and integrations, and either fix the problem or pass a complete case to tier 3.

  • Tier 3: engineering

    Developers and engineers who own the product or system. They fix defects, change code or infrastructure and decide on workarounds. Tier 3 usually stays in-house, because it needs access to source code and roadmap decisions.

Tier 1 and tier 2 side by side

Example tickets show where the line usually falls in a software company. Move the line for your own product, then write it down.

  • Goal

    Tier 1
    Resolve common requests on first contact
    Tier 2
    Diagnose and fix non-standard problems
    Tier 3
    Fix the product or system

  • Example tickets

    Tier 1
    Password reset, invoice copy, how to export a report, known outage
    Tier 2
    Integration fails for one account, data not syncing, error that cannot be reproduced
    Tier 3
    Defect in the code, performance problem, security fix

  • Skills

    Tier 1
    Clear communication, product basics, following documented steps
    Tier 2
    Deep product knowledge, logs, APIs, databases, structured troubleshooting
    Tier 3
    Software engineering on the product itself

  • Typical access

    Tier 1
    Helpdesk, customer account view, knowledge base
    Tier 2
    Admin tools, logs, test environments, read access to configurations
    Tier 3
    Source code, deployment, production infrastructure

  • Output when escalating

    Tier 1
    Complete ticket: customer, steps taken, screenshots, impact
    Tier 2
    Reproduction steps, logs, suspected cause, workaround if any
    Tier 3
    Fix, release note and an update to the knowledge base

  • Commonly outsourced?

    Tier 1
    Yes
    Tier 2
    Often, with clear access rules
    Tier 3
    Rarely

In internal IT help desks the same levels apply to employees: tier 1 handles access and device requests, tier 2 handles servers, networks and business applications, and tier 3 is the system owner or vendor.

Outsourcing technical support by tier

Outsourcing works best when each tier has a written scope, the right access and a clean handover to the next level. These points come up in almost every setup.

Which access does an outsourced tier 2 team need?

Usually admin or support views of customer accounts, read access to logs and configurations, a test or staging environment and the ticket history. Give named accounts with the least access that lets them do the job, log what they do, and review the list when people join or leave.

How do outsourced agents learn a technical product?

  • A sandbox or test account where they can break things safely
  • Recorded walkthroughs of the most common ticket types
  • Shadowing your own team on live tickets before taking them alone
  • Release notes and a short briefing before every product change
  • A knowledge base that tier 2 and tier 3 keep updating

How should tickets move to your engineers?

Agree one route, for example a linked issue in your engineering tracker, with a template for reproduction steps, logs, affected accounts and business impact. Engineers should be able to reply in the ticket, not in private messages, so the customer-facing team can keep the customer informed.

Continue reading

Which metrics show the tiers are working?

  • First-contact resolution at tier 1
  • Escalation rate from tier 1 to tier 2, and from tier 2 to tier 3
  • Time to resolution per tier and priority
  • Reopen rate after a ticket is closed
  • Number of escalations that became new knowledge-base articles

When should tier 2 stay in-house?

Keep tier 2 in-house while the product changes faster than documentation can follow, when the work requires production write access you cannot restrict, or when contracts with your own customers forbid third-party access. Revisit the decision once the product and runbooks are stable.

Last reviewed: . Written and reviewed by the OLYMP BPO team in Prishtina, Kosovo. About the company

Support tiers: common questions

What is the difference between tier 1 and tier 2 support?

Tier 1 is the first point of contact and resolves common, documented requests such as password resets, billing questions and how-to questions. Tier 2 handles problems that need investigation, such as integration failures or errors that require logs, test environments or deeper product knowledge.

What is tier 3 support?

Tier 3 is the engineering level: the developers or system owners who fix defects, change code or infrastructure and decide on workarounds. It usually stays in-house or with the software vendor.

What is tier 0 support?

Tier 0 is self-service: help-centre articles, in-app guidance, chatbots and status pages that let customers solve problems without contacting a person.

Which support tiers can be outsourced?

Tier 1 is the most commonly outsourced level, and tier 2 is often outsourced too when access rules, test environments and escalation paths are clear. Tier 3 is rarely outsourced because it needs access to source code and product decisions.

What is a good escalation rate from tier 1 to tier 2?

There is no universal number, because it depends on product complexity and on how much tier 1 is allowed to do. Measure your own rate for a few months, then watch the trend and the most common escalated issues rather than chasing a benchmark.

Does OLYMP provide tier 1 and tier 2 support?

Yes. OLYMP teams work at tier 1 and tier 2 inside your own helpdesk and tools, with escalation rules agreed with you. Tier 3 engineering stays with your developers or vendor.

Need tier 1 and tier 2 cover?

Tell us your product, ticket types and tools. We will propose where to draw the line between tiers and how escalation to your engineers should work.

Talk to usIT support outsourcing