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

# Investigate product behavior

> Review meaningful changes in product use and, when available, compare them with related customer feedback.

Use **Behavior** to investigate changes detected in product activity. Some reports combine usage changes with negative customer feedback, helping you validate whether what customers say matches what they do.

## Prerequisites

* A supported product analytics source is connected
* ClosedLoop AI has enough activity to produce a behavior report

<Steps>
  <Step title="Choose a review queue">
    Open **Behavior**, then choose **Active**, **Critical**, **Warning**, **Opportunity**, or **All**. Start with Critical when you need the highest-risk changes first.
  </Step>

  <Step title="Narrow the results">
    Search across the customer name, headline, or detail. Then choose a time range and sort order that fit the investigation.
  </Step>

  <Step title="Inspect the report">
    Open an item and review **Reports** for the observed change, affected usage, and recommended next check. If the report includes customer feedback, validate both the activity change and the feedback evidence.
  </Step>

  <Step title="Check how it was detected">
    Open **Detector** to understand the rule behind the report. Use **Activity** to review its status history.
  </Step>

  <Step title="Continue the investigation">
    Use **Insights** or **Context** to investigate related customer evidence. If you need recurring monitoring, create the Watch from a filtered view there.
  </Step>
</Steps>

## Verification

You should be able to describe the detected change, the evidence behind it, and which customer or product scope it affects.

<Warning>Resolve and Dismiss actions in Behavior do not create a workspace-wide shared review record. Use Inbox or Roadmap when the team needs durable follow-through.</Warning>

## Troubleshooting

* **Behavior is empty:** Confirm that a supported analytics source is connected and importing data.
* **A report lacks customer feedback:** Not every detector combines both evidence types. Validate the usage change on its own, then search **Insights** separately.
* **You cannot create a Watch:** Watches are currently created from filtered **Insights** or **Context** views.

## Related

* [Find and validate product evidence](/docs/guides/find-product-evidence)
* [Monitor a topic with a Watch](/docs/guides/watches-and-inbox)