Thread
Also known as: Thread AI, Magic Agents, Thread Voice AI
AI service desk for MSPs that automates triage, dispatch, and client conversations across chat, email, and phone with Magic Agents, resolving routine tickets and prepping the rest for technicians.
Thread is an AI service desk built for managed service providers, automating triage, dispatch, and client conversations across chat, email, phone, Microsoft Teams, and Slack.
Its Magic Agents handle ticket intake, gather details, categorize and prioritize requests, and resolve fifteen to twenty five percent of tickets end to end with no technician involvement, sending the remainder to the right technician fully prepped.
Thread reports triage, dispatch, categorization, and time entries running automatically at ninety six percent accuracy and says it has returned more than half a million hours of technician work across seven hundred fifty plus MSP partners processing over one hundred seventy million tickets.
A System of Agents spans the service journey: a Triage Agent collects context and routes, a Reminder Agent checks whether issues are still active and closes resolved threads, an Overflow Agent ensures no call goes to voicemail, and a Memory Agent (part of Service Intelligence) builds a living memory of each contact's devices, preferences, and past issues so any technician can deliver service as if they know the client. Thread Voice AI, generally available January 2026, automates the phone channel with capture, transcription, and automatic ticketing.
Founded in 2017, Thread says it was among the first to bring generative AI to the MSP space, through Microsoft's Azure OpenAI Service. Claude on AWS Bedrock now runs its Triage Agent and Super Magic features, with Azure carrying the other AI features. It raised an eighteen million dollar growth round led by Susquehanna Growth Equity in December 2025, bringing total capital to thirty million dollars, and guarantees positive ROI within sixty days or a refund.
Vendor details
Canonical URL
https://www.getthread.com
Category
Customer support agent
Subcategory
AI service desk for MSPs
Funding status
Growth equity; eighteen million dollar round led by Susquehanna Growth Equity with Headline (Dec 2025), thirty million dollars total raised
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Native integrations with ConnectWise PSA, Autotask, and HaloPSA plus Microsoft Teams, Slack, and Microsoft 365; connects to automation tools Rewst, Power Automate, and Zapier for human in the loop automations, and integrates with Pia for full ticket resolution.
In practice
A client messages the service desk and the Triage Agent gathers device and issue details, categorizes the ticket at ninety six percent accuracy, and routes it into the PSA fully prepped.
The Overflow Agent answers an after hours call that would have gone to voicemail, collects details, and escalates a P1 to the on call team.
Thread plus Pia resolves a routine password or access request end to end in the PSA with no technician acting as middleman.
Sources & related URLs
Research sources
Agentic Index coverage score
9.0 / 14 capabilities · 64%
| Integrations & Tool Calling | Full |
|---|---|
|
Native connections reach the systems an MSP runs on, with write actions into the ticket record. Thread integrates with the three main MSP PSAs, ConnectWise PSA, Autotask and HaloPSA, plus Microsoft Teams, Slack and Microsoft 365, and the agents write into them as well as reading. Triage sets ticket properties, categorizes, prioritizes, assigns a technician and creates time entries automatically, and Thread reports 96% accuracy on those properties. Beyond the PSA, Thread connects to Rewst, Power Automate and Zapier for automation and to Pia for full ticket resolution, with Triage passing structured data into Pia to complete PSA and Microsoft 365 actions end to end. Sourcegetthread.comread 2026-09-05 |
|
| Workflow Orchestration | Full |
|
Several specialized agents cover one journey end to end, with structured handoff between them and out to another platform. The System of Agents divides the service desk by job. Triage identifies the request, gathers context and triggers the workflow, Overflow catches calls that would go to voicemail and escalates a P1 to the on call team, Reminder checks whether an issue is still live and closes threads that resolved themselves, and Memory maintains the contact record underneath. Triage passes structured data into Pia to complete PSA and Microsoft 365 automation, so a routine password or access request finishes without a technician acting as middleman, and everything else routes to the right person with the ticket already categorized, prioritized and prepped. Sourcegetthread.com/blog/magic-agents-a-new-era-of-ai-powered-automation-for-mspsread 2026-09-05 |
|
| Knowledge Grounding & RAG | Full |
|
Thread grounds its agents in ticket resolution history, knowledge articles and ITIL best practice, and builds a living service catalog from historical tickets, so categories and answers reflect how that MSP actually works instead of a generic taxonomy, and the catalog updates as tickets accumulate. Thread describes the underlying conversational dataset as the largest in the MSP market, drawn from more than 170 million tickets across 750-plus partners. Device, preference and issue history for each contact sits with the Memory Agent. Sourcegetthread.comread 2026-09-05 |
|
| Human Oversight & Guardrails | Full |
|
The partner sets the autonomy boundary, and the end user always has a way out. Magic Agents are customized to the security and permissions each MSP needs, so the partner defines what agents may do in their clients' environments instead of accepting a default. Autonomy is bounded on purpose, with agents resolving 15 to 25 percent of tickets end to end and handing the rest to a technician fully prepped. Thread says the AI's job is triage and information gathering and that anything complex hands off immediately with full context, and end users are told that typing "speak to an engineer" at any point bypasses the assistant entirely. Automations built on Rewst, Power Automate and Zapier are described as human in the loop. There is no approval queue before individual agent actions go out. Sourcedocs.getthread.com/article/i6mm06bsv7-thread-partner-change-management-guideread 2026-09-05 |
|
| Security, Identity & Governance | Partial |
|
The security program is in place, but the SOC 2 attestation has not been issued yet. The Trust Center publishes continuous control monitoring across 107 controls, a subprocessor list, public data handling documents and restricted reports available on request. Thread acts as a data processor with processing terms available on request, data is encrypted, communications are logged into the ticketing system, and Thread states customer data is not used to train Claude or any other model, not by AWS, not by Anthropic and not by Thread. The SOC 2 Type II audit is in progress, with a bridge letter available under NDA, and Thread tells partners not to describe it as SOC 2 certified until the report is issued. AWS and Azure hold SOC 2 Type II and ISO 27001 for the clouds Thread runs on, not for Thread itself. Sourcedocs.getthread.com/security-billing/soc-2-and-compliance-statusread 2026-09-05 |
|
| Observability & Auditability | Partial |
|
Performance is measured, but execution is not traced. Thread reports ticket properties set at 96% accuracy, sentiment at 97% positive, resolution rates, hours returned to technicians and an ROI calculator, giving a desk manager a clear read on what the agents achieved across more than 170 million tickets. Communications are logged into the ticketing system, so a conversation can be retrieved as a ticket record. There is no reasoning trace for each decision, tool call log, source attribution on an answer or configuration audit trail for an agent, so a manager can see that triage was 96% accurate without being able to reconstruct why a particular ticket was categorized as it was. Sourcegetthread.comread 2026-09-05 |
|
| Memory & State Persistence | Full |
|
The Memory Agent, part of Service Intelligence, creates a living memory for every contact, remembering their devices, preferences and past issues and updating automatically as new interactions happen, so any technician on the desk can serve a client as if they already know them. The platform forms this state from interactions and keeps it across separate conversations, tied to an identifiable contact, beyond a lookup against the PSA. MSP technicians rotate, and the memory is what carries over when they do. Ticket resolution history, ITIL practice and the service catalog built from historical tickets sit on the knowledge side. Sourcegetthread.com/blog/magic-agents-a-new-era-of-ai-powered-automation-for-mspsread 2026-09-05 |
|
| Deployment & Data Residency | Partial |
|
Thread names one region and offers no choice. Data is held in the United States, application data lives in AWS US East in Northern Virginia, and Claude inference runs on Bedrock's US region capacity, with Azure carrying the other AI features. There is no alternative region, no location the customer selects, and no self hosted, private cloud or single tenant option. Thread acts as a data processor, with processing terms available on request and a subprocessor list published at the Trust Center. Sourcedocs.getthread.com/article/2gttcwtp4a-thread-ai-on-aws-bedrock-anthropic-claude-data-processing-security-triage-agent-super-magicread 2026-09-05 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
A named agent set ships for an MSP to switch on, not a catalog to browse. The System of Agents has a Triage Agent that collects context, categorizes and routes, a Reminder Agent that checks whether issues are still active and closes resolved threads, an Overflow Agent that stops calls reaching voicemail, and a Memory Agent inside Service Intelligence. Each works out of the box without a partner building it. The four agents are a product set, not a library a customer browses, and there is no template gallery. A community driven marketplace of service workflows and first party automations is on Thread's roadmap and not available today. Sourcegetthread.com/blog/magic-agents-a-new-era-of-ai-powered-automation-for-mspsread 2026-09-05 |
|
| Triggers & Channel Coverage | Full |
|
Five channels include the two an MSP desk lives in, and work starts three ways. Agents chat, email and call across chat, email, phone, Microsoft Teams and Slack, and Teams and Slack matter because that is where an MSP's end users raise issues, not a help portal. Thread Voice AI is generally available and automates the phone channel with capture, transcription and automatic ticketing. Work starts inbound, when a client messages or calls, on events, when the Overflow Agent picks up a call that would otherwise reach voicemail and escalates a P1 to the on call team outside hours, and proactively, when the Reminder Agent reaches back out to check whether an open issue is still live and closes the thread if it resolved itself. Traditional phone and email stay fully active alongside. Sourcegetthread.comread 2026-09-05 |
|
| Model Flexibility & Routing | Partial |
|
Two model platforms are in use and Thread chooses between them. Claude runs inside AWS Bedrock for the Triage Agent and Super Magic features, Thread's other AI features run on Microsoft Azure, and these features are being turned on progressively. The platform runs across at least two providers, Anthropic through Bedrock and Azure OpenAI, and has moved a flagship agent from one to the other, but the selection sits with Thread. There is no model selector, routing policy or bring your own key path for customers, and a customer cannot choose which model handles their tickets. Sourcedocs.getthread.com/article/2gttcwtp4a-thread-ai-on-aws-bedrock-anthropic-claude-data-processing-security-triage-agent-super-magicread 2026-09-05 |
|
| APIs, SDKs & MCP Extensibility | Not documented |
|
There is no public API, SDK, webhook reference or MCP endpoint. Partners extend Thread through other platforms, with automation through Rewst, Power Automate and Zapier and full ticket resolution through Pia, so they connect a third party automation tool instead of calling Thread directly. A community driven marketplace of service workflows is on Thread's roadmap and not available today. Sourcegetthread.com/blog/magic-agents-a-new-era-of-ai-powered-automation-for-mspsread 2026-09-05 |
|
| Testing, Debugging & Optimization | Partial |
|
Outcomes are measured and backed by a commercial guarantee, but nothing tests a change before it reaches clients. Thread tracks triage accuracy at 96%, sentiment at 97% positive, resolution rates and hours returned, and backs it with a 60 day positive ROI guarantee or a refund. There is no simulation, staging environment, scenario suite, regression run or scored evaluation of an agent before release, so tuning happens against live client tickets instead of in a sandbox. Sourcegetthread.comread 2026-09-05 |
|
| Browser & Computer Use | Not documented |
|
There is no browser control, hosted session or interface automation. Agents work through integrations, writing into ConnectWise, Autotask and HaloPSA through native connections, handing structured data to Pia to complete PSA and Microsoft 365 actions, and reaching people over chat, email, Teams, Slack and phone. Where an action falls outside those connectors, the path is a third party automation platform such as Rewst, Power Automate or Zapier, not an agent operating a screen. Sourcegetthread.comread 2026-09-05 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Product updates
Voice On-Call is now generally available to all Thread Voice AI customers. A Flow on any ticket condition triggers it to call down an ordered list of technicians until one presses a key to accept, then it adds that technician to the ticket, sets a chosen status and writes every call and acceptance as a ticket note.
Bears on: Agent capability
View sourceThread announced the general availability of Voice AI, introducing a new method for handling phone-based support. The feature brings the platform's speed and automation capabilities to voice channels.
Bears on: Agent capability
View sourceThread released a new integration with Liongard via the Thread MCP. This allows technicians to query Liongard's asset intelligence data directly from Claude or ChatGPT through Thread without needing a separate login.
Bears on: Integrations
View sourcePricing
$34 per license per month (AI Pro)
per license per month; AI ticket credits pooled across break-fix customers
Included quota
AI Pro includes unlimited AI for the licensed customer; each paid license adds three AI ticket credits to a pool for unlicensed customers
What is public
AI Pro at $34 per license, the tier structure, the credit pool mechanic, no multi year contracts, and the sixty day ROI guarantee are all publicly documented on the pricing page.
Billing mechanics
Per managed customer license per month across AI Essentials and AI Pro tiers. Chat is optional. A shared AI ticket credit pool extends AI to smaller break fix customers without a full license.
Cost watchouts
Chat is a paid add on beyond the AI license; unlicensed break fix customers draw on a shared AI ticket credit pool (three credits per paid license) and should convert to a license above three or four tickets per month.
Variable cost rationale
Per license pricing with unlimited AI on the licensed tier keeps cost predictable per managed customer; the main variable is how many customers are licensed versus drawing on the shared credit pool, which the vendor caps and guides toward conversion.
Additional watchouts
The per license model scales with the number of managed customers; the credit pool mechanic requires monitoring to decide when to convert break fix customers to licenses.
Overage / add-ons
Unlicensed customers consume shared AI ticket credits (three per paid license); exceeding three to four tickets per month signals converting them to a paid license, which unlocks unlimited AI and refunds credits to the pool
Sales call required
No, self serve available
Free / trial
No free tier; sixty day positive ROI guarantee or full refund
Lowest paid plan
AI Essentials (price not retrieved); AI Pro at $34 per license
Key ambiguities
No price is shown for AI Essentials or for the chat add on; only AI Pro is priced, at $34 per license.
Missing data
AI Essentials price, chat add on price, enterprise or volume discounts.
Related vendors
- Decagon — AI agent platform purpose-built for customer support, with deep…
- 5.Y — 5
- Ada — Agentic customer experience platform whose AI agents autonomously…
- Aisera — Enterprise agentic AI platform that orchestrates specialized agents…
- ASAPP — Generative AI for enterprise contact centers that plugs into…
- Assembled — AI customer support orchestration platform that unifies autonomous…
Alternatives to Thread
The closest documented capability profiles to Thread among customer support agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Cendra7.5 / 14A lighter documented profile than Thread
- ASAPP11.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- BlueTweak9.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- NICE CXone10.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- Plivo9.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- QueryPal8.5 / 14Fuller documented coverage on Deployment & Data Residency and Prebuilt Agents, Templates & Packs
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded