> 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-tutorial-videos/crm-triggering-flows-on-lost-opportunities.md).

# CRM - Triggering Flows on Lost Opportunities

Losing an opportunity in the sales funnel does not mean the end of the relationship with the customer — on the contrary, it can be the starting point for strategic actions that reactivate this contact at the right time. Automating this process is essential to ensure agility, consistency, and maximum use of sales history. 

💡 In this video, you will learn how to create a simple and effective automation: whenever an opportunity is marked as "Lost", a flow will be automatically triggered, allowing you to send targeted communications, nurture this lead, or even regain their interest later. 

It is a smart way to keep your funnel active and your conversion chances always alive.\
\
Check out the tutorial below: 

{% embed url="<https://www.youtube.com/watch?v=PztOIuJrLME>" %}

<br>


---

# 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-tutorial-videos/crm-triggering-flows-on-lost-opportunities.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.