> 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/sprinthub-app/crm/how-to-create-an-opportunity-in-the-crm-using-the-mobile-app.md).

# How to Create an Opportunity in the CRM Using the Mobile App

{% embed url="<https://youtube.com/shorts/8rGBuD7j0Yw>" %}

#### Step by Step to Create an Opportunity in the CRM

1. Access the CRM through the app on your phone.
2. In the top right corner, click the “+” icon to add a new opportunity.
3. Fill in the essential information:

* Select the Lead related to the opportunity.
* Set the opportunity title.
* Choose the funnel stage where the opportunity is located.
* Assign a person responsible for the opportunity.
* Enter the opportunity value.

4\. After filling in all required fields, click “Save”.<br>

Conclusion

Done! Your new opportunity is now registered in the CRM and available for tracking. This feature makes the process faster and allows your team to manage leads and opportunities from anywhere.

<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/sprinthub-app/crm/how-to-create-an-opportunity-in-the-crm-using-the-mobile-app.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.