> ## 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.

# Automation

> Decide how much of the work Lane handles on its own — from turning raw feedback into Signals to surfacing the ones that matter most.

Automation is the dial for how much Lane does without you. Feedback moves through a pipeline, and you choose which stages Lane runs on its own. Each stage builds on the one before it, so you can start manual and turn on more as you trust it.

You'll find it in **Settings → Automation**.

## Detect Signals

**Turns raw feedback into structured, tagged Signals.**

With this on, every incoming piece of [Feedback](/insights) is processed automatically — Lane extracts the Insights inside it, classifies type and sentiment, routes it to the right [Product Areas](/product-areas), and clusters related Insights across your feedback into [Signals](/signals). This is what moves you from an inbox of individual messages to a ranked list of patterns without anyone triaging by hand.

With it off, feedback is still captured and organized, but it won't be grouped into Signals for you.

## Surface what matters

**Highlights the Signals most worth your attention.**

Detecting Signals tells you *what's* being asked for; surfacing tells you *which ones matter to you right now*. With this on, Lane uses your [Context](/context) — your current priority, prioritized tiers, and churn-risk status — to flag the Signals you should look at first, which is exactly what powers the **For You** tab on [Signals](/signals).

This stage needs **Detect Signals** on — without Signals, there's nothing to surface. When you turn it on, Lane offers to scan your existing Signals against your context so surfacing applies to your current backlog, not just new feedback. Because that scan re-evaluates what you already have, it uses AI credits — Lane shows you what it'll cover and asks first.

## How the stages fit together

Think of it as a ladder you climb as you're ready:

1. **Detect Signals** — Lane does the triage, turning feedback into Signals.
2. **Surface what matters** — Lane does the prioritizing, putting the right Signals in front of you.

Turn on the first to stop triaging manually; add the second once your [Context](/context) is set and you want Lane to focus your attention automatically.

## FAQs

**Q: Do I need both stages on?**\
A: No. Detect Signals works on its own. Surface what matters builds on it, so it needs Detect enabled.

**Q: What does surfacing use to decide?**\
A: Your [Context](/context) — current priority, prioritized tiers, and churn-risk status. Keep those current and surfacing stays relevant.

**Q: Does turning on surfacing cost credits?**\
A: Only the optional scan of your existing Signals that it offers. New feedback is surfaced as it arrives.

**Q: What happens with everything off?**\
A: Feedback is still captured and you can work Signals manually — Lane just won't detect or surface them for you.