Tier 1, 2 and 3 support: how to structure levels and escalation rules
Tickets bouncing between teams are a sign of poorly defined levels. See the role of each tier, how to escalate with clear criteria and how to bring resolution closer to the user.
A ticket goes through the first tier, moves up to the second, comes back because information was missing and goes up again. Meanwhile, the user waits and the SLA clock keeps running. This “ping-pong” between teams almost always has the same cause: support tiers without clear boundaries and escalation without criteria. Structuring tiers 1, 2 and 3 is less about hierarchy and more about putting each issue, quickly, in the right hands.
What each tier does
- Tier 0 — self-service: a portal, knowledge base, chatbot or IVR resolves simple questions and requests without human intervention.
- Tier 1 — first contact: logs, classifies and prioritizes; performs initial diagnosis with scripts and the knowledge base; fulfils standard requests and known incidents; and keeps the user informed.
- Tier 2 — specialists: in-depth technical analysis, remote access, configuration of specific systems and applications, tests and fixes that require higher permissions.
- Tier 3 — engineering and vendors: infrastructure, development or manufacturer teams that handle product defects, structural changes and root cause, together with problem management.
Escalate with criteria: functional and hierarchical
Functional escalation transfers the ticket to whoever has the technical skills or access needed. Hierarchical escalation brings in management when impact, the risk of breaching the SLA or the need for a decision require it — for example, a critical incident affecting many users.
- Exit criteria: maximum time spent at each tier, types of issue that start directly at tier 2, and permissions tier 1 does not have.
- Complete handover: symptoms, impact, what has already been tested and evidence. Tickets escalated without this information tend to bounce back.
- Ticket owner: the service desk follows the ticket until closure and remains the user’s single point of contact.
- Internal agreements (OLAs): targets for each tier that are compatible with the SLA promised to the customer.
Shift-left: resolve earlier, safely
The service desk’s own data shows where to act. Tickets resolved at tier 2 with repetitive steps are candidates to become scripts and controlled permissions at tier 1; frequent questions at tier 1 can move to self-service. Knowledge management — methodologies such as KCS help — is what makes this transfer sustainable. There are also collaborative models, such as Intelligent Swarming, also from the Consortium for Service Innovation, which bring experts together around the case instead of passing it from queue to queue.
Track the tier 1 resolution rate, escalation rate, time in each queue, reopen rate and tickets returned due to improper escalation. Together, these metrics show whether the structure is helping or getting in the way.
In the 2018 edition of ISO/IEC 20000-1, incident management (8.6.1) and service request management (8.6.2) became separate clauses. In the 2011 edition, these processes appeared combined.
References and legislation
- ISO/IEC 20000-1:2018 · service management requirements, including incidents and requests — access
- KCS v6 Practices Guide · knowledge management applied to support — access
- Consortium for Service Innovation · history of KCS and Intelligent Swarming — access
We recommend reviewing escalation rules with the client based on data: what bounces back, what takes too long and what could have been solved earlier. A good structure is one that shortens the distance between the problem and the person who knows how to solve it.
— Multicanal Content Team · Multicanal Contact CenterHow Multicanal helps: Multicanal runs 24/7 help desk and service desk operations with support tiers, escalation rules and operational reports defined with each client.
Explore our service deskKeep reading
Service desk with ITIL 4 and ISO/IEC 20000-1: how to design SLAs that are actually met
A good SLA is one users can feel. Learn how to combine ITIL 4 practices with ISO/IEC 20000-1 requirements to build realistic, measured and improving agreements.
Knowledge base with KCS: how to cut repeat tickets at the service desk
When the same question is solved from scratch every day, the problem is knowledge. See how KCS turns each interaction into a useful, reusable article.
Secure cloud: ISO/IEC 27017 and 27018 in practice for cloud service customers
Moving systems to the cloud does not transfer responsibility for the data. See what ISO/IEC 27017 and 27018 recommend and what cloud customers need to demand…


