> 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-closing-reasons.md).

# Set up closing reasons

You use closing reasons in the final phase of your funnel.

This lets you record why a deal is won or lost.

{% hint style="warning" %}
Closing reasons only work in a lead phase with the type **Closing phase**.
{% endhint %}

### Create a closing reason

{% stepper %}
{% step %}

### Open CRM settings

Go to **Settings**.

Open **CRM** or search for **Closing reasons**.
{% endstep %}

{% step %}

### Add a closing reason

Open the overview.

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

{% step %}

### Fill in the reason

Use a unique **Code**.

Enter a clear **Description**.
{% endstep %}

{% step %}

### Save

The closing reason is now available in your closing phase.
{% endstep %}
{% endstepper %}

### Common closing reasons

* **Win**
* **Loss**
* **Competitor**

### Frequently asked questions

<details>

<summary>Why do I not see my closing reasons?</summary>

Check whether the lead is in a **Closing phase**.

</details>

<details>

<summary>Can I add more closing reasons later?</summary>

Yes. You can always expand the list.

</details>

<details>

<summary>Is there a limit?</summary>

No. Keep the list practical and easy to manage.

</details>

### Related articles

* [Set up lead phases](/marketplace-packages-and-power-ups/power-ups/crm+/set-up-lead-phases.md)
* [Work with customers and leads in CRM+](/marketplace-packages-and-power-ups/power-ups/crm+/work-with-customers-and-leads-in-crm+.md)
* [Use the CRM overview page](/marketplace-packages-and-power-ups/power-ups/crm+/use-the-crm-overview-page.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-closing-reasons.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.