> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revdesk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Launch your first workflow

> A seven-step path from a new workspace to a tested RevDesk workflow.

# Launch your first workflow

The best first launch is narrow enough to test and important enough to matter. Pick one audience, one outcome, and a clear point where a person should step in.

<Steps>
  <Step title="Set up your workspace">
    Add the business name, locations, teammates, working hours, and the people who should receive handoffs.
  </Step>

  <Step title="Choose the outcome">
    Decide what completed work means. This might be a routed call, qualified lead, booked appointment,
    reactivated customer, or updated opportunity.
  </Step>

  <Step title="Connect the source of work">
    Choose where eligible records arrive from, such as Deal Operations, a supported CRM, a form, an approved
    list, or an integration.
  </Step>

  <Step title="Set up the channels">
    Configure the phone and messaging channels the workflow may use. Complete any required number
    registration, consent, and sender setup before launch.
  </Step>

  <Step title="Define the coworker boundaries">
    Set the audience, goal, allowed actions, schedule, maximum follow-up, approval points, and human
    escalation path.
  </Step>

  <Step title="Test the complete path">
    Use a test record to verify the opening conversation, reply handling, booking or routing, record update,
    opt-out behavior, and handoff context.
  </Step>

  <Step title="Review the recommendation and launch">
    RevDesk can recommend a launch shape after the systems, audience, and rules are known. Review the
    recommendation, confirm ownership, then start with a controlled audience.
  </Step>
</Steps>

## A launch is ready when

* Every eligible record has one source and one owner.
* The coworker has a specific outcome and a defined stopping point.
* Approved channels, working hours, consent rules, and opt-outs are configured.
* A person knows where handoffs arrive and what response time is expected.
* The correct stage, activity, appointment, owner, and next step update in Deal Operations or a verified integration.
* Managers know where to review work, outcomes, and exceptions.

<CardGroup cols={2}>
  <Card title="Test your setup" icon="flask" href="/getting-started/setup/testing">
    Verify the full customer and teammate experience before launch.
  </Card>

  <Card title="Understand coworkers" icon="sparkles" href="/concepts/coworkers">
    Learn how coworkers receive work, act, stop, and hand off.
  </Card>
</CardGroup>