> For the complete documentation index, see [llms.txt](https://docs.3dolphins.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3dolphins.ai/analytic/sales/deal-lost.md).

# Deal Lost

See instantly the count or value of your company's lost deals based on the users. So, you can improve the sales strategies to increase sales of your product. In addition, you can see your data by **'Value'** or **'Count'** based on the filter selected. Hovering the cursor to each user will display the number of deals lost or lost value. 

To view the report, go to the **Analytic** menu and click the **Sales** menus, then click **Deal Lost** which you can find in the sales performance section.

![Deal Lost](/files/CLqYb4YE7HZt8tzbkyMZ)

The Bar Chart above explains:

1. The Y-axis represents users with a sales role.
2. The X-axis represents the number of deals or the total value depending on which metric is selected (count/value).
3. Deals lost represents the number of lost deal
4. Value of lost deal represents the total value of lost deal.

In addition to bar charts, this report also contains detailed table information of all deals lost that occurs on that pipeline. The following is an explanation of the table information:

| Name                   | Description                                          |
| ---------------------- | ---------------------------------------------------- |
| User                   | Your sales agent name.                               |
| Deals Won              | The number of deals lost at that stage.              |
| Value of Won Deals     | The total value of deals lost at that stage          |
| Average Won Deal Value | The average total value of deals lost at that stage. |


---

# 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.3dolphins.ai/analytic/sales/deal-lost.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.