Tiered support is a way to organize your support team for tackling customer support issues efficiently, no matter what your product or service is.
Although it isn’t the only way to structure customer support, it’s the most commonly used, especially by tech companies. But any company with customers or issues that need to be handled by an expert team can benefit from tiered support.
In this post, we discuss what tiered support is and how it’s structured, and share tips for setting up support tiers at your company.
Key takeaways
- Tiered support sorts issues by complexity. Self-service and automation handle Tier 0, generalists handle most issues in Tier 1, and harder cases move up to specialists in Tier 2 and product experts in Tier 3.
- The model puts each issue in front of the right people. Routine requests stay out of the specialists’ queues, which helps cut costs, improve customer service metrics, and keep customers satisfied.
- Swarming is the main alternative. Instead of escalating a case from team to team, one owner keeps it and pulls in experts. It suits new, complex issues, while tiers suit high volumes of repeatable ones.
- Every tier works better from the same answers. With shared TextExpander Snippets, Tier 1 replies, escalation notes, and expert fixes stay consistent, and one update reaches every agent in every tier.
What is tiered support?
Tiered support is a way of organizing a support center by skill level.
In tiered support, issues are filtered by complexity. Simple, repetitive issues are resolved through automation (Tier 0) or a “first line of defense” team (Tier 1), while complex cases are escalated to more experienced team members (Tier 2 or Tier 3).
Tiered support helps companies better allocate their resources, which leads to reduced costs and improved customer satisfaction.
Support tiers
Most tiered support teams are divided as follows:
- Tier 0 encompasses all the self-help resources available to users, including services like password reset automation, knowledge base articles, and blog posts.
- Tier 1 is the first-line support team that handles basic customer issues (around 40-60%). Usually the largest support team, Tier 1 is made up of generalists with strong communication and customer service skills.
- Tier 2 is the back-line senior team that tackles issues Tier 1 can’t solve. A smaller group composed of experienced support technicians, Tier 2 handles around 30% of incoming issues. They escalate the ones they get stuck on to Tier 3, but not without first replicating them and testing different solutions.
- Tier 3 is staffed with senior analysts that have deep knowledge of a product or service—sometimes, the engineers or programmers who created the product or service themselves. They investigate, diagnose, and resolve issues using resources not available to other support agents.
The number of tiers and who the teams report to can vary per organization. All support tiers follow and support a common support center vision, mission, and goals.
Why offer tiered support?
Imagine if, instead of bots, account-based services like Netflix and TextExpander relied on support agents to manually reset users’ passwords. Handling all of these cases would be incredibly tedious and time-consuming.
Just like password resetting is best done through automation, some cases are best handled by a generalist support team as opposed to a team of highly-specialized experts—and vice-versa.
That’s where tiered support comes in. Tiered support ensures resources are properly allocated—to maximize efficiency, cut costs, improve customer service metrics, and empower users and support teams.
Tips for setting up tiered support
- Automate. Automate support as much as possible to increase efficiency and availability.
- Invest in self-service resources. Make information easily accessible in Tier 0 to enable customers to find solutions on their own.
- Create a repository of best replies. Use a knowledge activation tool to enable support agents to access the best replies crowdsourced from all support Tiers.
Tiered support vs. swarming: which model fits your team?
Tiered support escalates an issue up a ladder of teams until someone can solve it. Swarming, also called Intelligent Swarming, drops the tiers: the first person who picks up an issue owns it until it’s resolved and pulls in experts as needed. Tiers suit high volumes of repeatable issues; swarming suits new, complex ones.
| Question | Tiered support | Swarming |
|---|---|---|
| How work moves | Escalated from Tier 1 to Tier 2 to Tier 3 | Stays with one owner, who brings in helpers |
| Who owns the issue | Each tier, in turn | The first person to work on it, until it’s resolved |
| Best for | High volumes of known, repeatable issues | New or complex issues with no documented fix |
| Main risk | Handoffs, repeated questions, and customers waiting between tiers | Experts pulled into too many cases if routing isn’t clear |
The Consortium for Service Innovation, which developed Intelligent Swarming, says the model isn’t right for every support environment. Many teams land on a hybrid: Tier 0 and Tier 1 still handle the common questions, and anything Tier 1 can’t solve goes to a swarm instead of a queue.
What both models depend on
Either way, the customer shouldn’t feel the structure. That means clean handoffs, where the next person gets the full context without asking the customer to repeat it, and replies that sound the same no matter who sends them. Standard empathy statements for customer service help every tier acknowledge a frustrated customer the same way.
This is where TextExpander fits. Save your best Tier 1 answers, escalation note templates, and documented expert fixes as Snippets, with fill-ins for the ticket details that change. Shared Snippets mean one update reaches every agent, whether they sit in Tier 1, Tier 3, or a swarm, and they work in any app you type in, on Mac, Windows, Chrome, iPhone, iPad, and Android. See how TextExpander for customer support keeps every reply consistent.
Try TextExpander
Although they might be separated by tiers, team members still need to effectively communicate and collaborate. Knowledge must be shared across the entire team, and every agent must have access to the most accurate, up-to-date information.
TextExpander helps customer support teams do that. Using our knowledge activation tool, support teams document and share knowledge across tiers to deliver the best support to customers.
TextExpander has a Free plan that’s free forever, no credit card required.
TextExpander is free. Your time isn’t.
Create shortcuts for the things you type most and start saving time everywhere you type. Use it solo or build a shared library with your team.
Free forever, no credit card required.
Frequently asked questions
What are the levels of tiered support?
Most tiered support teams use four levels. Tier 0 is self-service, such as knowledge base articles and automated password resets. Tier 1 is the first-line team of generalists who handle basic issues. Tier 2 is a smaller group of experienced technicians who take the issues Tier 1 can't solve. Tier 3 is made up of senior analysts or the engineers who built the product, and they resolve the hardest cases.
What is Tier 0 support?
Tier 0 support is everything customers can use to solve a problem on their own, without contacting an agent. It includes knowledge base articles, help center guides, blog posts, community forums, and automations such as password resets. A strong Tier 0 keeps simple, repetitive requests out of the queue, so Tier 1 agents have more time for the issues that need a person.
When should a support ticket be escalated to the next tier?
Escalate a ticket when the agent has tried the documented fixes and the issue still isn't solved, or when it needs access, skills, or permissions the current tier doesn't have. Before escalating, the agent should reproduce the problem if possible and write a clear note covering what the customer reported, what was tried, and what happened, so the next tier doesn't have to ask the customer again.
What is the difference between tiered support and swarming?
In tiered support, an issue moves up from one team to the next until someone can solve it. In swarming, there are no tiers: the person who first works on an issue owns it until it's resolved and brings in experts to help. Tiered support suits high volumes of repeatable issues, while swarming suits new, complex problems. Many teams combine the two.
