LoginSign Up
← Back to all sparks
T

Thread

SUPPORT
Velocity5.0

Thread is hardening its June voice launch rather than shipping the next one.

mspvoice-aioutbound-callingteams-integrationpsa-syncinternationalization
◆Current state
Thread put outbound calling into its MSP inbox in late June, and nearly everything since has been reinforcement: international regions, per-agent speech controls, and better contact mapping when the AI cannot identify a caller. A second track keeps closing gaps between Teams and Slack and the ticket itself, where reactions and assignment notifications now round-trip properly. Nothing in the last six weeks adds a new surface; all of it makes the June launch usable by more teams in more places.
◆Where it's heading
The voice work is moving from feature to infrastructure. Regional carrier bundles, recording-storage regions, KYC requirements and per-partner feature flags are the vocabulary of a product being deployed rather than demoed, and the release notes now read like operations documentation. Alongside that, Thread keeps narrowing the distance between where technicians actually work and where the ticket record lives. The direction is operational depth inside the MSP workflow, not expansion into a new category.
◆Prediction
Expect the company-context contact mapping to leave its feature flag for general availability, and international voice provisioning to shift from Thread-team coordination toward self-service as carrier bundles clear approval market by market.

◆Recent moves

  1. 4d ago

    Outbound Calling expands to supported international Voice workspaces

    The June outbound calling launch is now deployable outside North America, adding the UK, Netherlands, Australia and New Zealand behind regional voice infrastructure. The setup burden is substantial, with carrier bundles, KYC documentation, and an agent country that permanently fixes the recording-storage region, which makes this a deployment milestone rather than a switch being flipped.

  2. 4d ago

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

    Outbound voice agents pick up the speech speed and volume controls that inbound agents already had, applied to the auto-play consent message. Parity work of this kind is the tell that the June launch is being tuned against real call audio rather than extended.

  3. 4d ago

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

    Voice AI can now hold on to a caller's company when it cannot identify the individual, falling back to the PSA default contact instead of losing the context entirely. Thread is explicit that this is context and not authentication, a distinction that matters on an MSP ticket and one reason the change is rolling out partner by partner behind a flag.

  4. 13d ago

    Teams Emoji Reactions -> Inbox

    A contact's emoji reaction in a Teams group chat now lands on the matching Inbox message, and optionally as an internal note on the PSA ticket. It is a small fidelity win inside the larger project of treating Teams as a first-class channel rather than a lossy relay.

  5. 13d ago

    Companion App: Notify Secondary Members when they are assigned

    Secondary assignees now receive Companion App notifications through Teams and Slack, where previously only the primary assigned member did. For MSP teams that share tickets across technicians, this closes a gap where assigned work could sit unannounced.

  6. 14d ago

    Control Flow Ticket Notifications in Teams & Slack

    Flow notifications into Slack and Teams can now be scoped to specific update types, separating external notes, internal notes and activity logs instead of firing on everything. Existing flows keep the old send-all behavior until edited, which is the right default for a customer base that automates heavily.