> ## 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. # Stay ahead of your feedback > Set Lane up so the work that matters comes to you — detected, surfaced, and nudged — instead of waiting to be found. The old way to stay on top of feedback is to *remember to check* — open the inbox, scan the list, hope you didn't miss the request from your biggest account. That doesn't scale, and it means the important stuff surfaces late. Lane flips it. Set it up once and the important work comes to you: Lane detects the patterns, surfaces the ones that matter to *you* right now, and nudges you where you already work. This playbook shows how to make Lane proactive — so your attention goes to decisions, not triage. ## 1. Tell Lane what matters Proactivity starts with [Context](/context). In **Settings → Context**, set: * **Priorities**: what you're focused on this quarter * **Not now**: what you've decided not to pursue, so Lane stops suggesting it * **Priority tiers**: the customer tiers you care about most * **Churn-risk status**: the customer status that means an account is at risk * **Accounts to watch**: specific accounts you want Lane to keep an eye on This is the lens Lane uses to decide what's worth your attention. Two minutes here is what makes everything downstream sharp. ## 2. Let Lane detect and surface There's nothing to switch on. As [feedback](/insights) arrives, Lane processes it and groups it into [Signals](/signals) automatically, so you never triage a raw inbox, and uses your Context to flag what you should look at first. The pipeline runs itself: feedback in, ranked patterns out, the relevant ones marked. ## 3. Let the decisions come to you The important work is already sorted when you open Lane: * [**Signals**](/signals) are ranked by your Priority Score, and those touching your priority tiers or at-risk accounts carry a badge, so the ones that matter stand out in the list. * [**Opportunities**](/opportunities) find themselves. On the schedule you set, Lane weighs your Signals against your Context and the demand behind them, and recommends the few product bets most worth your focus, marked **Matches priority** when they fit what you're working on. Quiet weeks cost nothing. You're not searching for what's important; it's the first thing you see. ## 4. Get nudged where you already work You shouldn't have to open Lane to know something needs you. **[Automations](/automation)** do the checking for you and send what they find to the places your team lives: * **Slack**: each result posted to the channel you choose. * **Email**: each result sent to the members you pick. Set one up for a Monday read on what's rising, what's fading and where demand drifts from your priorities, or have Lane watch competitors and tell you when one ships something your customers asked for. Templates get you started in a minute. Now the loop reaches you even when you're heads-down elsewhere. ## What good looks like With this in place, the rhythm changes. You don't sit down to *find* what matters — Lane has already surfaced it and, when it's urgent, told you. You spend your time deciding and acting, which is the next playbook. Once something surfaces, turn it into shipped work — and close the loop with the customer. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.