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

# Quickstart: your first Motion

> Build a staged program with milestones and plays, assign an account, and approve its first work.

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

<Steps>
  <Step title="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](/integrations/overview).
  </Step>

  <Step title="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](/motions/build-your-motion).
  </Step>

  <Step title="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](/motions/milestones-and-verification).
  </Step>

  <Step title="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](/studio/overview) and AI prompt slots filled at send
    time. See [Agents in Motions](/motions/agents) and [Email plays](/motions/email-plays).
  </Step>

  <Step title="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.
  </Step>

  <Step title="Work your Inbox">
    Drafts needing your OK, escalations, and proposed stage advances land in the
    [Inbox](/inbox/overview). When a stage's required milestones confirm, Thread proposes the advance
    — a person always makes the call.
  </Step>
</Steps>

## Going bigger

* Route accounts into the right Motion automatically: [Workflows](/workflows/overview)
* Put a resident guide on individual accounts: [Quickstart: your first guide](/introduction/quickstart-guide)
* See what your customers experience: [Customer portal](/customer-portal/overview)