> 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-learn-how-to-edit-and-add-stages-in-the-sales-funnel.md).
# CRM: Learn How to Edit and Add Stages in the Sales Funnel
Keeping the stages of your CRM pipeline well organized and up to date is essential to ensure that the sales process accurately reflects the journey of your leads and customers. Over time, it is common to need to adjust stage names, add new phases, or adapt the pipeline to the current reality of the business. In this video, you will learn, step by step, how to edit the stages of an already created pipeline, whether to rename an existing stage or create new stages, in a practical way and without compromising the opportunity history. +
💡 Let's get straight to the point so you can keep your CRM always aligned with your sales strategy.
Check out the tutorial below:
{% embed url="" %}
---
# 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-learn-how-to-edit-and-add-stages-in-the-sales-funnel.md?ask=&goal=
```
`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.