> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/crm+/set-up-lead-phases.md).

# Set up lead phases

Lead phases are the steps in your sales funnel.

Each phase belongs to one account type.

### Phase types

Every funnel uses three phase types.

#### Qualification / Initial phase

This is the start of your sales process.

Use it for the first contact with a new lead.

This can be a first phone call or an introductory meeting.

Every funnel starts here.

Example: **Call appointment**

#### Regular phase

These are the steps between first contact and the final decision.

You can create as many regular phases as you need.

Use them for the work that moves a lead forward.

This can be a meeting, a calculation, or a quote.

Examples:

* **Meeting**
* **Calculation**
* **Send Quote**

#### Closing phase

This is the final step in your funnel.

It marks the end of the sales process.

When a lead reaches a closing phase, you can choose a closing reason.

For example, use **Won**, **Lost**, or **Competitor**.

Only a closing phase lets you record why a deal was won or lost.

Example: **Closed**

{% hint style="warning" %}
Create at least one lead phase with the type **Closing phase**.

Without it, you cannot select closing reasons on the customer card.
{% endhint %}

### Create a lead phase

{% stepper %}
{% step %}

### Open CRM settings

Go to **Settings**.

Open **CRM** or search for **Lead phases**.
{% endstep %}

{% step %}

### Add a lead phase

Open the overview.

Click **Add**.
{% endstep %}

{% step %}

### Fill in the phase

Use a unique **Code**.

Enter a clear **Description**.

Choose the correct **Phase type**.
{% endstep %}

{% step %}

### Set the order

Use **Order number** for the funnel sequence.

Then link the correct **Account type**.
{% endstep %}

{% step %}

### Save

Repeat this for each phase in your process.
{% endstep %}
{% endstepper %}

### Example of a simple funnel

* **Call appointment**
* **Send Quote**
* **Closed**

### Frequently asked questions

<details>

<summary>Can one lead phase belong to multiple account types?</summary>

No. Each lead phase belongs to one account type.

</details>

<details>

<summary>Where do I see the lead phases?</summary>

In the **Overview** tab on the customer card.

</details>

<details>

<summary>Do I need to use all phase types?</summary>

Use one **Qualification / Initial phase** at the start.

Add as many **Regular phases** as your process needs.

Always include at least one **Closing phase**.

</details>

### Related articles

* [Set up account types](/marketplace-packages-and-power-ups/power-ups/crm+/set-up-account-types.md)
* [Set up closing reasons](/marketplace-packages-and-power-ups/power-ups/crm+/set-up-closing-reasons.md)
* [Work with customers and leads in CRM+](/marketplace-packages-and-power-ups/power-ups/crm+/work-with-customers-and-leads-in-crm+.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/crm+/set-up-lead-phases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.