> 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/sales-insights/explore-customer-insights/review-a-customer-profile/explore-top-products.md).

# Explore top products

{% hint style="info" %}
**Early access:** This feature is available to participating Sales Insights customers.
{% endhint %}

A **Top Products** opportunity highlights popular products across your business that the customer hasn't bought in the last 12 months. Use these opportunities to find gaps in the customer's product range and prepare talking points, even when the customer has only bought from you once. Use your knowledge of their needs to decide which products are relevant.

In **Opportunities**, select **Top Products** to view this opportunity type.

### Understand the rankings

There are three rankings, each covering the last 12 months:

| Ranking     | What determines popularity                       |
| ----------- | ------------------------------------------------ |
| By customer | The number of customers who bought each product. |
| By quantity | The total quantity sold of each product.         |
| By revenue  | The total revenue from each product.             |

Each ranking can highlight different products.

### Review product gaps

The opportunity heading shows the number of gaps in the top 10 products. A *gap* is a product the customer hasn't bought in the last 12 months. The bought indicator shows how many products in that initial list they have bought.

![Top products opportunity overview](https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FIwlWjNcnifZUaUPDnQ7D%2Ftop-products-overview.png?alt=media)

Expand an opportunity to see:

* The ranked products, including products the customer has already bought.
* A check mark beside each product the customer bought in the last 12 months. These products appear dimmed so you can distinguish them from gaps.
* **Share of your customers** in the customer-based ranking. This is the percentage of customers who bought the product in the last 12 months. It describes past purchases, not the likelihood that this customer will buy the product.

![Expanded Top products opportunity](https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FqYwgtByAC6Bxz7pZaLzB%2Ftop-products-analytics.png?alt=media)

For example, **4 of 10 bought** means the customer bought 4 of the top 10 products in the last 12 months. The remaining 6 are possible talking points. The customer might have bought them before that period.

Select **More** to see the top 25 products, or **Less** to return to the top 10.

### Explore in Analytics <a href="#explore-in-flex-modes" id="explore-in-flex-modes"></a>

Select **Open in Analytics** to explore the top products in [Analytics](https://docs.phocassoftware.com/analytics/). All the top products are shown in the grid.

Top products opportunities don't have an estimated annual value and don't contribute to **Potential upside**. Use them to identify products to discuss with the customer.


---

# 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/sales-insights/explore-customer-insights/review-a-customer-profile/explore-top-products.md?ask=<question>&goal=<user_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.
