Signals

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.

A Signal is a recurring pattern across your customer feedback — like “slow CSV export” or “missing SSO” — that the Agent has detected by grouping related insights together. Signals are how you move from a scattered inbox of feedback to a clear, ranked list of opportunities worth acting on. Find Signals in the sidebar. Clicking it opens the Trends view by default; toggle the chevron next to the heading to switch to All Signals.

---

​

How Signals fit into your workflow

1. Feedback comes in from your connected sources — Slack, Intercom, email, the portal, calls.
2. The Agent processes it — extracts insights, classifies sentiment and type, assigns product areas, and groups related insights into Signals.
3. You review Signals — sense-check what’s growing, what’s unaddressed, where revenue is concentrated.
4. You act on the strong ones — promote a Signal to a Feature, and all its linked insights and customer context carry forward.

For an end-to-end walkthrough, see Turn customer feedback into a roadmap.

---

​

Enable automatic detection

Automatic Signal detection is the Agent’s Opportunity Intelligence pipeline. With it on, every new piece of feedback gets processed — insights extracted, sentiment and type classified, product areas assigned, and related insights grouped into Signals — without anyone in your team having to triage manually. To enable it:

1. Click your workspace name in the top-left corner.
2. Go to Settings → Signals.
3. Toggle Opportunity Intelligence on.

Without Opportunity Intelligence enabled, you can still create and manage Signals manually — automatic grouping just won’t run.

---

​

Two views

The Signals surface has two views you toggle between using the chevron next to the page heading.

​

Trends — the default view

The dashboard for spotting what’s gaining traction. Use it when you want a high-level read: what’s growing, what’s stuck, where the money is. Summary cards at the top show three pulses:

• New Signals — count for the selected time range, with growth percentage, revenue impact, and customer count.
• Processed Signals — all-time count of Signals you’ve acted on, broken down by features in progress vs. done.
• Unaddressed Signals — all-time count still in New, with the age of the oldest one and the number of product areas affected.

Charts beneath the cards:

• Trending Signals — top 5 by momentum, switchable between insight count and customer count.
• Signals by Revenue Impact — top 5 ranked by revenue impact (all-time).
• Signals Over Time — area chart of Signals created vs. Signals linked to a feature, daily or weekly.
• Unaddressed by Revenue — top 5 unaddressed Signals by revenue.
• Signal Pipeline — weekly stacked chart of New / In Progress / Done.
• Product Areas by Volume — top 5 product areas by Signal count in the selected range.

Time range (top right): Last 7 days, Last 30 days, Last 3 months. Most charts respect the selected range; a few all-time cards (Processed, Unaddressed, Signals by Revenue, Unaddressed by Revenue) ignore it on purpose. Refresh clears cached data and reloads every chart.

​

All Signals — the list view

Every Signal in your workspace, organized by status. Use it when you want to work through Signals one by one — review, accept, reject — rather than scan the dashboard. Status tabs at the top of the list:

• New — recently detected, not yet reviewed. This is where most of your day-to-day work happens.
• Processed — Signals you’ve accepted and turned into Features.
• Rejected — Signals you’ve dismissed as not actionable.

Columns (toggle via the Display dropdown):

• Priority Score
• Trends — the per-Signal momentum indicator
• Last activity
• Insights — number of linked insights
• Customers — distinct customers behind the Signal
• Revenue Impact — total revenue across requesting customers

Search narrows the list by name. Create Signal opens a manual creation flow (see below).

---

​

Priority Score

Every Signal carries a Priority Score from 0 to 100 — a single number for how impactful this Signal is, calculated from the prioritization weights you’ve set for your workspace. For Signals, three components shape the score:

• Revenue impact — total revenue across the customers behind the Signal
• Customer count — distinct customers requesting the Signal
• Insight count — feedback volume linked to the Signal

Each component is normalized against the highest value in your workspace and weighted by the percentages you set under Settings → Prioritization. You’ll see the score as a sortable column on All Signals and as the first stats card on the Signal detail page. Tune the weights to match how your team prioritizes — revenue-driven teams crank up Revenue Impact, volume-driven teams lean on Insight Count. See Prioritization for the full breakdown and configuration steps.

---

​

Working with a Signal

Click any Signal to open its detail view. What you see:

• Title and description
• Priority Score and stats: linked insights, customers, total revenue
• The full list of linked insights — verbatim customer quotes that share this pattern
• Linked Features (if any)

What you can do:

• Accept the Signal — moves it to Processed and creates a Feature from it. Two ways:
  • With Agent (recommended) — the Agent analyzes the linked insights and drafts a structured feature brief. Requires at least one linked insight and consumes credits.
  • Manually — you create the feature and write the brief yourself.
• Reject the Signal — dismiss it. Useful when the Agent has grouped something that isn’t actually a pattern worth tracking.
• Edit the name, description, or product area.
• Link more insights — broaden a Signal by attaching insights the Agent didn’t initially group.

Accepting carries every linked insight and customer over to the new Feature, so the brief starts with full context.

---

​

Statuses, in plain terms

A rejected Signal can be moved back to New at any time if you change your mind.

---

​

Create a Signal manually

When you spot a pattern the Agent hasn’t grouped yet:

1. Go to All Signals.
2. Click Create Signal in the top right.
3. Give it a name, an optional description, and link the insights you want it to cover.

Manual Signals behave exactly like detected ones — same statuses, same accept/reject flow, same place in Trends, same Priority Score logic.

---

​

A few habits that work

• Review New weekly. Don’t let New build up — momentum signals are most useful when you catch them early.
• Sort by Priority Score before acting. It’s the fastest way to surface what’s most impactful right now, given how your workspace weights revenue, customers, and feedback volume.
• Use Reject freely. Rejecting a Signal isn’t permanent — it just keeps your New tab focused on the patterns that matter.

---

​

FAQs

Q: Are Signals detected automatically?
A: Yes, when Opportunity Intelligence is enabled under Settings → Signals. Existing insights from before you enabled it aren’t reprocessed retroactively. Q: Can I create a Signal myself?
A: Yes. Use Create Signal on the All Signals view to start one and link insights manually. Q: How is Priority Score calculated?
A: From three components — revenue impact, customer count, and insight count — each normalized across your workspace and weighted by the percentages you set under Settings → Prioritization. Q: What happens when I accept a Signal?
A: It moves to Processed and creates a Feature. Every linked insight, customer, and the total revenue carry over — so the new Feature starts fully grounded. Q: Can I undo a rejected Signal?
A: Yes. Open the Signal and move it back to New. Q: Why isn’t my Signal showing up on Trends?
A: Trends respects the selected time range (7d / 30d / 3m) for several cards. If a Signal was created outside that window, switch the range or check the all-time cards (Processed, Unaddressed, Revenue Impact).