What is Ticket Deflection?

Ticket deflection is resolving a customer's question before it ever becomes an agent ticket — through a help center, an AI agent, or in-product answers. The deflection rate is the share of potential contacts handled this way. Higher deflection means lower cost, faster answers for customers, and agents freed for complex work.

Diagram: incoming questions split into a large deflected stream (help center and AI agent) and a small stream reaching an agent ticket.

How deflection works

Instead of every question reaching an agent, customers find their answer themselves: a help-center article surfaces at the right moment, or an AI agent resolves the question instantly in chat. Each of those is a deflected contact — the customer got helped, and no agent time was spent. Done well, deflection improves experience and efficiency at once.

How to raise your deflection rate

Build a strong, well-organized knowledge base, surface it where customers get stuck, and put an AI agent grounded in that content on the front line. The agent answers the common, documented questions completely and only escalates what genuinely needs a person — which is what moves deflection from a trickle to a meaningful share of volume.

Formula

Deflection rate % = (Self-service resolutions ÷ (Self-service resolutions + Tickets created)) × 100

Example: 800 help-center/AI resolutions against 200 tickets created: (800 ÷ (800 + 200)) × 100 = 80% deflection.

Selvo Help Center

Give customers a place to answer their own questions

Publish answers once in your Selvo help center and customers solve problems without opening a ticket. Your AI agent cites the same articles when it replies, so self-service and assisted support stay in sync.

See how Selvo Help Center works

Questions about Ticket Deflection

How is ticket deflection measured?

Commonly as the ratio of self-service or AI-resolved questions to total potential contacts. Definitions vary, so document yours — for example, counting help-center sessions that didn't lead to a ticket, or AI conversations closed without escalation.

Does deflection hurt customer experience?

Done badly (dead-end bots, thin docs) it frustrates people. Done well, it's faster than waiting for an agent — customers prefer an instant correct answer to a queue. The key is accuracy and an easy path to a human when needed.

Related terms

Cost per Contact

Cost per contact is the average fully-loaded cost of handling a single support interaction — total support spend divided by the number of contacts handled. It turns support's budget into a per-interaction number you can manage, and it's the metric automation most directly improves.

Resolution Rate

Resolution rate is the percentage of support tickets that get resolved out of all tickets received in a period. It's a fundamental throughput metric — are you actually closing what comes in? A resolution rate consistently below 100% means a growing backlog of unresolved issues.

Knowledge Base vs Wiki

A knowledge base is a structured, curated library of help articles built for a specific audience — usually customers solving problems. A wiki is a loosely structured, collaboratively edited collection of pages, usually for internal knowledge. Knowledge bases optimize for findability and self-service; wikis optimize for open, flexible contribution.

Browse the full customer support glossary →