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.
What is 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.
Also: support rep · customer service agent
Human agent and AI agent
Since 2023 the word "agent" is also used for software that handles conversations with nobody involved. Both senses can turn up in the same sentence — "the agent escalates to the agent" — so it is worth saying "AI agent" for the second. In this glossary, an agent on its own is a person.
Why it matters
What changes in a SaaS
At a small SaaS, whoever answers support is usually also whoever knows the product best. That turns every support hour into an hour not spent on product, and it is why the real cost of a ticket is not the tool licence but that person time.
Support agent in detail
What actually eats the time
Not writing the answer. It is the trip before it: understanding what is being asked, opening the admin panel, checking the plan, the usage and the last payment, and coming back. On top of that sits the cost of breaking concentration, which shows up in no tool metrics.
Tiers
On organised teams the work is split by tier: the first handles the known, the second what needs technical knowledge, the third what ends up with engineering. On small teams all three tiers are the same person, which is why one complex question takes the whole morning.
What can be taken off their plate
Everything that is documentary repetition, where the answer is the same for everybody, and a good part of the repetition that needs a customer-specific fact, the kind that requires opening the account. What cannot be taken away is judgement, and that is exactly what they were hired for.
How Intake handles it
Questions about support agent
How many tickets does a support agent handle per day?
The number varies so much between products that comparing it is close to useless. It is more useful to measure real time per ticket, including the context hunt and the interruption, and multiply by volume: that number is genuinely comparable with the cost of automating.
Does an AI agent replace a support agent?
It replaces part of the job: the repeated work and the cases resolved by checking one fact. Anything needing judgement, or any customer who asks for a person, still belongs to a human, and that is the part that adds value.
What is the difference between a support agent and a CSM?
The agent reacts to what arrives; the CSM gets ahead of it. The agent is measured in times and resolution, the CSM in retention.
Related terms
A term on its own is only half understood. These come up in the same conversation.
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.
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.
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.
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.
AHT — Average handle time
Average handle time is the time an agent actively spends on a question: reading it, finding the context, answering it and logging whatever needs logging. It excludes waits, which is why it is the metric that best approximates what a given support volume costs in hours.
Service desk
A service desk is the single point of contact between an organisation and the people who use its technology services. Beyond resolving incidents, it handles service requests, changes and access, and works through formal processes: a service catalogue, service level agreements and approval flows.
