Skip to main content
This walkthrough builds a Motion — a versioned, staged program — and runs one account through it. You’ll need an org admin role; Motions live under Operate → Motions.
1

Connect your CRM

Motions work best fed by real account data. Connect Salesforce or HubSpot under Connectors so accounts, deal context, and verification reads are live. See Integrations.
2

Draft the Motion

Two paths: build it by hand, or let Build your Motion draft it from your own material — upload your onboarding docs, point it at a Notion page or URL, add notes — and it generates stages with timelines, milestones tagged for automatic or manual verification, and draft agents per stage. Everything lands as a draft; nothing runs until you publish. See Build your Motion.
3

Shape stages and milestones

Each stage owns its plays and its milestones. A milestone is a plain-English customer outcome — “the location is taking payments” — confirmed either by an agent reading connected systems or by a human marking it. Mark the ones that gate stage advance as required. See Milestones and verification.
4

Review the plays

Plays are mostly agents: they draft emails, chase documents, watch for stalls. Set each action’s autonomy — Already sent (autonomous) or Needs your OK (approval first). Email plays have a full editor with attachments from Studio and AI prompt slots filled at send time. See Agents in Motions and Email plays.
5

Publish and assign

Publish the Motion and assign an account. The account pins to the version it entered on — later edits to the Motion never silently change accounts mid-flight.
6

Work your Inbox

Drafts needing your OK, escalations, and proposed stage advances land in the Inbox. When a stage’s required milestones confirm, Thread proposes the advance — a person always makes the call.

​
Going bigger