What does a Customer Support FTE own, and what does it never touch?
It owns first-line resolution for the categories you name, answering from the knowledge base and policy pages with a citation on every reply; triage and routing; knowledge base upkeep by proposing articles for recurring gaps with sources; and the escalation summary for everything else. It never touches refunds, credits, account access, complaints, legal or safety language, or a distressed customer; those reach your team every time, with the FTE's summary attached, at every autonomy level.
It also never continues past its sources. A ticket with no source escalates with a note that the base has a gap, which is how the base improves.
What should a head of support ask?
Ask what always escalates and whether the list can be loosened by a setting: on ftes.ai it is fixed in the remit at every level and grows after incidents. Ask what an escalation contains: what was asked, what was found, why it did not resolve, a suggested next step, routed to the person who owns that category. Ask how the knowledge base improves: the FTE proposes articles from recurring gaps, sourced, for your approval. Ask what earns autonomy: one routine category at a time, within bounds, from a clean record, and never anything on the escalate list.
Ask how quality is reviewed: every reply scored against your rubric with itemised notes, patterns to you, coaching drafted for you to deliver, never feedback to an agent from the system.
- Escalate list: fixed at every level?
- Escalation contents: the four parts, routed by category?
- Knowledge base: proposed articles, sourced, approved by me?
- Autonomy: one category, bounded, from the record?
What should a head of support measure?
Measure first-line resolution per category against the baseline, median first response including out of hours, escalation volume by category, and escalation quality, meaning summaries that meet the standard. Measure knowledge gaps closed: proposed articles approved and first-line resolution in their categories afterwards. Measure approval rate per category with send-back reasons, which shows where the remit needs a rule. Satisfaction where you survey it, and unmeasured where you do not.
Refuse to measure reply volume. A hundred drafts nobody approved are a hundred tasks and no value.
What should a head of support refuse?
Refuse to start with several categories; one high-volume, low-risk category with a clean record is worth more than three muddled ones. Refuse to accept an escalation that arrives as a reassigned ticket; the summary standard is a remit rule. Refuse to promote a category to auto-send in the first month or on anything touching money or accounts, ever. Refuse to let articles publish unattended; the base is a source for the fact gate and a wrong article propagates.
And refuse to let the system deliver feedback to agents. Coaching is a decision about a person, and it is yours.
What happens to the team?
The team moves to the hard cases with better preparation. Agents who answered password resets handle the complaints and the account problems the FTE escalated, starting from the summary rather than from the inbox. The quality review surfaces knowledge gaps and inconsistent policy across the team, which are fixes to the base and the process rather than to people. Say this early, in each agent's terms, and let the team watch the first category succeed before the second arrives.
Overnight coverage of escalations may still need people; most heads of support find the FTE's first line reduces the need, and the decision is made from the record.
What do the first 30 days look like from the head of support's seat?
Week one: pick the category, confirm its articles, write the always-escalate list with receivers and the summary standard, connect the helpdesk with scoped credentials, and record the baseline. Weeks two to three: approve cited replies in seconds, send back with reasons, check every escalation against the standard, and approve the first proposed articles. Week four: read the FTE's own report, decide whether the one category has earned auto-send within bounds, and choose the second category.
By day 30 one category is owned with a cited source on every reply, the escalation path reaches your team with summaries, and the base has improved from the tickets that exposed its gaps.
What does the platform not do for a head of support?
It does not talk to a customer with money or feelings at stake; that is your team. It does not decide about your agents; quality patterns come to you as coaching notes to deliver. It does not answer beyond its sources, and it does not publish articles unattended. And it does not measure satisfaction without a survey connected; it marks it unmeasured.
A head of support who wants a bot that answers everything should look elsewhere. One who wants the known answers owned with citations and the hard cases reaching people with context has the mechanisms here.