> ## 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 problems in your feedback, found for you and ranked by the customers and revenue behind them. The unit you decide on, act on, and close. A thousand pieces of feedback are hard to act on. The same dozen problems are not. A Signal is one recurring problem, like "slow CSV export" or "missing SSO", assembled from every piece of feedback that describes it, in your customers' own words. Lane finds Signals for you, keeps them current as new feedback arrives, and ranks them by who is asking and the revenue behind them. So instead of reading an inbox, you work a short, ranked list of real problems, each one carrying its evidence. Signals are also where work begins and ends: you accept the ones worth acting on, send them to your team's tracker or turn them into a [Doc](/docs), and close them when the work ships, which lets the customers who asked know. And from your Signals, Lane recommends [Opportunities](/opportunities): the few product bets most worth investing in, based on your priorities, the customers who matter most to you, and the demand behind them. ## How Signals form There's nothing to set up. As [feedback](/insights) comes in from your sources, Lane reads it, picks out what customers are asking for, and brings together the requests that point to the same problem into a Signal. Each Signal keeps itself up to date as new feedback arrives, so the customers, revenue and [Priority Score](#priority-score) behind it are always current. ## Highlights and Evidence A single piece of feedback often says several things. A call note might mention a slow export, a missing integration and praise for the new dashboard. Lane pulls each of these out as a **highlight**: one specific point, in the customer's own words, with its type (bug, feature request or praise), sentiment, product area and the customer who raised it. Highlights are what Signals are made of: when highlights point to the same need, Lane groups them into a Signal, so one call note can feed three different Signals. In Lane, highlights are your **Evidence**. Open **Signals** and choose the **Evidence** tab to see them. It opens on the highlights that aren't in a Signal yet; switch to **In Signal** to see the ones already grouped. On a Signal's page, its Evidence is the highlights it's built from, and on a feedback item, the **Highlights** tab shows what Lane pulled out of it. ### Why some highlights aren't in a Signal Lane groups highlights when they repeat. A highlight that matches no Signal and no other highlight stays in Evidence. These are often the most specific asks: a request from one large customer, a bug only one team hits, an idea nobody else has raised yet. ### Turning Evidence into Signals On a highlight that isn't in a Signal yet: * **Create Signal** makes a new Signal from it. Lane writes the name and summary. * **Add to Signal** adds it to a Signal you pick. * **Delete** removes a highlight that isn't useful. Select several to create one Signal from all of them, or add them all at once. Filter by product area, type and sentiment, or search by keyword, to find what you're after. **Want Signals for something specific?** Lane finds Signals by spotting the problems that come up again and again across your feedback. But what matters most to you doesn't always repeat: a request from your biggest customer, the issues one segment keeps hitting, everything about a feature you're about to rework. To turn that Evidence into Signals for exactly your focus, set up an [automation](/automation) and tell it what to look for. For example: *Every Monday, look at new Evidence from our Enterprise customers and create a Signal for each distinct problem that no existing Signal covers.* Lane reads only what matches your focus, creates the Signals, and tells you what it created and why. ## The Signals list Open **Signals** in the sidebar. The tabs at the top switch between **Signals** and **[Feedback](/insights)**, and **Sources** connects more places to bring feedback in from. Signals are split by status: **Open**, **Accepted** and **Closed**. Each row shows the Signal's [Product Areas](/product-areas), how many customers and how much feedback are behind it, the revenue impact, its 30-day trend, and its Priority Score. A **Priority tier** or **At-risk customer** badge marks Signals that touch the customer tiers and at-risk accounts you've set in [Context](/context). * **Sort** by **Newest**, **Trending** (most feedback in the last 30 days), **Priority score** or **Revenue Impact**. * **Filter** by Product Area, including **No Product Area** to find what isn't mapped yet. * **Search** by name. ## 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 customers asking with **demand**, how many customers or how much feedback is behind it, weighted the way your team has chosen in [Prioritization](/prioritization). Momentum counts too. A Signal that's picking up feedback gets a lift and one that's fading eases off, so two Signals of the same size don't rank the same when only one of them is growing. Momentum only adjusts real demand and revenue; it never outweighs them. ## Working with a Signal Open a Signal to see the full picture in one place: its status and any linked Docs, the summary, the Priority Score with customers, feedback, revenue and overall sentiment, the Product Areas it touches, its 30-day trend, the top customers asking and how they split by tier and status, and its **Evidence**: the highlights the Signal is built from, in the customers' own words. **Ask Lane** answers questions about the Signal right there. From the top of the page you can: * **Send it to your team's tracker.** **Send to** creates an issue, page or task in [Linear](/linear), [Notion](/notion), [Jira](/jira) or [Asana](/asana), with the Signal's summary and a link back to Lane. An Open Signal becomes Accepted, and the button then shows the item's live status, so you can see where delivery is without leaving Lane. Available on Pro. * **Turn it into a Doc.** **Create Doc** with **Use Lane** drafts a brief from the Signal's highlights and customer context, using a template you choose; **Write it myself** starts a Doc with the Signal's title and summary. Either way the Doc stays linked to the Signal. * **Refine it.** Edit the name or summary, or unlink a highlight that doesn't belong with the **×** on its row. * **Star it** to keep it in your favorites, or **Delete** it from the **⋯** menu. Deleting keeps the feedback; its highlights go back to Evidence. ## Statuses | Status | Means | | :- | :- | | **Open** | Found by Lane and not decided yet | | **Accepted** | Your team has taken it on | | **Closed** | The work has shipped | Change the status from the chip above the title. You can move in any direction, including back. A status change carries through to everything underneath it: * **Accepted** moves the Signal's feedback into progress. * **Closed** marks its feedback done and, with [close the loop](/close-the-feedback-loop) turned on, tells the customers who raised it in Slack, Intercom or Zendesk that the work has shipped. Some changes happen for you: sending a Signal to a tracker accepts it, accepting an [Opportunity](/opportunities) accepts its Open Signals, and status sync from [Linear](/linear) or [Notion](/notion) can move a Signal to Accepted or Closed as the work moves there. ## A few habits that work * **Sort by Trending once a week.** Momentum matters most when you catch it early; a Signal that's climbing is more useful this week than next quarter. * **Let the Priority Score do the sorting** before you act. It reflects how your team weighs revenue against demand. * **Close Signals when the work ships.** That's what tells the customers who asked, and it keeps Open focused on what's still undecided. * **Keep Context current.** Your priority tiers and churn-risk status decide which Signals get badges, and your priorities shape which ones Lane recommends as Opportunities. ## FAQs **Q: Do I need to turn anything on for Signals to form?**\ A: No. Lane groups feedback into Signals automatically as it's processed. **Q: What's the difference between a Signal and an Opportunity?**\ A: A Signal is one specific problem customers keep raising. An [Opportunity](/opportunities) is a product bet Lane recommends from your Signals, weighed against your priorities, your most important customers and the demand behind them. Opportunities are where you decide what to invest in. **Q: What happens when I turn a Signal into a Doc?**\ A: The Doc is linked to the Signal, and its highlights, customers and revenue carry into the draft so it starts grounded. Creating a Doc doesn't change the Signal's status; accept it separately when you're ready. **Q: Can Contributors work with Signals?**\ A: Contributors can view Signals. Changing them is for Editors and the Owner. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.