What changed
AWS added outcome scoring to Amazon Connect Customer analytics. Each interaction is scored for whether the customer left satisfied, is at risk of churning, made a purchase or resolved the need in self-service. Each metric has a default definition that businesses can adjust, and the metrics are available in analytics dashboards and through APIs. In a separate announcement the same day, AWS added customer segments to metrics, so any metric can be compared for repeat callers versus other contacts or for high-lifetime-value customers.
Vendor documentation (opens in a new tab)Why it matters
Efficiency metrics such as handle time say little about whether a contact actually worked. Outcome scores and segment views can show, for example, that repeat callers or high-value customers are faring worse than the average suggests, but the scores are only as meaningful as the definitions behind them.
CxCave practical context
Who should care
- CX leadership
- Reporting teams
- Quality teams
Implementation considerations
REVIEWReview the default outcome definitions against how your business defines success, adjust them before sharing results widely, and add repeat-caller and lifetime-value cuts to the dashboards leadership already uses.
CxCave recommendation, not a vendor mandate unless explicitly stated.