Front line
The front line is whoever receives conversations before anybody else: they resolve what is documented, gather the missing information and pass on what they cannot close. It is the filter that decides what reaches the rest of the team and in what state.
What is front line?
The front line is whoever receives conversations before anybody else: they resolve what is documented, gather the missing information and pass on what they cannot close. It is the filter that decides what reaches the rest of the team and in what state.
Also: first line · tier 1 · L1
Filtering is not answering and forwarding
A front line that forwards everything with a "let me get somebody who knows" is not filtering: it adds a step and a customer who has already explained their case once. The value is in what it resolves and, when it cannot, in the context it leaves for whoever comes next.
Why it matters
What changes in a SaaS
Because it protects the time of the expensive people. A team with no front line sends every question straight to whoever knows the product deeply, and that person ends up explaining how to change a password instead of fixing what only they can fix.
Front line in detail
What it needs to work
Good documentation and access to customer data. Without the first it does not resolve; without the second it cannot even diagnose. A front line with neither is a mailbox with a person attached.
Where an AI agent fits
It is the layer that automates best, because its job is exactly the repeated and the documented. With the difference that an agent with access to account state also closes part of what today moves up to the second tier.
What to measure
The share it resolves without escalating and, of what it escalates, how much comes back for lack of context. The second figure says whether the filter works or merely distributes.
How Intake handles it
Questions about front line
Does a three-person team need a front line?
As a job title, no. As a rota, yes: having one person a day be the one who watches what comes in stops all three interrupting themselves for every conversation.
Does an AI agent replace the front line?
It covers a good part of the job, the documented and the repeated. Anything needing judgement still moves up, and for that the handoff has to arrive with the case assembled.
Related terms
A term on its own is only half understood. These come up in the same conversation.
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.
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.
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.
AI agent
An AI agent is a system that, beyond generating text, reads data and takes actions to finish a task. In support that means it checks the actual state of the customer account before answering, and when the answer involves doing something, it does it instead of explaining how.
Routing
Routing is the set of rules deciding which queue or which person each incoming conversation goes to: by detected language, by customer plan, by words in the message or by team workload. It replaces somebody distributing by hand.
Satisfaction per agent
Satisfaction per agent is CSAT broken down by the person who handled each conversation. It is used to see who needs support and what is working, and it is one of the metrics that does the most damage when used for anything else.
