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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.poly.ai/feedback

```json
{
  "path": "/flows/no-code/quickstart",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Quickstart

> Build your first no-code flow step by step with Default steps and routing.

This walkthrough builds a simple booking flow:

* Collect phone number (or fallback to email)
* Collect booking details
* Route large parties differently
* Finish cleanly

## Step 1 -- Create a flow

1. Go to **Build > Flows**
2. Click **+ Create flow**
3. Name it (example: **Make a booking**)

Start with a Default step as your entry point.

## Step 2 -- Add your first Default step (entry point)

1. Add a **Default step**
2. Name it **Collect contact details**
3. In the **Prompt**, write something like:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Ask for the caller's phone number to create or look up the booking.
If they don't want to provide a phone number, ask for an email address instead.
Confirm what you captured in one sentence.
```

## Step 3 -- Add entities to the step

In **Collect contact details**, add:

* Phone number
* Email address (fallback)

This tells the system what structured information to extract and validate. See [Entities](/flows/no-code/entities) for the full list of entity types.

## Step 4 -- Add routing

After collecting information, add labeled edges such as:

* phone collected
* phone missing
* caller refuses

Keep labels short and explicit.

If you later add a step like **Collect Number of Passengers**, you might branch into:

* Individual Booking
* Group Booking

Clear labels make routing easier to understand and maintain.

## Step 5 -- Add a finish/exit step

1. Add an **Exit flow**
2. Name it **Booking complete**
3. Connect your success branches to it

## Writing good condition labels

Good labels are:

* Short
* Unambiguous
* Business-focused

Examples:

* phone collected
* phone missing
* party size above 15
* requires handoff
* unclear

Avoid vague labels like:

* valid
* ok
* continue

If someone else looks at your flow, they should understand the logic immediately from the labels alone.

## Next steps

<CardGroup cols={3}>
  <Card title="Entities" icon="puzzle-piece" href="/flows/no-code/entities">
    Configure entity types and validation for your flows.
  </Card>

  <Card title="Advanced steps" icon="gear" href="/flows/no-code/advanced-steps">
    ASR biasing, DTMF collection, and rich text references.
  </Card>

  <Card title="Flows overview" icon="diagram-project" href="/flows/introduction">
    Understand how flows work and when to use them.
  </Card>
</CardGroup>