Motions · private preview
A Motion is how you put guides on the whole customer lifecycle, not just one conversation. It holds the goal, the context, and the exit criteria at every stage, engages the right guide at the right moment, and only closes an outcome when a fresh read of your system says it happened. Done, earned, never claimed.
private preview · running with design partners today
Illustrative Motion. Guides stack per stage, the harness engages each at the right moment, and humans approve the calls. No stage exits on a say-so; the close is the read.
What a Motion is
You break the lifecycle into stages and write the exit criteria in terms your systems can answer. The Motion does the rest.
Closing, onboarding, first value, expansion, each stage exits on facts a system can confirm: deal closed-won in the CRM, integrations live, usage rows fresh. Criteria are reads, not opinions.
The Motion carries the goal and the full account context across every stage. Nothing is re-gathered at a handoff, and nobody rebuilds the plan from a call recording. Context moves with the account.
Guides work their plays inside each stage, kickoff, document chase, stuck detection, the quiet-week call. The Motion engages the right one at the right moment. Agents do the work; the harness keeps them honest.
A stage exits and an outcome closes only on a fresh read of your record. "The customer says it's set up" is a lead, not a close.
Inside a Motion
The moment a deal closes, the Motion pulls what the AE knew, CRM fields, call notes, the contract, into a brief the guide starts from. The first message to the customer already knows the use case, the stakeholders, and what was promised.
No handoff gap, no re-asking questions the customer already answered.
Every Motion reports itself: time to value against the baseline you set when you launched it, verified outcomes closed, and where accounts are stalling. The numbers come from the same system reads that close the stages.
The report and the verification are the same read, there's no separate dashboard to reconcile.
Text, email, and voice land in one thread per account, with one memory. Your team supervises the guides from a single workspace and steps in where a human converts better.
Humans in the loop
Approval gates. You decide which moves wait for sign-off, by action type, stage, or account tier. The guide drafts, a human approves, and the approval sits in the log next to the send.
Every dial asks first. Phone calls are part of the floor: a guide never dials without a human saying go. That rule is enforced in the runtime, not in a settings page.
Escalations with the whole story. When a guide is stuck, or an account needs a person, it pages your team with the full context and its last read of the record, not a ticket number.
Every step in the log. Each action is recorded with the context the guide had and the output it produced. Replay any decision; audit any close.
Proof
A national point-of-sale platform runs this motion on merchant activation today.
anonymized · every close verified in their warehouse
A 190,000-merchant payments processor runs it on merchant data onboarding.
anonymized · done means the record landed, present and correct
Questions
Motions is the harness inside Thread. It runs on the same platform, reads the same connected systems, and drives the same guides, you don't choose between them.
Workflow rules are if-this-then-that. A Motion holds a goal and lets guides pick the next step from the account's actual state. And stages exit on reads of your systems, a fresh record, not a completed send.
Yes. A Motion reads the systems you connect, CRM, warehouse, product telemetry, to ground the guides and to check exit criteria. It stays within the permissions you set, and every read is logged.
A platform fee plus $1.25 per verified outcome. The 30-day pilot is priced per verified outcome only, see pricing.
Motions is in private preview, running with a small set of design partners. Book a 30-day pilot and we'll run your first Motion on a real cohort.
Start here