Thread Docs bronze
docs.getthread.com
we checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 23 Nov 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI use policy
-
What this site's
robots.txtsays about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents. - AI-facing documents
-
Publishes
/llms.txt— “Thread Docs” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 2 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Cloudflare, Inc. (AS13335)
- Last checked
- 2d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of docs.getthread.com controls every word below.
Admin onboarding
Use when an admin, owner, or project lead is standing Thread up for their MSP and wants to know the order of work — "how do I roll out Thread", "what do I do first / next", "we just signed, where do we begin", "how do I onboard my team", "what's left before we go live", "how long does onboarding take", "AI Service Unleashed". Covers the ten staged groups of the onboarding path from workspace creation through Voice AI and leadership review, what each stage delivers, and what has to be true before moving on. This is the setup journey, distinct from the per-role enablement paths.
By role
Use when the answer depends on who the reader is, or when they ask for a tour or a starting point — "which agents or skills should I use", "where do I start", "how do I get my team going", "what should my dispatchers know", "I'm a technician / dispatcher / service manager / CSM / owner". Covers all eight role paths (Technician, Dispatcher, Service & Ops Manager, CSM / Account Manager, Security & Compliance Owner, Sales & Business Development, MSP Owner / Leadership, Automation Engineer), what each role cares about, and the lesson order for a guided tour. Ask which role the reader holds before recommending a path, then walk it with them.
Contact support & feedback
Use when the user needs a human, can't find an answer, hits an error/outage, or wants to request a feature or give feedback. Covers all the ways to reach the Thread Help team (help center, in-app chat from Admin, email) and how to submit feedback and feature requests. Trigger on "contact support", "talk to a human", "how do I get help", "report a bug", "something is broken", "this isn't in the docs", "submit feedback", "request a feature", "feature request".
Getting started
Use for newcomer and orientation questions — what Thread is, its core products, how to begin, creating a workspace, the onboarding path, and role-based starting points. Covers the Thread overview (Inbox, Messenger, Assistive AI, Magic Agents, Voice AI, Client/Contact Intelligence), supported PSAs and channels, and where each role should start. Trigger on "what is Thread", "getting started", "how do I begin", "set up / create my workspace", "onboarding", "I'm new", "where do I start", "what can Thread do", "guides for my role".
Magic Library
Use for any question about picking or running a prebuilt job from Thread's Magic Library — "which agent or skill should I use", "is there something for offboarding / phishing / stale tickets", "what's the difference between an agent and a skill", "how do I run a skill", "how do I make it run automatically", "what does Verified mean", "how do I browse the library", "can I contribute one". Covers the agent-versus-skill distinction, the three places a job can run (Super Magic, Thread MCP, a Flow), how to narrow the catalog by category, connector, role and outcome, and how to go from reading an entry to running it.
PSA Integrations
Use for questions about connecting Thread to a PSA — ConnectWise, Autotask, or HaloPSA — and how ticket/data sync works. Covers setting up each PSA integration, creating the required API user, ConnectWise permission requirements, HaloPSA setup and troubleshooting, keeping members in sync with the PSA, and how Thread talks to a PSA via webhooks/APIs. Trigger on "connect my PSA", "ConnectWise integration", "Autotask integration", "HaloPSA / Halo integration", "API user", "PSA sync", "tickets not syncing", "webhooks", "member sync", "which PSAs does Thread support".
Security and compliance
Use for any question about Thread's security posture, certifications, or compliance status — SOC 2, SOC 2 Type II, ISO 27001, GDPR, HIPAA, BAA, DPA, sub-processors, penetration tests, encryption, data residency, tenant isolation, audit logging, the Trust Center, or answering a client security questionnaire / vendor DDQ. Trigger on "are you SOC 2", "what is your SOC 2 status", "do you have SOC 2", "SOC2", "certification", "attestation", "compliance", "trust center", "ISO 27001", "HIPAA", "BAA", "DPA", "GDPR", "sub-processors", "pen test", "security questionnaire", "is Thread secure", "where is my data stored", "encryption at rest".
Super Magic
Use for questions about Super Magic — Thread's in-Inbox AI assistant. Covers what it is, where to find it, what it can do (find/create/update tickets, log time, add notes, search KB/IT Glue/Hudu/web, scheduling, devices via NinjaOne/ImmyBot), the read-freely / confirm-before-acting safety model, connectors and skills, example prompts, admin setup and access, and limits. Trigger on "Super Magic", "the Magic button", "AI assistant in the Inbox", "ask Super Magic to…", "can Super Magic do X", "reboot a device from Super Magic", "Super Magic connectors", "Thread MCP".
Thread History & Founders
Use for questions about Thread's origin story, founders, and company history — who founded Thread, when it started, the original name, how it became Thread, and how it grew into an AI service desk. Trigger on "who founded Thread", "who are the founders", "Mark Alayev", "Matt Linn", "when was Thread founded", "history of Thread", "was Thread always called Thread", "Chatgenie", "how did Thread start", "Thread's story", "why is it called Thread".
Voice AI
Use for questions about Thread Voice AI — the AI phone agent that answers calls, gathers details, maps callers to the right contact/company in the PSA, and creates or updates tickets. Covers creating a first Voice AI agent, overflow & after-hours answering, the Auto-Attendant (phone-menu replacement), on-call escalation, outbound calling, SIP trunks & caller ID, Voice Shield, pronunciation, and the Voice AI FAQ. Trigger on "Voice AI", "phone agent", "answer calls", "after-hours calls", "overflow", "auto attendant", "IVR replacement", "outbound calling", "SIP trunk", "caller id", "Voice Shield".
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Thread Docs — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://docs.getthread.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.