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

# Groups

> Organize issues into smart, reusable buckets to monitor what matters most

## What are Groups?

Groups let you define high-level buckets of issues you care about (for example, “Payment failures” or “Login not loading”). Once created, Decipher will automatically find matching sessions and keep these groups up to date.

* **Why use groups**:
  * **Persistent monitoring**: Keep a continuous watch on a category of problems.
  * **Shareable context**: Give your team one place to track a problem area and its impact.
  * **Actionable views**: Filter alerts, funnels, and metrics around a specific theme.

## How to create a Group

1. Go to All Issues → Groups → New Group
2. Fill in the form:
   * **Group name**: A clear title (e.g., “Payment failures after Pay Now click”)
   * **Error type**: Choose the type that best fits: Error, Loading Issue, or Rage Click
   * **URL matching**: Track all URLs or limit to specific paths (e.g., `/checkout`)
   * **Issue matching method**:
     * Contains: simple substring match in error text (only for Error type)
     * AI-powered: semantic matching using your description
   * **Issue description**: Plain-English description of what should match
3. Click Create Group

<Tip>
  Start broad, then narrow URL filters or wording if you see unrelated matches. Use <b>Contains</b> when you know the exact error phrase; use <b>AI-powered</b> for conceptual matching.
</Tip>

<Tabs>
  <Tab title="AI-powered">
    Use when the problem can be described in natural language. Decipher will semantically match your description to sessions.

    <Info>
      Works best with specific, verifiable details (page, action, UI pattern, message).
    </Info>
  </Tab>

  <Tab title="Contains">
    Use when you know an exact error phrase (e.g., <code>"Client Side Exception"</code>). Only available for the Error type.

    <Note>
      Use precise, stable phrases to avoid unrelated matches.
    </Note>
  </Tab>
</Tabs>

## Testing groups before creating

Use Test Group to preview how your definition performs before saving.

* **What happens when you test**:
  * We find similar collections for your org based on your inputs
  * Up to the first 100 are analyzed for matches
  * You’ll see results in three buckets:
    * Matched
    * Rejected
    * To be analyzed (includes skipped beyond the first 100)

If results look off, tweak the description, URL filters, or matching method and test again.

<Info>
  During testing, only the first 100 similar collections are analyzed; the rest are shown as <b>Skipped</b> so you can quickly iterate on your definition.
</Info>

## What makes a good prompt (AI-powered)

Write a short, specific description that an AI could verify against a session.

<AccordionGroup>
  <Accordion title="Be specific">
    * “Users click Pay now and see ‘Payment failed’ message”
    * “Loading spinner never disappears after login submit”
  </Accordion>

  <Accordion title="Include context when relevant">
    * Feature or page (e.g., “Bank Accounts page”)
    * UI pattern (e.g., “modal error”, “banner warning”)
  </Accordion>

  <Accordion title="Avoid vague wording">
    * “Stuff breaks”
    * “Seems slow sometimes”
  </Accordion>
</AccordionGroup>

<CardGroup>
  <Card title="Good example 1" icon="check">
    “User clicks Pay now and sees a error modal with an error code that prevents from paymenting.”
  </Card>

  <Card title="Good example 2" icon="check">
    “Login page fails to load and shows a full-page error 'client side exception' instead of the form.”
  </Card>

  <Card title="Good example 3" icon="check">
    “User has an issue with the delete button with no response from the UI.”
  </Card>
</CardGroup>

Once saved, Decipher continuously matches new sessions to your group so your team can monitor, triage, and share progress from one place.

## Alerts for Groups

Get notified when a group you care about has activity.

<Steps>
  <Step title="Create a new alert">
    Go to <b>Alerts</b> and click <b>Create alert</b>. Give it a clear name (e.g., "Payment failures – daily summary").
  </Step>

  <Step title="Add a Group condition">
    Click <b>Add Condition</b> → choose <b>Group</b> → select the group you want to monitor.
  </Step>

  <Step title="Choose where to notify">
    At the bottom, select <b>via email</b>, <b>via Slack</b>, or both. Add email recipients and/or pick Slack channel(s).
  </Step>

  <Step title="Set summary frequency">
    Pick how often you want email summaries (e.g., Daily). Frequency is enabled once at least one email is added.
  </Step>

  <Step title="Save the alert">
    Click <b>Save Alert</b>. You can edit or disable it any time from the Alerts page.
  </Step>
</Steps>

<Note>
  Email summary frequency appears after you add at least one email recipient.
</Note>