> For the complete documentation index, see [llms.txt](https://closingdealz.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://closingdealz.gitbook.io/product-docs/features/analytics/sale-log.md).

# Sale Log

### **Overview**

The **Sale Log** in **ClosingDealz** provides a structured record of all **closed and lost deals**, offering insight into revenue generation and deal performance. It enables sales teams to **analyze outcomes, track financial progress, and optimize their sales strategy** based on past results.

With **search, filtering, and detailed deal summaries**, the Sale Log ensures complete transparency over all finalized deals.

***

### **Key Features**

* **Closed vs. Lost Deals** – Quickly differentiate between **closed (green)** and **lost (red)** deals.
* **Total Revenue & Loss Tracking** – See the sum of **won deals** and the potential value of **lost deals**.
* **Search & Filters** – Easily find specific deals using search and status or date filters.
* **Deal Summary View** – Click on any deal to access a detailed breakdown of its history, contacts, and notes.

***

### **Sale Log Table Breakdown**

The Sale Log presents data in a structured table, including the following details:

| Column          | Description                                 |
| --------------- | ------------------------------------------- |
| **Title**       | The deal name.                              |
| **Company**     | The company associated with the deal.       |
| **Price**       | The deal value in USD.                      |
| **Assigned To** | The salesperson responsible for the deal.   |
| **Status**      | Whether the deal is **Closed** or **Lost**. |
| **Date Closed** | The timestamp when the deal was finalized.  |

Users can **sort and filter** data to analyze sales trends effectively.

***

### **Deal Summary & Details**

Clicking on a deal opens the **Deal Summary** panel, providing additional details:

**1. General Deal Information**

* **Deal Title** – Name of the deal.
* **Deal Price** – The finalized deal amount.
* **Loss Reason** – If applicable, the reason why a deal was lost.
* **Deal Notes** – Additional notes related to the deal.
* **Close Confidence** – The likelihood of deal closure at different stages.

**2. Contacts**

* View all contacts associated with the deal.

**3. Lead Details**

* Company name, industry, employee count, and lead origin.

**4. Deal History**

* Tracks key updates, such as **deal creation, status changes, and stage movements** over time.

***

### **How to Use the Sale Log**

1. **Filter by Date & Status** – Select a time range and deal type (**Closed or Lost**).
2. **Search for Specific Deals** – Use the search bar to find deals by name or company.
3. **Review Financial Performance** – Compare closed revenue vs. lost deal value.
4. **Analyze Individual Deals** – Click any deal to view its full history and details.

***

### **Why Use the Sale Log?**

* **Track Sales Outcomes** – Monitor deal closures and identify patterns in lost deals.
* **Measure Revenue Impact** – Assess how much revenue is gained vs. lost.
* **Improve Deal Management** – Use deal history insights to refine sales strategies.

The **Sale Log** ensures that every finalized deal contributes to **business growth, performance tracking, and continuous sales improvement**.


---

# 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:

```
GET https://closingdealz.gitbook.io/product-docs/features/analytics/sale-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.