Support tiers
Support tiers are the usual way of splitting questions by what it takes to resolve them. Tier 1 handles the known and documented, tier 2 what requires technical knowledge of the product, and tier 3 what ends up with whoever wrote the code.
What is support tiers?
Support tiers are the usual way of splitting questions by what it takes to resolve them. Tier 1 handles the known and documented, tier 2 what requires technical knowledge of the product, and tier 3 what ends up with whoever wrote the code.
Also: tier 1, 2 and 3 · L1, L2 and L3 · support levels
Why it matters
What changes in a SaaS
The split exists for an economic reason: each tier time costs very differently. A ticket resolved at tier 1 costs a few euros; the same ticket escalated to engineering rarely lands under forty, and it interrupts deep work on top. Which is why the metric that matters is not how many tickets get handled, but how many move up a tier without needing to.
Support tiers in detail
Tier 1
Questions whose answer is written down: how to do something, where an option lives, what a message means. It is the tier that absorbs the most volume and the one that automates best, because the answer does not depend on who is asking.
Tier 2
Cases that need the specific account opened: why this customer cannot do something everybody else can, why they were charged that amount, why that integration stopped syncing. This is where the time goes in a SaaS, and where a bot that only reads documentation is no help.
Tier 3
Product bugs, edge cases and things nobody had seen. It should be a very small minority. If it grows, the problem is not support: either the product is failing or the documentation does not cover what people actually do with it.
Escalation on teams without tiers
On a team of three, all three tiers are the same faces, but the distinction is still useful as a way to measure: classifying questions by tier for a month tells you exactly where the cost sits, and it usually surprises.
How Intake handles it
Questions about support tiers
What do L1, L2 and L3 mean in support?
They are the three tiers: L1 handles the documented, L2 what requires opening the account and product knowledge, and L3 what reaches engineering. The numbering says nothing about difficulty for the customer, only about who is needed to resolve it.
Do you need tiers on a small team?
As an org structure, no. As a way to classify and measure, very much: knowing what share of your volume sits at each tier is what tells you whether to automate, document better, or fix something in the product.
Which tier can be automated?
Tier 1 almost entirely, given well-written documentation and something that can search it. A good part of tier 2 as well, but only with a system that can check how the account actually stands. Tier 3 cannot, and should not be attempted.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Escalation
Escalation is handing a conversation to somebody with more knowledge or more permissions to resolve it. It can go from one support tier to another, from an automated agent to a person, or from support to engineering — and in every case whoever receives it has not seen the case until that moment.
Support agent
A support agent is the person who handles incoming customer questions: reads them, finds the context needed to answer, resolves them or escalates them to whoever should take over. It is a reactive job by definition, and the work is measured in response time, resolution and satisfaction.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
SLA — Service level agreement
A service level agreement is the written commitment to respond within set deadlines. It fixes maximum times — usually first response and resolution — defines the hours in which they count, and normally states what happens when they are missed.
Resolution time
Resolution time is how long passes between a question arriving and it being resolved and closed. Unlike first response time, it measures the whole process, including waits on the customer and escalations to other teams.
CSM — Customer Success Manager
A Customer Success Manager (CSM) is the person responsible for making sure a customer gets the outcome they signed up for. They work proactively across a book of accounts, own adoption, retention and expansion, and their success is measured in renewals, not in closed tickets.
