> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer Insights report

> Track the product problems customers raise in sessions, then assign, research, resolve, archive, merge or export each insight from one report.

Customer Insights turns the product problems customers describe in their sessions into insights: short, general statements of one problem, each with a count of the sessions that raised it. Use it to see which issues come up most often, hand them to the right team, and follow them until they are fixed.

> [!NOTE]
>
> **Reports & Apps → Customer Insights** in your [OpenCX dashboard](https://platform.open.cx/reports/voice-of-customer). Opening it requires **Reports: Read** and **Voice of Customer: Read** in [Settings → Roles](https://platform.open.cx/settings/roles). Assigning, resolving, archiving, merging, commenting, deep research, exports and the **Settings** button require **Voice of Customer: Write**.

## Add Customer Insights to the sidebar

The **Reports & Apps** section shows only the Impact Dashboard until someone pins more reports. A member with **Helpdesk settings: Write** selects **Add** under the pinned reports, then **Customer Insights**. Pins apply to everyone in your organization. See [Reports overview](https://docs.open.cx/reports/overview.md) for arranging the section.

Without a pin, the report is still available at the link above to anyone with both permissions.

## How insights are created

OpenCX analyzes two kinds of sessions:

* **Handed-off sessions**, on any channel. Analysis starts when the session is handed off to your team.
* **Phone and web calls the AI resolved.** A call is analyzed once it has had no new messages for 15 minutes.

Text sessions the AI resolves on its own are not analyzed. A session that contains only internal notes is skipped.

Each analysis keeps only clear, high-confidence findings, at most two per session. When a finding closely matches an existing insight in the same category, OpenCX adds the session to that insight and raises its **Events** count instead of creating a new one. New insights get a category and a sentiment, and can arrive already assigned to one of your [teams](https://docs.open.cx/teams.md), picked from team names and descriptions.

> [accordion] What counts as an insight
>
> An insight is a problem or limitation of your product that the customer states directly, written as a general statement in English with personal details removed.
>
> These are left out:
>
> * Billing, pricing and account-specific requests
> * One-off problems tied to a single order, transfer or account
> * Issues solved during the session, and questions that were fully answered
> * Nice-to-have features and personal preferences
> * Complaints about the support experience, response times or the AI assistant
>
> A general product question that stayed unanswered is filed under the **Knowledge Gap** category. To steer what counts for your business, add [AI instructions](https://docs.open.cx/reports/customer-insights-settings.md#write-ai-instructions).

## Find the insights that matter

The list shows each insight with its number, status (**Unresolved**, **Resolved** or **Archived**), sentiment, category, **Events** (sessions linked to it) and **Team**. It is sorted by occurrences, highest first.

Type in the search box to match insight text. Select the sparkle button to switch to natural language search, type a request such as "show unresolved insights" and press Enter; OpenCX turns it into filters you can see and remove.

Select **Filters** to narrow the list:

| Filter | What it narrows |
| - | - |
| Category, Assigned team | Insights in one category, or assigned to one team (or **Not assigned**) |
| Status | **Resolved** or **Archived** only. With neither selected, all insights show |
| Insight sentiment | **Happy**, **Neutral** or **Angry** |
| Insight number, Minimum occurrences | One insight by number, or insights with at least this many sessions |
| Ticket date range, Session channel, Session language | Insights with sessions created in that range, on that channel or in that language |
| Session custom data, Contact custom data | Insights with sessions matching your custom data. These can slow the list |
| Sort by, Sort order | **Occurrences**, **Last Seen**, **First Seen** or **Created Date**, descending or ascending |

> [!NOTE]
>
> Session-based filters (date range, channel, language and custom data) also change the **Events** count: it counts only the matching sessions. The insight panel then shows the same subset, with **Show all** to see every linked session.

## Work on an insight

Select an insight to open its panel. It shows when the insight was created and last seen, its **Category** (select it to change), **Related Sessions** with a chart of sessions over time, **Deep Research Agent**, **Activity**, discussion and **Similar insights** (up to five in the same category, with a match percentage). Each related session opens in the inbox.

**Activity** records every change and who made it. Automatic changes show as **System**.

> [accordion] Assign a team
>
> Select the avatar in the **Team** column (**N/A** when unassigned) and choose a team, or **No team** to clear it. Every member of the team except you gets a notification. Insights are assigned to teams, not to individual people.

> [accordion] Resolve or reopen
>
> Select **Resolve** when the problem is fixed, or **Reopen** to undo. If a new session reports the same problem later, the insight reopens on its own and **Activity** shows "reopened after a new occurrence".

> [accordion] Archive
>
> Select **Archive**, choose when the insight can come back, add a reason, then select **Archive**. Archived insights keep counting new sessions.
>
> | Option | When it comes back |
> | - | - |
> | It escalates | 5 new sessions within 7 days |
> | 10 occurrences | 10 new sessions, at any time |
> | Forever | Never. A reason is required |
>
> When the threshold is reached, the insight returns to the list as **Unresolved** and **Activity** shows "escalated this archived insight". The panel shows progress toward the threshold. Select **Unarchive** to bring it back yourself.

> [accordion] Merge duplicates
>
> 1. Open one of the duplicates and select **Merge**.
> 2. While **Merge Mode Active** shows, select the other insight in the list. Use search or the **Insight number** filter to find it.
> 3. In **Merge Insights**, choose the primary insight. The one with more sessions is preselected.
> 4. Select **Merge Insights**.
>
> Sessions and discussion move to the primary, counts combine, and the other insight leaves the list. A merge cannot be undone.

## Run deep research

Under **Deep Research Agent**, select **Generate Report**. OpenCX writes a report in English on the problem across the 50 most recent related sessions, with links to the sessions it cites. It runs in the background; when it finishes, you get a "Your deep research report is ready" notification and the report appears in the panel.

Each insight has one report. If generation fails, you can start it again. Deep research does not run on archived insights.

## Discuss with your team

Add comments in the panel, reply in threads and react with emoji. Type **@** to mention a teammate; they get a notification. Everyone who has commented in a thread is notified of new replies.

## Export to CSV

* **All insights:** select **Export**, then **Generate new export**. The file includes the insights that match your current filters, with category, content, sentiment, status, team, occurrence count, dates and who resolved or archived each one.
* **One insight's sessions:** in **Related Sessions**, select **Export Sessions**. The file lists every linked session with its channel, status, contact name, email and phone, summary and team.

You get a notification when the file is ready; open the same menu and select **Download CSV**. Turn on desktop alerts for deep research, exports and team assignments in [Settings → Notifications](https://platform.open.cx/settings/notifications).

## Example: from first report to fix

1. **Detected.** A customer tells an agent that the order confirmation page shows an error after paying with a gift card. The session is handed off, and OpenCX creates insight #57 under **Bug** with **Negative** sentiment. Matching sessions over the next days raise its **Events** count to 14.
2. **Assigned.** A support lead sorts by occurrences, opens #57 and assigns it to the Payments team. Each Payments member is notified.
3. **Researched.** A Payments agent selects **Generate Report**, reads the report when the notification arrives, and @mentions the engineer who owns checkout.
4. **Resolved.** After the fix ships, the agent selects **Resolve**. If a new session reports the same error, #57 reopens on its own.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| Customer Insights is missing from the sidebar | It is not pinned, or you lack a permission | Pin it (needs **Helpdesk settings: Write**), and check you have **Reports: Read** and **Voice of Customer: Read** |
| No **Settings** button, or an action fails | You have **Voice of Customer: Read** only | Ask an admin for **Voice of Customer: Write** |
| A session you expected is not linked to any insight | The AI resolved it on a text channel, or nothing in it met the bar for an insight | Only handed-off sessions and AI-resolved calls are analyzed |
| **Generate Report** confirms the start, but no report appears | The insight is archived | Unarchive it, then select **Generate Report** again |

***

## Related Documentation

> [card] [Customer Insights settings](https://docs.open.cx/reports/customer-insights-settings.md)
>
> Categories and AI instructions

> [card] [Reports overview](https://docs.open.cx/reports/overview.md)
>
> Reports & Apps and pinning

> [card] [Roles](https://docs.open.cx/security/roles.md)
>
> Grant report permissions

> [card] [Customer Insights API](https://docs.open.cx/api-reference/customer-insights/index.md)
>
> Insights over the API


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.