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

# Signals

> Turn customer conversations into grouped evidence about bugs, requests, friction, and emerging operational issues.

Signals help you see what customers are experiencing across the conversations handled by your support operation. CraftCX detects meaningful observations in individual conversations, then groups related observations into recurring customer problems and needs.

This preserves the insight that support teams often develop by reading tickets every day: a new bug appearing after a release, repeated requests for the same capability, a confusing workflow, or a gap in your documentation.

[Open Signals in CraftCX](https://app.craftcx.com/signals).

## What CraftCX detects

Each signal has one type:

| Type                  | What it captures                                                     |
| --------------------- | -------------------------------------------------------------------- |
| **Bug report**        | A customer describing behavior that appears broken or incorrect      |
| **Feature request**   | A request for a new capability or an improvement to an existing one  |
| **Documentation gap** | Missing, unclear, or hard-to-find guidance                           |
| **Usability issue**   | Friction or confusion caused by a workflow or interface              |
| **Billing issue**     | Problems with charges, plans, invoices, or payment workflows         |
| **Incident signal**   | Activity that may point to a broader service or operational incident |

A single conversation can produce more than one signal. For example, a customer asking how to export data might reveal both a feature request for self-service exports and a documentation gap around the current process. CraftCX keeps those observations separate so each underlying need remains clear.

## Signal groups

The **Signals** tab groups related observations into persistent themes. Each group represents one specific customer problem or desired outcome and includes:

* A title and summary of the recurring theme
* Its signal type, lifecycle, and trend
* Conversation volume for the last 30 days and overall
* Change compared with the previous 30 days
* When the theme was first and most recently seen

By default, groups are ranked using lifecycle, growth, recent activity, and conversation volume. You can also sort by the most recently seen groups or the groups with the most conversations.

### Lifecycle

Lifecycle shows how established a signal group is:

| Lifecycle       | Meaning                                                     |
| --------------- | ----------------------------------------------------------- |
| **New**         | A recently identified recurring theme                       |
| **Recurring**   | A theme that continues to appear in customer conversations  |
| **Established** | A sustained theme with an established history               |
| **Inactive**    | A theme that is no longer appearing in recent conversations |

Growing groups also receive a **Growing** trend label, making increases in customer activity easier to spot.

### Filtering groups

Use the controls at the top of the Signals page to filter groups by signal type or lifecycle. Filters can help you answer focused questions, such as:

* Which bug reports are new?
* Which feature requests keep recurring?
* Are any documentation gaps growing?
* Which established issues have become inactive?

## Reviewing source evidence

Open a signal group to see the evidence behind it. The detail page includes the group's summary, activity totals, first-seen and last-seen dates, and every supporting signal currently assigned to the group.

Each supporting signal links to its source conversation, so you can review the customer's language and the surrounding context before deciding what to do next.

<Tip>
  Use source conversations to validate the scope of a problem. A group summarizes the shared theme,
  while the underlying tickets show the different ways customers describe and experience it.
</Tip>

## The Signals Feed

The **Feed** tab shows individual signals as CraftCX detects them, before or alongside grouping. Each entry includes its type, summary, detection time, and a link to the source ticket.

Use the feed when you want to review the latest customer observations. Use grouped Signals when you want to understand repeated themes, changes in volume, and which problems may deserve broader attention.

## Using Signals in your workflow

Signals are designed to turn support activity into evidence for support, product, and operational decisions. A practical review loop is:

<Steps>
  <Step title="Start with ranked groups">
    Review the highest-ranked themes for new, growing, or high-volume customer problems.
  </Step>

  <Step title="Narrow the view">
    Filter by type or lifecycle when you are investigating a specific area, such as recent bugs or
    recurring feature requests.
  </Step>

  <Step title="Review the evidence">
    Open a group and read its supporting conversations to confirm the problem and understand its
    impact.
  </Step>

  <Step title="Share the finding">
    Use the group's summary and source conversations as evidence when prioritizing product,
    documentation, or operational work.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Open Signals" icon="comments" href="https://app.craftcx.com/signals">
    Review grouped customer problems and needs in CraftCX.
  </Card>

  <Card title="CraftCX overview" icon="telescope" href="/introduction">
    Learn how Signals fit into the CraftCX product.
  </Card>
</CardGroup>