Quick answer
Technical support helps users solve technical problems with a product, through channels such as chat, email and phone. It is organized in tiers, so simple problems are fixed by generalists and hard ones reach specialists. The goal is to get the user working again, ideally on the first contact.
Formula: First-contact resolution = tickets solved at Tier 1 without escalation ÷ all tickets
What is technical support?
Technical support is the service that helps users of a product solve technical problems with it: they cannot log in, a feature fails, an install does not work, an integration returns an error. It is delivered through channels such as live chat, email, phone, remote sessions or a help centre, and it is usually organized in tiers so that simple problems are solved quickly by generalists and hard ones reach specialists.
Wikipedia describes tech support as a service that advises and assists registered users with problems related to technical products, and Techopedia calls it a subset of customer service. The useful way to hold the idea is by its goal. The goal is not to answer tickets; it is to get the user working again, ideally on the first contact, and to learn from the pattern of problems so fewer of them happen.
This page covers the model (tiers), the numbers that tell you whether it works, and a worked example. It is not a comparison of support providers; for the broader handling of requests, see the help desk guide for ecommerce.
How is technical support different from customer service?
The two overlap and share tools, but they answer different questions.
| Dimension | Customer service | Technical support |
|---|---|---|
| Typical question | "Where is my order?" "Can I change my plan?" | "The export fails with an error." "The script is not collecting data." |
| Needs | Policy and account knowledge | Product and troubleshooting knowledge |
| Usual first step | Look up the account | Reproduce or diagnose the problem |
| Typical output | An answer or an account change | A fix, a workaround or a bug report |
| Escalates to | A supervisor or billing | A more technical tier, then engineering |
In small teams the same person does both. The distinction still matters for measurement: a billing question and an install problem have very different expected resolution times, and mixing them in one average hides both.
What are the three tiers of technical support?
The common model has three tiers (sometimes called L1, L2 and L3), with self-service often placed in front as an unnumbered first layer.
| Tier | Who | What they handle | Escalates when |
|---|---|---|---|
| Self-service | Help centre, FAQ, knowledge base | Known, repeatable questions | The user cannot find or apply the answer |
| Tier 1 (L1) | Support generalists | Gather details, identify the real problem, solve simple issues such as login problems and setup checks | The problem needs deeper product knowledge or a fix they cannot apply |
| Tier 2 (L2) | Technical specialists | Deeper investigation; they review what Tier 1 already tried; diagnostics, configuration, remote sessions | The problem is new, unsolved or needs a code change |
| Tier 3 (L3) | Experts, often developers or people who know the back end | The hardest problems; develop fixes for new issues and test them before release | Rarely; the loop may end in a bug fix or a product change |
Two rules keep tiers useful. Every escalation carries the history: what the user reported, what was tried and how long they have waited, so the next tier does not start from zero. And escalation is a tool, not a failure: a Tier 1 agent who correctly escalates a hard ticket in five minutes serves the customer better than one who spends an hour guessing.
Which metrics tell you whether technical support works?
Four measures cover most of what matters; more can be added later.
| Metric | Definition | What it tells you |
|---|---|---|
| First response time | Time from the user's request to the first human reply | Whether people feel heard; see first response |
| Resolution rate | Resolved conversations ÷ all conversations | Whether the team closes what it opens; see resolution rate |
| First-contact resolution (FCR) | Tickets solved at Tier 1 without escalation ÷ all tickets | How much self-service and Tier 1 can absorb |
| Escalation rate | Tickets passed up a tier ÷ tickets that reached that tier | Whether tiers are sized and trained right; see ticket escalation |
Add satisfaction (a short score after resolution) and reopen rate (tickets that came back) if you can. Do not judge a team on speed alone: a fast, wrong answer looks good on first response time while resolution stays low.
Worked example: where 1,000 tickets go
Sample data: a software product receives 1,000 technical tickets in a month. Here is where they end up.
| Stage | Tickets in | Resolved here | Passed up | Rate |
|---|---|---|---|---|
| Tier 1 | 1,000 | 640 | 360 | FCR 64.0%; escalation 36.0% |
| Tier 2 | 360 | 250 | 110 | Resolved 69.4% of 360; escalation 30.6% |
| Tier 3 | 110 | 85 | 25 still open | Resolved 77.3% of 110 |
| Total | 1,000 | 975 | 25 open | Resolution 97.5% |
How to recompute: FCR = 640 ÷ 1,000 = 64.0%. Tier 2 escalation = 110 ÷ 360 = 30.6%. Total resolved = 640 + 250 + 85 = 975, and 975 ÷ 1,000 = 97.5%. The 25 open tickets are the 110 that reached Tier 3 minus the 85 it resolved.
What to do with it: Tier 2 is carrying 360 tickets, 36% of all volume. Suppose a knowledge-base article for the most common Tier 2 problem lets Tier 1 solve 100 more tickets on its own. Then Tier 1 resolves 740 (FCR 74.0%), and Tier 2 receives 260 instead of 360, which is 27.8% less. The specialists get time back for the harder tickets, and users with that problem are answered faster. Changing one article moved FCR by ten points, which is why the ticket topics that reach Tier 2 are worth reading every week.
What are the common mistakes?
- Measuring only speed. Fast first replies with low resolution mean customers wait politely and are not helped.
- One average for every ticket. A password reset and an integration bug differ by orders of magnitude in time. Segment by topic or tier.
- Escalation without context. Making the user repeat everything at Tier 2 is the quickest way to lose goodwill.
- No path from Tier 3 back to Tier 1. A bug fix should become a known answer at the front line, or the same ticket will come back next month.
- Treating self-service as optional. A clear help article often resolves a problem in zero agent minutes; keep it current.
- Counting unresolved tickets as closed. Auto-closing silent tickets inflates resolution rate. Report closed-without-confirmation separately.
Technical support with TapCub and AskCub
TapCub's live chat can run the front line of technical support on your site, and its analytics tell you what was happening to the user before they wrote in. It is a live chat inbox, not a full ticketing system: there are no formal tier fields, service-level timers or phone channels, so the tiers in the example are handled by transferring conversations between your agents.
- Self-service first. In Live chat › Knowledge base, Q&A entries are sent as written when a question matches and cost no AI call; pinned entries appear in the visitor FAQ, and opening an answer does not create a conversation. Only "not solved" hands the visitor to an agent.
- Tier 1 with context. In Live chat › Inbox, each conversation arrives with the visitor's source, current page and their last two days of browsing. One click opens the visitor profile in analytics. Common replies are inserted from Live chat › Canned replies by typing
/. - Escalate by transfer. Transfer a conversation to a colleague with deeper knowledge; internal notes stay hidden from the visitor and carry what was tried. Who can see all conversations is set in Live chat › Agents.
- See the problem from the user's side. For web issues, Monitoring › Errors shows error groups with the affected sessions, pages and devices, which helps a Tier 2 agent reproduce what the user saw.
- Measure it. Live chat › Reports gives conversation count, resolution rate (resolved ÷ all conversations), average first response (human replies only; an AI reply does not count), satisfaction, agent workload including transfers in and out, and the knowledge-base hit rate. Offline messages are counted separately and are not part of resolved. Escalation rate and FCR are not built-in metrics; calculate them from transfers and conversations as in the example.
Sources
- Wikipedia, Technical support (definition; Tier I, II and III model).
- Built In, What Is Technical Support?.
- Techopedia, Technical Support.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Analyst
Focuses on event analysis, conversion funnels, and retention, using clear metric definitions and structured analysis to explain product performance.