> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/crm/analysis.md).
# CRM analysis
Analyze your CRM data in the Analytics module to correlate activities to results.
{% hint style="info" %}
User permission: CRM
The CRM analysis database in only available in the **desktop version** of CRM.
{% endhint %}
The CRM analysis database opens in the [Analytics module](https://docs.phocassoftware.com/analytics/). If you have permission, it appears on your homepage with other databases and in the **Analytics** menu.
The CRM analysis database is often tailored to suit individual businesses. You might need to contact your administrator to gain access to the CRM database. See [Databases](/basics/dashboards/use-dashboards.md) to learn more.
A standard CRM analysis database is similar to any other database in Phocas, but instead of seeing value, profit or quantities, you see the number of activities for accounts, contacts and leads.
Typically, full details can be viewed using [Transaction mode](/analytics/customize-your-view-analytics/change-the-mode/transaction-mode.md), where you can change the properties as required.
Example: Find accounts that have had no activity over the last 12 months
1. Open the CRM analysis database.
2. Select a period and a dimension, such **Rolling 12 Months** and **Campaign**.
3. Change the activity filter to **No Activity**. All campaigns with no recorded activity display in the grid, highlighted in green. Example: Create a dashboard that compares Sales Activity to Sales Value
First, [create a new dashboard](https://docs.phocassoftware.com/basics/dashboards/create-a-dashboard) called **Sales vs Activity in the last three months***.* After you select **Save**, a new blank dashboard opens.
Next, create an activity bar chart using data from the CRM analysis database:
1. On the new dashboard, select **Add widget** > **Query**. The widget configuration screen has a database selection on the top-right and widget settings on the left. The Phocas grid appears inside the screen and operates as usual.
2. In the top-right, select the CRM database.
3. Select a period (this example uses Last 3 months).
4. Select **Mode** > **Total**.
5. Select the **Chart** button.
6. Select the Column chart and enter a name for the chart (in this example the name is Activity last 3 months).
7. Select **Save**. The chart displays on the dashboard.
Next, create a sales value chart using data from the Sales database.
1. On the new dashboard, select **Add widget** > **Query**.
2. Select the Sales database.
3. Select a period (match it to the period used in the activity chart).
4. Select **Mode** > **Total**.
5. Click the **Chart** button.
6. Select the Column chart, enter a name for the chart (in this example the name is Sales last three months) and place it on the same line as the previous chart (in this example, Line 0).
7. Click **Save**. The chart displays on the dashboard.
Now you can view your dashboard. The charts sit side by side so you can compare sales activity with sales value for the same period. In this example, the link between activity and sales is not clear. Activity levels are about the same across the three months, but sales values vary a lot. This would be something to follow up with the sales team.
{% embed url="" %}
The CRM analysis dashboard
{% endembed %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.phocassoftware.com/crm/analysis.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
