> 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-how-to-configure.md). # CRM - How to configure The SprintHub CRM allows you to organize opportunities, track negotiations, and have a clear view of the entire sales process, from the first contact to closing. In this article, you will learn **how to access the CRM, create a pipeline, and configure all the steps needed to use it day to day**. *** {% embed url="" %} *** ### How to access the CRM in SprintHub You can access the CRM area in two ways: * Through the menu: **Menu >> General >> CRM** * Or by typing **CRM** in the field **Find services** When you access it, you will see the pipelines and registered opportunities. *** ### What is a CRM pipeline in SprintHub The CRM pipeline visually represents the **stages of your sales process**, allowing you to track which phase each opportunity is in. Examples of common stages: * New lead * Contact made * Proposal sent * In negotiation * Won * Lost Each company can adapt the pipeline to its own reality. *** ### How to create a CRM pipeline 1. Access **Menu >> General >> CRM** 2. Go to the **CRM pipelines** 3. Click on **Create pipeline** 4. Enter: * **Pipeline name** (e.g.: Sales Pipeline, WhatsApp Sales, After-sales) * **Description** (optional) 5. Save the information Once created, the pipeline will be available for use in opportunities. *** ### How to create and configure pipeline stages The stages define the negotiation flow within the pipeline and can be fully customized. 1. Inside the created pipeline, click **Add stage** 2. Configure the following fields: * **Stage name**: phase identification (e.g.: Proposal sent) * **Stage color**: used to make the pipeline easier to view * **Maximum time in stage (optional)**: defines how long the opportunity can remain in this phase * **Expected closing time (optional)**: closing forecast from this stage onward * **Card sorting**: defines how opportunities will be organized within the stage * **Automatic movement**: choose whether the opportunity will be moved automatically to this stage based on messages or contact interactions 3. Save the stage 4. Repeat the process until you build the entire pipeline flow 💡 Tip: always correctly configure the stages of **won** and **lost** to keep CRM reports and indicators accurate. *** ### How to create an opportunity in the CRM 1. Access the CRM 2. Click on **New opportunity** 3. Select: * The **CRM pipeline** * The **initial stage** 4. Link a **contact** or create a new one 5. Fill in the opportunity fields 6. Save From there, you can move the opportunity between stages as the negotiation progresses. *** ### Moving opportunities in the pipeline Opportunities can be moved: * Manually, by dragging them between stages * Automatically, via **automations**, according to contact actions This ensures more agility and standardization in the sales process. *** ### CRM screens and features The SprintHub CRM is divided into screens and settings that make sales management and opportunity tracking easier. #### Main CRM screens * **Dashboard**: overview with indicators, opportunity volume, pipeline status, and team performance. * **Funnel**: view of opportunities by stage, allowing manual or automatic movement of cards. * **Automations**: automatic rules for creating, moving, and updating opportunities according to contact actions. * **Campaign Planner**: allows you to relate sales campaigns to the CRM, organizing actions by pipeline stage. * **Approvals**: control of opportunities that require approval before advancing in the pipeline or being completed. *** ### CRM settings In the settings area, it is possible to fully customize how the CRM works according to the company's process. #### Pipeline list Displays all pipelines registered in the system, allowing you to create, edit, or remove pipelines as needed. *** #### Reasons (won or lost) Allows you to configure the reasons used when an opportunity is marked as **won** or **lost**. This information is used in reports and performance analysis. *** #### Blocks Defines blocking rules in the CRM, preventing improper movements or unauthorized changes in certain stages or situations. *** #### Custom fields Allows you to create additional fields for opportunities, such as: * Product or service type * Negotiated value * Expected closing date * Opportunity source These fields help enrich the information and generate more complete reports. *** ### Filters in the CRM The CRM includes filters that make it easier to search and organize opportunities, making tracking faster and more efficient. #### Available filters * **Status**: allows you to filter open, won, or lost opportunities. * **Responsible party**: shows only opportunities assigned to a specific user. * **Creation date**: filters opportunities based on the date they were created. * **Expected closing date**: ideal for tracking closing forecasts over a specific period. * **Advanced filters**: allow more detailed combinations, including custom criteria and multiple conditions. *** ### Search in the CRM In addition to filters, the CRM also includes quick search to find specific opportunities. #### Search options * **By contact data**: name, phone, email, or other information linked to the contact. * **Opportunity title**: direct search by the opportunity name or identifier. These options speed up navigation and make daily pipeline management easier. *** ### Best practices for using the SprintHub CRM * Keep pipelines simple and objective * Update opportunities regularly * Use standardized win and loss reasons * Set up blocks to avoid operational errors * Use automations to gain scale and standardization --- # 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-how-to-configure.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.