> 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-dashboard-and-reports.md). # CRM - Dashboard and Reports The **Reports** and **Dashboards** The CRM reports and dashboards allow you to track results, analyze sales performance, and make strategic decisions based on real data. Each view has specific objectives and its own criteria for displaying information. Understanding these criteria and the **available filters** is essential to ensure accurate analyses {% embed url="" %} *** ### 1. Global Filters and Period Selection Before starting any analysis, use the top control bar to segment the displayed data: * Period Filter: Allows isolating the history (e.g., current month, quarter, or custom periods). * Pipeline Filter: If your company works with multiple pipelines (e.g., Pre-sales, Enterprise Sales, Aesthetics), you can select which one you want to analyze separately. * User Filter: Segments the view to analyze the performance of a specific salesperson or team. *** ### 2. Macro-System Indicators (Global Metrics) The top row of cards shows the consolidated result of the operation for the selected period: * Conversion Rate: The exact percentage of opportunities closed as "Won" out of the total opportunities worked. * Average Ticket: The average financial amount transacted per completed sales opportunity. * Sales Funnel (Opportunity Status): Shows the volume and financial flow divided among opportunities *Created, Opened, Won, and Lost*. *** ### 3. Operations Panel and At-Risk Opportunities This quadrant acts as the manager's preventive alert system, signaling where the sales team is losing traction or speed: | **Risk Alert** | **Technical Description** | **Impact on the Pipeline** | | ----------------------- | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | No messages for +3 days | Open opportunities that have not received any contact interaction in the last 3 days. | High risk of the lead going cold due to lack of follow-up. | | No edits for +15 days | Negotiations that have had no stage changes or data edits for more than 2 weeks. | Indicates stagnation in the negotiation process. | | Stagnant for +30 days | Opportunities that have been stalled with no progress at any stage for more than a month. | Artificially inflates the funnel and needs to be discarded or have a break-contact email sent. | Alongside, the panel shows operational control cards for Meetings, Tasks, Customer Service, and Calls that help monitor the daily activities required of consultants. *** ### 4. Performance Rankings and Win/Loss Analysis #### Salesperson Ranking Displays the ranking table of sales consultants ordered by Total Won Value. The table details crucial individual metrics such as: * Number of wins; * Average ticket per salesperson; * Individual conversion rate; * Sales Cycle (Win vs. Loss): The average time (in days) it takes the salesperson to move an opportunity to the end of the sales process. #### Chart: Ticket vs. Conversion A multidimensional quadrant chart that crosses the *Conversion Rate (%)* on the vertical axis with the *Average Ticket (R$)* on the horizontal axis. It is used to instantly identify the team's high-performance profile (salespeople who sustain high conversion with high ticket values). #### Analysis of Loss and Win Reasons Statistical tables that point out the main factors of success and failure in negotiations: * Loss Reasons: Classifies the biggest bottlenecks in the product or process (e.g.: *"Closed with the competitor"*, *"High price"*), showing the total financial amount that failed to enter cash flow. * Win Reasons: Identifies which sales triggers or campaigns (e.g.: *"I offered a 10% discount"*) are generating the most revenue. *** ### 5. Distribution and Time Analysis * Opportunities by Time (Open / Lost / Won): Bar charts that segment lead age (e.g., 31 to 60 days, over 150 days). Ideal for forecasting the time needed for a lead to mature before the sale. * Distribution by Value Range: Shows which price range contains the largest volume of opportunities in your company, separating transactional-volume sales from sales *Enterprise*. * Average Ticket by Source: Maps which channel, campaign, or digital media the most financially profitable opportunities are coming from. *** #### 📧 Automatic Report Delivery by Email The CRM allows you to configure **automatic report delivery by email**, ensuring that managers and teams receive updated data without needing to access the system. **🔄 How it works** Reports can be: * Automatically generated * Sent at defined intervals (daily, weekly, monthly, or custom) * Shared with specific users
**🎯 Benefits of automatic delivery** * Operational time savings * Continuous tracking of results * Standardization of analyses * Greater agility in decision-making --- # 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-dashboard-and-reports.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.