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

# Catch bugs early

> Spot suspected product bugs in customer conversations as they appear.

Rippit reads every conversation for signs that something is broken, so bugs surface from the first customers who hit them, not after the tenth escalation.

## Ask Rippit

```text wrap theme={null}
In the last 7 days, which conversations describe something in the product not working as it should? Group them into distinct issues, tell me how many customers hit each, and whether it's new this week.
```

To answer, Rippit can:

* Recognize a bug report even when the customer and the agent treated it as a how-to question.
* Group reports of the same problem into one issue, with the steps and details customers gave.
* Look up the matching issue in [Linear](/agentic-chat/connectors/linear) or [Jira](/agentic-chat/connectors/jira-confluence), when connected, and show which bugs are already tracked.

Ask Rippit for conversation links under each issue, so engineering gets the customer's own report rather than a summary.

To get suspected bugs every day without asking, turn the question into an [Agent App](/plg/agent-apps) that posts them to Slack for triage.

<CardGroup cols={2}>
  <Card title="Ask Rippit questions" icon="comments" href="/plg/chat/asking-questions" />

  <Card title="Deploy Agent Apps" icon="robot" href="/plg/agent-apps" />
</CardGroup>