Skip to main content
Thread puts a resident AI agent — a guide — on every customer account you’ve already sold, to finish the job selling started: complete the onboarding, land the rollout, activate the add-on. A guide texts, emails, and calls with a professional’s patience, brings your team in when a human is what works, and closes an outcome only when a fresh read of your own system of record confirms it happened. Thread is built for the gap between sold and live: the installed base that bought but never activated, the rollout that stalled at store 40 of 200, the onboarding that goes quiet in week two.

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

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.