Skip to content

Support tiers

Adrià Castany 3 min

What are 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 called

tier 1, 2 and 3, L1, L2 and L3, support levels

Topic
Roles and teams
On this page
  1. Support tiers and service levels
  2. Why it matters
  3. The tiers at a glance
  4. Tier 1
  5. Tier 2
  6. Tier 3
  7. Escalation on teams without tiers
  8. How Intake handles it
  9. Frequently asked questions

Support tiers and service levels

Support tiers (L1, L2 and L3) split queries by difficulty.

Service levels are the deadlines committed to in an SLA. They get confused because sales proposals call both a “level”, and a customer can have a high service level without that saying anything about which support tier handles them.

Why it matters

The split exists for an economic reason.

Each tier’s time costs very differently. A ticket resolved at tier 1 costs a few minutes of whoever answers. The same ticket escalated to engineering costs the time of a more expensive profile, and it interrupts deep work on top. That is why the number to watch is how many move up a tier without needing to.

The tiers at a glance

Each tier is defined by what it takes to resolve, not by the seniority of whoever answers.

  • Tier 0. Self-service, what the customer resolves alone with the help center.
  • Tier 1. The known and documented. Resolved by the front line or an AI agent.
  • Tier 2. What requires looking at the account or knowing the product in depth. Resolved by technical support.
  • Tier 3. Bugs and edge cases. Resolved by engineering or product.

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 lies in the product, which is failing, or in the documentation, which does not cover what people 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

Frequently asked questions

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 the state of the account. Tier 3 cannot, and should not be attempted.

What is tier 0 support?

It is self-service. Everything the customer resolves without talking to anyone, with the help center, their account dashboard or an assistant. It is called tier 0 because it comes before the first tier staffed by people.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment