The pieces
Guides
Resident agents, one per account, each with its own memory and a single outcome it pursues across text, email, and voice.
Motions
Staged programs that hold the goal, the context, and the milestone criteria for accounts moving through a lifecycle.
Workflows
The routing layer: reads each account’s state and sends it down the right path.
Inbox
The one place everything needing a human lands — approvals, exceptions, customer replies, wins.
Customer portal
A white-labeled, passwordless portal where your customers see where they are, what’s next, and what’s needed from them.
Integrations
CRM, warehouse, and collaboration connectors — the systems Thread reads to verify outcomes and acts through to do the work.
What makes Thread different
Verification is the product. A guide can’t mark its own homework. An outcome closes one of two ways: a fresh read from a connected source (your CRM, your warehouse, your product telemetry) confirms it, or a human on your team explicitly confirms it. “The customer says it’s connected” is a lead, not a close. See Outcomes and verification. Humans hold the controls. Every phone call is proposed to a person before it’s placed. Approvals land in your Inbox with the whole story. Agents that draft outbound work can run in “Needs your OK” mode per action, and everything an agent does — every send, every source check — lands in a certified log you can read. Compliance is enforced in the runtime, not a settings page. Consent before the first text, quiet hours in the recipient’s timezone, STOP honored instantly and across channels, AI disclosure on voice. See Compliance.Where to start
- To drive one customer to one outcome over real channels, start with a guide: Quickstart: your first guide.
- To run accounts through a staged program with milestones and plays, start with a Motion: Quickstart: your first Motion.
- Not sure which fits? How Thread works explains how the pieces compose.
Authoring surfaces — Guides, Voice Studio, Motions, Agent Templates, and Workflows — are available to
org admins. Every member of your org gets the Inbox, Accounts, and Studio. See
User management.
