> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thread.app/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Thread?

> Thread is the customer success platform built around workflows. Trigger from your CRM, draft handovers, run kickoff, customize plans per account, and give customers a portal that's actually useful.

Thread is the customer success platform built around **workflows**. Wire your CRM, calls and documents into one place, and Thread orchestrates everything that happens after a deal closes — handover briefs drafted from the actual sales calls, success plans tailored to the customer, the right CSM assigned by rule, kickoff scheduled, and a customer portal that mirrors the plan in real time.

<Frame>
  <img src="https://mintcdn.com/threadsolutionsinc/MFTGqD087bXZP0ze/images/screenshots/introduction/accounts-home.png?fit=max&auto=format&n=MFTGqD087bXZP0ze&q=85&s=55cf67f631a606fb7646b04cf4d9bb48" alt="Thread accounts dashboard showing 38 active onboardings with status, ARR, progress, and assigned CSM for each" width="2560" height="1560" data-path="images/screenshots/introduction/accounts-home.png" />
</Frame>

## What you build with Thread

<CardGroup cols={2}>
  <Card title="Customer handover" icon="handshake" href="/use-cases/customer-handover">
    AE → CSM briefs auto-drafted from CRM context and call transcripts, with the questions you actually want answered.
  </Card>

  <Card title="Success plans" icon="map" href="/use-cases/success-plans">
    Phased plans with owners, milestones and dates — customizable per account, mirrored to the customer portal.
  </Card>

  <Card title="CSM assignment" icon="user-plus" href="/use-cases/csm-assignment">
    Route accounts by ARR, region, segment or any field — round-robin, least-loaded, or named owner.
  </Card>

  <Card title="Statement of Work analysis" icon="file-magnifying-glass" href="/use-cases/sow-analysis">
    Compare every signed SOW against your standard. Surface deviations, custom commitments and risk before kickoff.
  </Card>

  <Card title="Customer kickoff & onboarding" icon="rocket" href="/use-cases/kickoff-onboarding">
    Turn a closed deal into a live customer on a measurable timeline. First-value, not first-meeting.
  </Card>

  <Card title="Customer portal experience" icon="window" href="/use-cases/customer-portal-experience">
    Branded, customer-facing portal that's the source of truth for the plan and what's next.
  </Card>
</CardGroup>

## How it works

Thread sits between your CRM and your customer experience. One workflow drives the journey from "deal closes" to "customer is live."

### 1. A deal closes in your CRM

Connect Salesforce, HubSpot or any of the other [integrations](/integrations/overview) and Thread reacts the moment a stage changes. No copying data, no manual upload — the trigger fires, the workflow runs.

<Frame>
  <img src="https://mintcdn.com/threadsolutionsinc/MFTGqD087bXZP0ze/images/screenshots/integrations/salesforce-connected.png?fit=max&auto=format&n=MFTGqD087bXZP0ze&q=85&s=fb5956bd94db34a8d9eb5f3288aaed3a" alt="Connectors page in Thread with Salesforce, Slack, Gong and Google Workspace connected" width="2560" height="1436" data-path="images/screenshots/integrations/salesforce-connected.png" />
</Frame>

### 2. The workflow runs

Each workflow is a chain of nodes: triggers, branches, AI drafts, human reviews, action sends, integrations. Drop them on a canvas and Thread handles the choreography.

<Frame>
  <img src="https://mintcdn.com/threadsolutionsinc/MFTGqD087bXZP0ze/images/screenshots/integrations/salesforce-workflow.png?fit=max&auto=format&n=MFTGqD087bXZP0ze&q=85&s=d6f0bbc021750740355556f339d13802" alt="Workflow builder with a Salesforce trigger flowing through Branch, Handover brief, Route to CSM and Apply success plan nodes" width="2560" height="1508" data-path="images/screenshots/integrations/salesforce-workflow.png" />
</Frame>

### 3. The handover lands ready to review

The brief is drafted from the CRM payload, linked Gong calls and any uploaded SOW — every answer cites its sources. The AE reviews, edits, submits. The CSM lands on an account that already knows the answers.

<Frame>
  <img src="https://mintcdn.com/threadsolutionsinc/MFTGqD087bXZP0ze/images/screenshots/use-cases/customer-handover.png?fit=max&auto=format&n=MFTGqD087bXZP0ze&q=85&s=e7411bd36adf3d7d5c08b9c9b76155de" alt="Handover brief with AI-drafted answers to What did the customer buy and why, Who are the stakeholders, and What's at risk — each citing the sales calls and CRM notes that informed it" width="2560" height="1718" data-path="images/screenshots/use-cases/customer-handover.png" />
</Frame>

### 4. Onboarding kicks off — for both sides

The CSM sees the success plan in their workspace. The customer sees a branded portal — same plan, same milestones, same actions, mirrored in real time.

<CardGroup cols={2}>
  <Card title="Internal kickoff view" icon="window-maximize" href="/use-cases/kickoff-onboarding">
    The stepper, what's next, and the action queue.
  </Card>

  <Card title="Customer portal" icon="window-restore" href="/use-cases/customer-portal-experience">
    What your customer sees of the same plan.
  </Card>
</CardGroup>

<Frame>
  <img src="https://mintcdn.com/threadsolutionsinc/MFTGqD087bXZP0ze/images/screenshots/use-cases/customer-portal-experience.png?fit=max&auto=format&n=MFTGqD087bXZP0ze&q=85&s=a194db85c5d8cf80d6a927d59fc6b95f" alt="Customer-facing portal showing the kickoff stepper, three actions waiting on the customer, and the assigned team contacts" width="2560" height="1342" data-path="images/screenshots/use-cases/customer-portal-experience.png" />
</Frame>

## Connects to your stack

Thread reads from your CRM, your call recordings and your collaboration tools — and writes back to Slack, email, calendars and your services PSA when a workflow tells it to.

| Tool                                                   | What Thread does                                                         |
| ------------------------------------------------------ | ------------------------------------------------------------------------ |
| **[Salesforce](/integrations/salesforce)**             | Trigger workflows from opportunity stage changes; pull rich CRM context. |
| **[HubSpot](/integrations/hubspot)**                   | Trigger workflows from deal stages; sync companies and contacts.         |
| **[Gong](/integrations/gong)**                         | Pipe call transcripts and insights into briefs, plans and SOW analysis.  |
| **[Slack](/integrations/slack)**                       | Post updates to shared channels, alert CSMs, broadcast handovers.        |
| **[Kantata](/integrations/kantata)**                   | Spin up services projects with role-based resourcing.                    |
| **[Notion](/integrations/notion)**                     | Use Notion databases as a trigger source.                                |
| **[Google Workspace](/integrations/google-workspace)** | Send branded email, create docs, schedule kickoff meetings.              |
| **[Microsoft](/integrations/microsoft)**               | Calendar and email through Microsoft 365 / Teams.                        |
| **[Zoom](/integrations/zoom)**                         | Schedule and track customer calls.                                       |

## Get started

<CardGroup cols={2}>
  <Card title="Quick start" icon="rocket" href="/introduction/getting-started">
    Up and running in 10 minutes — connect a CRM, build your first workflow.
  </Card>

  <Card title="Key concepts" icon="book" href="/introduction/key-concepts">
    Templates, workflows, milestones, actions — the vocabulary in 5 minutes.
  </Card>

  <Card title="Use cases" icon="lightbulb" href="/use-cases/customer-handover">
    Walk-throughs of the six experiences Thread is built around.
  </Card>

  <Card title="Integrations" icon="plug" href="/integrations/overview">
    Connect Thread to the tools your team already uses.
  </Card>
</CardGroup>
