LoginSign Up
← Back to all sparks
T

Thread

SUPPORT
Velocity6.3

Thread takes the service-level clock off the PSA and runs it itself

msp-helpdeskservice-levelsxlareal-time-alertingpsa-independencevoice-ai
◆Current state
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.
◆Where it's heading
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.
◆Prediction
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.

◆Recent moves

  1. 19d ago

    XLAs (Experience Level Agreements)

    ⚡ SPARK

    XLAs land as a new arc, unrelated to the Voice work that has filled this feed since June. Where the product had been adding channels and polish on top of an inherited PSA, this release redefines how service is measured and puts the configuration in Thread's own admin panel — the first entry in months that changes what the product is rather than what it reaches.

  2. 1mo ago

    Outbound Calling expands to supported international Voice workspaces

    Outbound calling reaches supported international Voice workspaces, widening the reach of the capability that sparked in June without changing what it does. Geographic expansion of an established surface.

  3. 1mo ago

    Outbound Calling: per-agent consent-message speed and volume

    Per-agent control over consent-message speed and volume — a compliance-driven refinement to outbound calling. It signals the Voice arc moving from launch into the regulatory detail that comes with running calls at scale.

  4. 1mo ago

    Voice AI: keeping the company context when the caller is unclear

    Voice AI keeps company context when it can't identify the caller, so an unrecognised number no longer drops the agent into a blank slate. A reliability fix on the weakest point of an automated phone path.

  5. 1mo ago

    Teams Emoji Reactions -> Inbox

    Teams emoji reactions now surface in the Inbox, closing a gap where acknowledgement in chat was invisible to the ticket. Part of the steady work making Slack and Teams first-class ticket surfaces rather than notification endpoints.

  6. 1mo ago

    Companion App: Notify Secondary Members when they are assigned

    The companion app notifies secondary members on assignment, a small routing correction so shared ownership of a ticket actually reaches everyone named on it.