Effective Automation Rate (EAR) measures the percentage of support tickets fully resolved by AI without human intervention and without a quality failure. It answers the question: "How much of my ticket volume is AI actually handling well?"

Most vendors report automation rate or deflection rate, which count any ticket touched by AI—including tickets where the AI failed, hallucinated, or frustrated the customer into abandoning the conversation. EAR is more rigorous. It only counts tickets where three conditions are met: the AI resolved the issue, the customer didn't return within a defined window (typically 72 hours), and the resolution passed quality checks.

Calculating EAR requires defining what counts as "independently resolved." At minimum, this means: (1) the ticket was closed without human involvement, (2) no reopens within the lookback window, and (3) no negative signals like CSAT bombs or escalation requests. Some teams add QA sampling to catch hallucinations that customers didn't catch.

EAR is the metric that matters for ROI conversations. If you're paying for AI support and only tracking automation rate, you're measuring activity, not outcomes. A 60% automation rate with a 30% quality failure rate means you're only getting 42% effective automation—and burning customer trust on the rest.

Related terms: Independently Resolved (IR), Resolution Rate, Automation Rate, Total Quality Score (TQS)