> ## 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.

# Glossary

> Key terms and definitions used throughout Thread

## Thread Terminology

A comprehensive glossary of terms used in Thread. Terms are organized alphabetically for easy reference.

***

## A

### Account

A customer organization being onboarded through Thread. Accounts contain contacts, milestones, actions, and all related onboarding data.

**Related:** [Creating Accounts](/csm-guide/accounts/creating-accounts)

### Account Executive (AE)

The sales team member who closed the deal and initiates the handoff to Customer Success. AEs complete handoff forms to transfer customer context to CSMs.

**Related:** [Handoff Process](/csm-guide/accounts/handoff-process)

### Action

A discrete task or communication within an onboarding milestone. Actions have types (email, meeting, form, etc.), triggers, and completion criteria.

**Types:** SEND\_EMAIL, REQUEST\_DOCS, COLLECT\_INFO, REQUEST\_ASSETS, SCHEDULE\_MEETING, SLACK

**Related:** [Action Types Reference](/reference/action-types)

### Action Instance

A specific occurrence of an action for a particular account. When a template is applied, action definitions become action instances with their own status and data.

### Admin

A user role with full organizational permissions including user management, template creation, workflow building, and connector configuration.

**Contrast with:** User (CSM)

### Approval Node

A workflow node that pauses execution until a designated person approves or rejects. Used for manager sign-off or quality gates.

**Related:** [Building Workflows](/csm-guide/workflows/building-workflows)

### ARR (Annual Recurring Revenue)

The annualized value of a customer's subscription, used for segmentation and routing decisions in workflows.

***

## B

### Blocker

An action marked as required for milestone completion. Blockers prevent milestone progress until completed.

**Configuration:** Set in action's `customer_portal.blocker` setting

### Broadcast

A feature for sending bulk Slack messages to multiple customer channels simultaneously. Used for announcements and updates.

**Related:** [Broadcast](/admin-guide/broadcast)

***

## C

### Condition Node

A workflow node that routes execution based on data conditions. Supports comparisons like equals, greater than, contains, etc.

**Related:** [Building Workflows](/csm-guide/workflows/building-workflows)

### Connector

An integration with an external service (Slack, Google, HubSpot, etc.). Connectors enable automated triggers and actions.

**Related:** [Integrations Overview](/integrations/overview)

### CSM (Customer Success Manager)

The primary user of Thread. CSMs manage customer onboarding, review AI-generated content, and ensure successful implementations.

### CSM Assignment Node

A workflow node that assigns a CSM to an account, either from a specific queue or directly to a named individual.

### Customer Portal

The customer-facing interface where contacts complete actions, upload documents, fill forms, and track onboarding progress.

**Related:** [Portal Overview](/customer-portal/overview)

***

## D

### Delay Node

A workflow node that pauses execution for a specified duration (hours or days) before continuing to the next node.

### Draft

The initial state of generated content (emails, forms) before CSM review and approval. AI generates drafts that CSMs can edit.

***

## E

### End Node

A workflow node that terminates a workflow path. Workflows can have multiple end nodes for different outcomes (completed, rejected, etc.).

### Executable Action

An action type that can be programmatically executed through Thread (SEND\_EMAIL, REQUEST\_DOCS, COLLECT\_INFO, REQUEST\_ASSETS). Non-executable actions require manual completion.

***

## F

### Form Field

An input element within a COLLECT\_INFO action. Types include text, textarea, select, multi\_select, checkbox, date, email, phone, and number.

***

## G

### Generator

A component that creates initial draft content for actions using AI. Generators use template configuration and account context to produce personalized content.

***

## H

### Handoff

The process of transferring customer context from Sales (AE) to Customer Success (CSM). Includes structured questions about goals, risks, and requirements.

**Related:** [Handoff Process](/csm-guide/accounts/handoff-process)

### Handoff Form

A structured questionnaire completed by AEs during handoff. Questions are configured by admins and can be pre-filled by AI.

**Related:** [Handoff Configuration](/admin-guide/handoff-configuration)

### Handoff Template

A collection of questions used during the sales-to-CS handoff. Organizations can have multiple templates for different scenarios.

***

## I

### Implementation Tab

The main interface where CSMs manage account onboarding, review actions, and track progress.

**Related:** [Implementation Tab](/csm-guide/accounts/implementation-tab)

### Integration

A connection to an external service that enables data sync, triggers, or actions. See Connector.

***

## L

### LLM Transform Node

A workflow node that uses AI to process, transform, or extract information from data. Used for normalizing CRM data or generating content.

***

## M

### Magic Link

A one-time authentication link sent to customers for portal access. Eliminates password management for occasional users.

### Manual Upload

The process of bulk-importing accounts via JSON/CSV with AI-powered data normalization.

**Related:** [Manual Upload](/admin-guide/manual-upload)

### Milestone

A phase or stage within an onboarding template. Milestones contain related actions and have sequential or parallel completion requirements.

**Related:** [Milestones and Phases](/csm-guide/templates/milestones-and-phases)

***

## N

### Node

A single step in a workflow. Nodes are connected to define execution flow. Types include Start, End, Condition, Queue, Approval, and various action nodes.

**Related:** [Building Workflows](/csm-guide/workflows/building-workflows)

***

## O

### Organization

A Thread customer account (your company). Contains users, templates, workflows, connectors, and customer accounts.

***

## P

### Phase

See Milestone. Terms are used interchangeably in Thread.

### Pipeline

In CRM context, a series of stages that deals/opportunities move through. Thread can trigger workflows based on pipeline stage changes.

### Portal

See Customer Portal.

### Primary Contact

The main customer contact for an account. Receives portal invitations and is the default recipient for communications.

***

## Q

### Queue

A holding area for workflow tasks requiring human action. CSMs process queue items from the Queue Dashboard.

**Related:** [Queues](/csm-guide/workflows/queues)

### Queue Dashboard

The interface where CSMs view and process pending workflow tasks, approvals, and assignments.

### Queue Node

A workflow node that pauses execution and creates a task for human processing. The workflow resumes when the task is completed.

***

## R

### RLS (Row-Level Security)

Database security ensuring users only access data within their organization. Enforced at the database layer.

### Run

A single execution of a workflow. Runs have states (pending, running, completed, failed, paused) and can be monitored in the workflow interface.

**Related:** [Running Workflows](/csm-guide/workflows/running-workflows)

***

## S

### Scheduled Action

An action with a delay trigger that executes at a future time. Managed by a background job system.

**Related:** [Scheduled Actions](/csm-guide/automation/scheduled-actions)

### Start Node

The entry point of a workflow. Configures the trigger source (CRM events, manual, API).

### Switch Node

A workflow node that routes to multiple paths based on a value. Similar to a programming switch statement.

***

## T

### Template

A reusable onboarding blueprint containing milestones and actions. Applied to accounts to create their implementation plan.

**Related:** [Creating Templates](/csm-guide/templates/creating-templates)

### Template Revision

A versioned snapshot of a template. When templates are applied to accounts, the revision is locked to ensure consistency.

### Trigger

The condition that activates an action or workflow. Types include milestone\_start, manual, CRM events, and time-based delays.

### Triage Node

A workflow node for initial account assessment. Routes accounts based on characteristics like size, industry, or deal value.

***

## U

### User

A Thread team member. Users have either Admin or User (CSM) roles determining their permissions.

**Related:** [User Management](/admin-guide/user-management)

***

## V

### Variable

A placeholder in templates that gets replaced with actual values. Format: `{{variable_name}}`. Common variables include company\_name, contact\_name, csm\_name.

### Vault

Supabase's secure storage for sensitive data like API tokens and credentials. Used for connector authentication.

***

## W

### Webhook

An HTTP callback triggered by external events. Thread receives webhooks from CRMs and integrations to trigger workflows.

### Workflow

An automated process that orchestrates account onboarding. Workflows use nodes to define logic, routing, and actions.

**Related:** [Workflows Overview](/csm-guide/workflows/overview)

### Workflow Builder

The visual interface for creating and editing workflows. Uses a canvas with draggable nodes and connections.

**Related:** [Building Workflows](/csm-guide/workflows/building-workflows)

***

## Acronym Reference

| Acronym | Full Term                        |
| ------- | -------------------------------- |
| AE      | Account Executive                |
| ARR     | Annual Recurring Revenue         |
| CSM     | Customer Success Manager         |
| CRM     | Customer Relationship Management |
| LLM     | Large Language Model             |
| QBR     | Quarterly Business Review        |
| RLS     | Row-Level Security               |
| SSO     | Single Sign-On                   |

***

## Need Help?

<CardGroup cols={2}>
  <Card title="FAQ" icon="circle-question" href="/reference/faq">
    Common questions and answers
  </Card>

  <Card title="Support" icon="envelope" href="mailto:team@thread.app">
    Contact our support team
  </Card>
</CardGroup>
