Kapture CX vs Thread

Thread spent the summer on Voice: outbound calling went live in June, then expanded to supported international workspaces, picked up per-agent consent-message speed and volume controls, and learned to hold company context when a caller can't be identified. Around it sat inbox and notification work — Teams emoji reactions routed into the Inbox, ticket notification control in Teams and Slack, refreshed navigation. The newest release moves somewhere else entirely: XLAs replace the SLA model with per-source response and resolution targets, risk-coloured timers in the Inbox, business hours built into the clock, and flows that alert Slack or Teams before a threshold is crossed.

Two things change here. Thread reframes the service-level contract from after-the-fact compliance into a live risk signal, with per-source targets conceding that a Slack request and a phone call at the same priority are not the same promise. The more consequential detail is that it is configured entirely in Thread's own admin panel with no PSA-side setup — the product has been a modern front end on someone else's system of record, and pulling the service-level definition in-house moves a core primitive across that line. The Voice arc, meanwhile, has settled into refinement rather than expansion.

Expect reporting to follow the timers, since attainment dashboards and per-source breakdowns are the obvious use of data the product has only just begun collecting. The entry describes thresholds and alerting but says nothing about what happens after a breach, so whether XLAs go on to drive escalation or routing cannot be read from it.