Why containment rate is the wrong KPI to put on a dashboard

Containment rate is the metric every voice AI deployment reports because it is the easiest one to define. It is also the metric most likely to be quietly inflated, mis-defined, or read in isolation by a steering committee that does not realise how much it is being told.

The honest version of the metric is autonomous resolution rate: contained calls, minus calls that re-contacted for the same intent within a defined window, divided by total in-scope calls. It is harder to measure, smaller in value, and much closer to what the customer would say if you asked them whether the AI fixed their problem.

A dashboard that shows containment without autonomous resolution rate next to it is a dashboard that rewards the wrong behaviour. Engineers optimising for containment will push the boundary of "contained" outwards until it includes calls that should have escalated; the re-contact line then quietly absorbs the cost a week later.

If you can only put one number in front of the executive sponsor, make it autonomous resolution rate. If you can put two, add CSAT on escalated calls — the early-warning indicator that scope has been pushed too far.