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

# Find recurring problems and review outcomes

> Connect repeated customer issues to actions your team can take.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Connect repeated customer issues to actions your team can take. Where to find it: Analytics → Recurring problems, Daily briefings and Outcomes

## Before you start

* Permission to read the relevant analytics and conversation evidence.

## Steps

<Steps>
  <Step>
    Open Recurring problems and select the period and scope you want to investigate.
  </Step>

  <Step>
    Inspect a group’s supporting conversations before deciding that they share the same cause.
  </Step>

  <Step>
    Assign follow-up work, improve a knowledge article or create a ticket for a confirmed problem.
  </Step>

  <Step>
    Review Daily briefings for the permitted summary of current issues and open the evidence for anything important.
  </Step>

  <Step>
    Use Outcomes to check whether the change improved customer results over a comparable period.
  </Step>
</Steps>

## Example

Repeated password-reset questions lead to clearer help content and a product fix if the reset flow is actually broken.

## Things to know

* A grouped problem is a lead for investigation, not proof of a common root cause.
* Briefing availability depends on your reporting permissions and eligible data.

## What happens next

<Check>
  A trend leads to an evidence-based action rather than an assumption based only on a summary.
</Check>

## If something goes wrong

<Warning>
  * No groups or briefing: check time range, accessible evidence and the specific availability message.
  * Unexpected trend: inspect the underlying conversations and compare the same filters.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Find missing answers and improve your help centre" href="/stackshift-support/knowledge-insights">
    Use feedback and unanswered questions to decide what to write next.
  </Card>

  <Card title="Create and follow a ticket" href="/stackshift-support/tickets">
    Track requests that need structured information and a clear lifecycle.
  </Card>
</CardGroup>


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