Macha
CX & Support Metrics

Ticket Deflection

Definition

Ticket deflection is the share of customer questions resolved through self-service or automation before they ever become a human-handled support ticket.

Also known as: deflection rateself-service deflection

How to calculate it

A common formula is: deflected interactions ÷ total interactions (deflected + human-handled). If 1,000 people start a chat and 600 get their answer from a help center or AI agent without an agent stepping in, deflection is 60%.

Definitions vary between vendors, so always confirm what a given tool counts as "deflected" — some count any self-service view, others only count sessions that never reached a human.

Why it matters

Deflection is the headline metric for support automation ROI: every deflected ticket is one an agent didn't have to handle. But it can be gamed — a customer who gives up isn't really "deflected." Pair it with CSAT and resolution rate so you're measuring genuinely solved problems, not just avoided ones.

Frequently asked

What is a good ticket deflection rate?

It varies widely by industry and query mix, but many teams target 20–60% for well-documented, repetitive questions. Judge it alongside CSAT so you're not counting abandonments as deflections.

Is deflection the same as resolution?

No. Deflection means a ticket never reached a human; resolution means the customer's problem was actually solved. Good automation aims for both.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial