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

# Signals

> The recurring patterns Lane finds across your feedback — a ranked list of what customers keep asking for, and the unit you prioritize and act on.

A Signal is a recurring pattern across your feedback — "slow CSV export," "missing SSO" — assembled from the individual [Insights](/insights) that say the same thing. It's the unit that turns a scattered inbox into a decision: instead of reading a thousand messages, you work a ranked list of the things customers keep asking for, each one carrying the customers and revenue behind it.

Signals are where prioritization happens and where work begins. You review them, rank them, and turn the strong ones into [Plans](/docs).

## How Signals form

Signals are detected for you. As feedback is processed, Lane clusters related Insights across many items into a Signal and keeps it updated as more evidence arrives — new Insights attach, the customer count and revenue climb, the [Priority Score](#priority-score) shifts. This runs automatically once the **Detect Signals** stage is enabled in Automation settings.

## Two ways to work the list

The Signals page has two tabs, and which one you live in depends on how you work.

### All Signals

The complete list, organized by status — **New**, **Processed**, **Rejected**. This is where you triage: work through New Signals, decide what's worth acting on, and reject the noise. Sort by **Newest**, **Trending** (momentum), **Priority Score**, or **Revenue Impact**, and toggle those same columns on with the Display control.

### For You

A focused cut that surfaces only the New Signals that match what your workspace has said matters right now. Rather than scan everything, you see the handful worth your attention first — and each surfaced Signal shows *why* it made the cut: **Matches priority**, a **prioritized customer tier**, or a **churn-risk status**.

For You is driven by your workspace **Context** — your current priority, the tiers you care about, the statuses that signal churn risk. It comes to life once you've set that context and turned on the **Surface what matters** stage in Automation; until then, For You shows a short setup prompt instead of a list.

## Priority Score

Every Signal carries a **Priority Score** from 0 to 100 — one number for how much this Signal should command your attention. It blends the **revenue** behind the requesting customers with **demand** (how many customers or how much feedback is behind it), weighted the way your team has chosen.

The score is a sortable column on All Signals and the headline stat on a Signal's detail. Tune what drives it — revenue-led or demand-led — under [Prioritization](/prioritization).

## Working with a Signal

Open any Signal to see the full picture and decide what happens next.

**What you see:** the title and description, the Priority Score and stats (linked Insights, distinct customers, total revenue), the [Product Area(s)](/product-areas) it touches, the verbatim Insights behind it, and any [Plans](/docs) already linked.

**What you can do:**

* **Accept it.** Mark a Signal **Accepted** once you've decided it's worth acting on. Accepting is its own action, independent of creating a Plan — you can accept a Signal before you're ready to draft the work.
* **Turn it into a Plan.** **Create Plan** is how a Signal becomes work. **Use Lane** drafts a structured brief from the Signal's Insights and customer context — optionally against a plan template — while **Write it myself** opens a Plan seeded with the Signal linked. Creating a Plan keeps it linked back to the Signal, but doesn't change the Signal's status by itself — accept it separately if you haven't already.
* **Reject it.** Dismiss a Signal that isn't a real pattern or isn't worth acting on. Nothing is lost — a rejected Signal can move back to New anytime.
* **Refine it.** Edit the name or description, and link additional Insights that weren't initially grouped.

## Statuses

| Status       | Means                                                                     |
| :----------- | :------------------------------------------------------------------------ |
| **New**      | Detected and waiting on a decision                                        |
| **Accepted** | Marked as worth acting on (previously labeled "Processed" in some places) |
| **Rejected** | Dismissed — not a real pattern, or not worth acting on                    |

## A few habits that work

* **Review New regularly.** Momentum matters most when you catch it early — a Signal that's climbing is more useful this week than next quarter.
* **Let Prioritization do the sorting.** Sort by Priority Score before you act; it reflects how your team weighs revenue against demand, so the top of the list is the fastest read on what matters now.
* **Reject freely.** Rejecting keeps New focused on real patterns, and it's always reversible.

## FAQs

**Q: Are Signals detected automatically?**\
A: Yes, once **Detect Signals** is enabled in Automation. Feedback captured before you turned it on isn't reprocessed retroactively.

**Q: What's the difference between All Signals and For You?**\
A: All Signals is the complete list with status tabs for triage. For You surfaces only the New Signals that match your workspace context, so you see what's most relevant first.

**Q: Why did a Signal surface in For You?**\
A: Because it matched your current priority, a prioritized customer tier, or a churn-risk status — the badge on the row tells you which. Set those under **Context** in settings.

**Q: What happens when I turn a Signal into a Plan?**\
A: The Plan is linked to the Signal, and its Insights, customers, and revenue context carry into the Plan so the draft starts grounded. Creating a Plan doesn't change the Signal's status on its own — use **Accept** separately to mark it Accepted.

**Q: Can I bring a rejected Signal back?**\
A: Yes. Open it and move it back to New.