> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/crm/crm-initial-settings/crm-maximum-time-alert-color.md).

# CRM - Maximum Time (Alert Color)

To make it easier to view inactive deals, the CRM allows you to configure alert colors on opportunity cards. These colors appear according to the **maximum time defined**, helping you quickly identify when a deal has been idle for a long time.

You can:

* Set the **alert color**.
* Choose the **maximum inactivity time**.
* Add **more than one color** to create different levels of attention.

#### How to set up

1. Access the **CRM**.

<figure><img src="/files/8d73f9d9608f43cb76535a2fc3dac70d7a00a92c" alt=""><figcaption></figcaption></figure>

2. Go to **Settings** → **Pipeline List**. In the desired pipeline, click Settings.

<figure><img src="/files/0495f31bff81e42c918b8089f6ee9fd33fef4c2f" alt=""><figcaption></figcaption></figure>

3. In the stage, click **Edit**.

<figure><img src="/files/ed0cf5faa848aadd7008d7405ada185bce9eaf6c" alt=""><figcaption></figcaption></figure>

4. Set the **color** and the **maximum inactivity time.**

<figure><img src="/files/10dc2be59308d6ab0663c52922583862e19eb311" alt=""><figcaption></figcaption></figure>

You can add more colors in maximum time by clicking "Add Maximum Time":

<figure><img src="/files/9719ed383c05a1e4b5f404980afce2cd0a60abd7" alt=""><figcaption></figcaption></figure>

5. Click **Save** when editing the stage and also click **Save** when editing the pipeline

Done! Now your cards will automatically show the alert colors according to the time of each opportunity.

🎥 Check out the video below for the full step-by-step on how to configure:

{% embed url="<https://youtu.be/i6gQ4uzLXlw>" %}


---

# 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://docs.sprinthub.com/en/topics/general/crm/crm-initial-settings/crm-maximum-time-alert-color.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.