Sales
Account Executive
Four levels from Associate to Principal AE, across six competencies from building pipeline to closing complex deals.
- 4 levels
- 6 competencies
Career ladder template
Customer support career ladder template
Five levels from Support Associate to Head of Support, across seven competencies from solving tickets to running the function.
Free plan · No credit card required
This career ladder is written for support teams in companies of roughly 20 to 200 people: a handful of people answer every channel, know the product as well as anyone, and are the first to hear when something breaks. It describes five levels, from someone in their first support job to the person who owns support for the whole company. Its top level, Head of Support, is the head of the support function rather than an individual-contributor level.
Levels are defined by what a person does, not by how many tickets they close. Read a row of the competency matrix from left to right to see how one expectation grows from handling a single conversation to shaping how the company treats every customer. Use it to explain what the next step looks like, to structure check-ins, and to make promotion cases that rest on more than a satisfaction score.
Treat it as a draft. Match the levels to the titles you already use, drop the ones your team is too small to need, and rewrite each expectation in your own words before you share the ladder with the team.
The levels at a glance
Support Associate
Learns the product and the tools, and resolves common questions using saved replies and the help centre.
- Scope
- Individual conversations on the most common topics, with a more experienced colleague to turn to.
Support Specialist
Resolves most customer issues independently, across channels, and knows when and how to escalate the rest.
- Scope
- The full range of everyday conversations in one or more channels, including account and billing questions.
Senior Support Specialist
Owns the hardest cases, investigates technical problems, and is the team's go-to person for one or more product areas.
- Scope
- Complex and escalated cases, one or more product areas, and the support side of new feature launches.
Support Lead
Runs the day-to-day work of the support team and improves how it handles volume, quality and escalations.
- Scope
- The whole support queue and its processes, often with direct responsibility for two to six people.
Head of Support
Owns customer support as a function: its strategy, staffing, budget and place in the company's decisions.
- Scope
- Every customer channel, the support team and its leads, and support's influence on product and revenue.
Competency matrix
Each row is a competency and each column a level. Read a row from left to right to see how the expectation grows.
What each competency means
- Issue resolution
- Understanding what the customer actually needs and getting them to a working answer.
- Customer communication
- Writing and speaking to customers clearly, kindly and in the company's voice.
- Product and technical knowledge
- Knowing how the product works, how customers use it, and where it tends to break.
- Escalation and product feedback
- Turning what customers report into bugs, fixes and product decisions.
- Knowledge base and self-service
- Writing the help content and saved replies that let customers and colleagues answer questions without waiting.
- Support operations
- Running the queue, the tools and the numbers that keep support reliable as volume grows.
- Mentoring and leadership
- Helping colleagues grow and building a support team people want to stay in.
| Competency | Support Associate | Support Specialist | Senior Support Specialist | Support Lead | Head of Support |
|---|---|---|---|---|---|
| Issue resolution | Resolves common questions with the help centre and saved replies, asks clarifying questions before answering, and hands over a case with a clear summary when it is beyond them. | Resolves most cases in the first reply or two without help, reproduces problems in a test account before escalating, and closes the loop with the customer once a fix ships. | Takes on the cases nobody else could solve: digs into logs, data and account settings, finds the real cause, and turns one-off fixes into steps others can follow. | Sets how cases are triaged, prioritised and handed over across the team, watches the queue for patterns, and steps in personally on the cases that put a customer relationship at risk. | Decides the support model — channels, hours, response targets, tiers — so that customers get a fair, consistent answer whichever way they reach the company. |
| Customer communication | Writes replies that are accurate, polite and easy to follow, adapts saved replies to the customer's situation, and checks that the question was actually answered. | Adjusts tone and detail to the customer and the situation, explains limitations and workarounds honestly, and calms frustrated customers without over-promising. | Handles the most sensitive conversations — outages, data problems, angry key accounts — and writes the customer-facing messages for incidents and changes in the product. | Defines the team's tone of voice and quality standards, reviews a sample of conversations every week, and gives each person specific feedback on their writing. | Owns how the company communicates with customers in difficult moments, and speaks directly with key customers and leadership when a relationship is at stake. |
| Product and technical knowledge | Knows the main features and common workflows, finds answers in internal docs before asking, and keeps a list of what they have learned for their next shift. | Knows the product end to end, including settings, integrations and billing, and reads basic logs, error messages or API responses to narrow down a problem. | Is the reference for one or more product areas, learns new features before they launch, and trains the rest of the team on them. | Makes sure the team's knowledge keeps up with the product: plans training before launches, spreads expertise so no area depends on one person, and onboards new hires in weeks rather than months. | Gets support involved early in product decisions, so that launches come with documentation, training and a support plan instead of a surprise spike in tickets. |
| Escalation and product feedback | Follows the escalation process, tags conversations correctly, and attaches the details engineers need: account, steps, screenshots and expected behaviour. | Writes bug reports that engineers can act on without asking follow-up questions, links duplicate reports, and keeps customers updated while a fix is in progress. | Spots trends across conversations, backs them with numbers, and brings them to product and engineering with a clear description of the customer impact. | Runs the regular feedback loop with product and engineering: agrees escalation rules and response times, tracks open issues to resolution, and reports what customers ask for most. | Makes customer pain a standing input to the roadmap, with data that leadership trusts, and agrees with product and engineering how support issues are prioritised. |
| Knowledge base and self-service | Flags articles that are wrong or out of date, and suggests a new saved reply when the same question comes in again and again. | Writes and updates help-centre articles and saved replies for their areas, with screenshots and steps that match the current product. | Owns the help content for whole product areas, rewrites it based on what customers keep asking, and measures whether articles actually reduce tickets. | Sets the structure, style and review process for the knowledge base, and decides with the team which topics to cover next based on ticket data. | Sets the self-service strategy — help centre, in-product help, community, chatbot — and invests in it so that support grows more slowly than the customer base. |
| Support operations | Works the queue in the agreed order, meets the team's response targets for their shifts, and keeps case statuses and tags accurate. | Manages their own workload across channels, meets response and resolution targets in a normal week, and suggests changes when a process slows them down. | Improves the team's setup: builds macros, automations and views in the helpdesk tool, and fixes the bottlenecks that hurt response times. | Plans schedules and coverage, tracks response time, backlog and satisfaction every week, and changes routing, staffing or process when the numbers move. | Owns support's tools, budget and metrics, forecasts volume from the company's growth plans, and makes the case for headcount or tooling before the team is overloaded. |
| Mentoring and leadership | Asks for feedback on their replies, shares useful findings in the team channel, and helps keep the team's shared notes up to date. | Helps newer colleagues with tricky cases, reviews their replies when asked, and covers for teammates during busy periods. | Mentors one or two people, runs onboarding for new hires in their product areas, and gives teammates honest, specific feedback. | Holds regular 1:1s with the team, sets development goals with each person, notices burnout early, and takes part in hiring. | Builds and develops the support team and its leads, defines the career paths in this ladder, and makes support a respected place to grow a career. |
Scroll the table sideways to see every level.
Download as CSV Opens in Excel, Google Sheets or Numbers.
Support Associate: what is expected
Learns the product and the tools, and resolves common questions using saved replies and the help centre. Individual conversations on the most common topics, with a more experienced colleague to turn to.
- Issue resolution
- Resolves common questions with the help centre and saved replies, asks clarifying questions before answering, and hands over a case with a clear summary when it is beyond them.
- Customer communication
- Writes replies that are accurate, polite and easy to follow, adapts saved replies to the customer's situation, and checks that the question was actually answered.
- Product and technical knowledge
- Knows the main features and common workflows, finds answers in internal docs before asking, and keeps a list of what they have learned for their next shift.
- Escalation and product feedback
- Follows the escalation process, tags conversations correctly, and attaches the details engineers need: account, steps, screenshots and expected behaviour.
- Knowledge base and self-service
- Flags articles that are wrong or out of date, and suggests a new saved reply when the same question comes in again and again.
- Support operations
- Works the queue in the agreed order, meets the team's response targets for their shifts, and keeps case statuses and tags accurate.
- Mentoring and leadership
- Asks for feedback on their replies, shares useful findings in the team channel, and helps keep the team's shared notes up to date.
Support Specialist: what is expected
Resolves most customer issues independently, across channels, and knows when and how to escalate the rest. The full range of everyday conversations in one or more channels, including account and billing questions.
- Issue resolution
- Resolves most cases in the first reply or two without help, reproduces problems in a test account before escalating, and closes the loop with the customer once a fix ships.
- Customer communication
- Adjusts tone and detail to the customer and the situation, explains limitations and workarounds honestly, and calms frustrated customers without over-promising.
- Product and technical knowledge
- Knows the product end to end, including settings, integrations and billing, and reads basic logs, error messages or API responses to narrow down a problem.
- Escalation and product feedback
- Writes bug reports that engineers can act on without asking follow-up questions, links duplicate reports, and keeps customers updated while a fix is in progress.
- Knowledge base and self-service
- Writes and updates help-centre articles and saved replies for their areas, with screenshots and steps that match the current product.
- Support operations
- Manages their own workload across channels, meets response and resolution targets in a normal week, and suggests changes when a process slows them down.
- Mentoring and leadership
- Helps newer colleagues with tricky cases, reviews their replies when asked, and covers for teammates during busy periods.
Senior Support Specialist: what is expected
Owns the hardest cases, investigates technical problems, and is the team's go-to person for one or more product areas. Complex and escalated cases, one or more product areas, and the support side of new feature launches.
- Issue resolution
- Takes on the cases nobody else could solve: digs into logs, data and account settings, finds the real cause, and turns one-off fixes into steps others can follow.
- Customer communication
- Handles the most sensitive conversations — outages, data problems, angry key accounts — and writes the customer-facing messages for incidents and changes in the product.
- Product and technical knowledge
- Is the reference for one or more product areas, learns new features before they launch, and trains the rest of the team on them.
- Escalation and product feedback
- Spots trends across conversations, backs them with numbers, and brings them to product and engineering with a clear description of the customer impact.
- Knowledge base and self-service
- Owns the help content for whole product areas, rewrites it based on what customers keep asking, and measures whether articles actually reduce tickets.
- Support operations
- Improves the team's setup: builds macros, automations and views in the helpdesk tool, and fixes the bottlenecks that hurt response times.
- Mentoring and leadership
- Mentors one or two people, runs onboarding for new hires in their product areas, and gives teammates honest, specific feedback.
Support Lead: what is expected
Runs the day-to-day work of the support team and improves how it handles volume, quality and escalations. The whole support queue and its processes, often with direct responsibility for two to six people.
- Issue resolution
- Sets how cases are triaged, prioritised and handed over across the team, watches the queue for patterns, and steps in personally on the cases that put a customer relationship at risk.
- Customer communication
- Defines the team's tone of voice and quality standards, reviews a sample of conversations every week, and gives each person specific feedback on their writing.
- Product and technical knowledge
- Makes sure the team's knowledge keeps up with the product: plans training before launches, spreads expertise so no area depends on one person, and onboards new hires in weeks rather than months.
- Escalation and product feedback
- Runs the regular feedback loop with product and engineering: agrees escalation rules and response times, tracks open issues to resolution, and reports what customers ask for most.
- Knowledge base and self-service
- Sets the structure, style and review process for the knowledge base, and decides with the team which topics to cover next based on ticket data.
- Support operations
- Plans schedules and coverage, tracks response time, backlog and satisfaction every week, and changes routing, staffing or process when the numbers move.
- Mentoring and leadership
- Holds regular 1:1s with the team, sets development goals with each person, notices burnout early, and takes part in hiring.
Head of Support: what is expected
Owns customer support as a function: its strategy, staffing, budget and place in the company's decisions. Every customer channel, the support team and its leads, and support's influence on product and revenue.
- Issue resolution
- Decides the support model — channels, hours, response targets, tiers — so that customers get a fair, consistent answer whichever way they reach the company.
- Customer communication
- Owns how the company communicates with customers in difficult moments, and speaks directly with key customers and leadership when a relationship is at stake.
- Product and technical knowledge
- Gets support involved early in product decisions, so that launches come with documentation, training and a support plan instead of a surprise spike in tickets.
- Escalation and product feedback
- Makes customer pain a standing input to the roadmap, with data that leadership trusts, and agrees with product and engineering how support issues are prioritised.
- Knowledge base and self-service
- Sets the self-service strategy — help centre, in-product help, community, chatbot — and invests in it so that support grows more slowly than the customer base.
- Support operations
- Owns support's tools, budget and metrics, forecasts volume from the company's growth plans, and makes the case for headcount or tooling before the team is overloaded.
- Mentoring and leadership
- Builds and develops the support team and its leads, defines the career paths in this ladder, and makes support a respected place to grow a career.
How to adapt this ladder
Use only the levels your team needs
A support team of three needs Associate, Specialist and Senior at most. Add a Support Lead when someone is really running the queue and coaching others, and a Head of Support when support needs its own seat in planning and budgeting.
Use metrics as evidence, not as the ladder
Response times and satisfaction scores show how a person works, but they depend on shifts, channels and product areas. Look at them next to the expectations in this ladder, and never promote on ticket volume alone.
Decide how technical your support should be
A developer tool needs specialists who read logs and call APIs; a consumer app may not. Rewrite the Product and technical knowledge row to match what your customers actually ask, so the bar is explicit.
Place your current team on the draft
Before you publish, ask the person who leads support to place everyone on the ladder and note one example per competency. Wherever they hesitate, the wording is too vague — fix it, then publish.
FAQ
Questions about this ladder
How many levels should a customer support career ladder have?
For a company of 20 to 200 people, three to five are enough: one or two levels for handling conversations, a senior level for complex cases and product expertise, and a lead or head of support once the team needs one. Add a level only when there is a real difference in what people do.
Should customer support promotions be based on CSAT and ticket volume?
Use them as evidence, not as the decision. Ticket volume rewards easy cases, and satisfaction scores depend on the product as much as on the reply. A promotion case should show the person meeting the next level's expectations — harder cases, better help content, product feedback that led to a fix.
How do support tiers (Tier 1, 2 and 3) map to career levels?
Tiers describe how cases are routed; levels describe what a person can do. In small teams a Specialist often handles Tier 1 and 2, and a Senior takes Tier 3 escalations. Keep the two separate so that a person can grow without waiting for a new tier to be created.
Is a Support Lead a manager or a senior individual contributor?
In most companies of this size a Support Lead does both: they run the queue and also hold 1:1s with a few people. If your senior people want to grow without managing, keep a Senior Support Specialist path that goes deeper into product areas, operations or tooling instead.
Can customer support be a long-term career, or is it a stepping stone?
It can be both. A clear ladder makes staying in support a real option, with growing scope and pay. Some people will move into customer success, QA, product or engineering — treat that as a win, and use the ladder to show which skills carry over.
Build this career ladder in LadderKit — free
Set up its levels and skills for your team, assess people against them in check-ins, and keep promotion decisions consistent.
Free plan · No credit card required
Related templates
Product
Product Manager
Five levels from Associate PM to Head of Product, across six competencies from discovery to product strategy.
- 5 levels
- 6 competencies
Engineering
QA Engineer
Four levels from Junior QA to Lead QA Engineer, across six competencies from test design to quality practices.
- 4 levels
- 6 competencies
Further reading
- Career ladders
How to build a career ladder: a step-by-step guide
A practical, seven-step method for companies of 20 to 200 people: tracks, levels, competencies, expectations, calibration and rollout — with a worked example and the mistakes to avoid.
Updated 1 October 2026