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

# Feedback

> Every piece of customer input, in one place — captured from your tools, processed by Lane, and grouped into the patterns worth acting on.

Feedback is the raw material of product decisions: support tickets, sales notes, portal requests, call transcripts, a message someone flagged in Slack. On their own they're scattered and hard to reason about. In Lane, every one of them lands in a single place, gets processed the same way, and rolls up into [Signals](/signals) — the recurring patterns you actually prioritize.

This page covers how feedback gets in, what Lane does with it, and how a single item becomes part of a larger decision.

## Where feedback comes from

Feedback flows in from the tools your customers and team already use. Each source stamps the item with its origin, so you can always trace a request back to where it was said.

* **Support & messaging** — [Slack](/slack), [Intercom](/intercom), [Zendesk](/zendesk), and [Email](/email) forwarding
* **Customer portal** — requests your customers submit directly, via the [Portal](/portal)
* **Browser** — capture a page or a selected quote with the [Chrome extension](/chrome-extension)
* **Bulk** — [CSV import](/import) from a spreadsheet or another tool
* **Manual** — add a piece of feedback yourself from anywhere in the app

Much of this happens without anyone lifting a finger. Connect a support tool and Lane can **ingest feedback automatically** — solved Zendesk tickets, for instance, flow in on their own, each run through an AI filter so only genuine product feedback is captured rather than every routine ticket. Sources that shouldn't fire on everything let your team capture on demand instead — an emoji reaction in Slack, a click in Intercom — so the signal gets in without the noise.

When an item arrives with a customer email, Lane resolves it to the right [Customer](/customers) automatically — matching the person by email and the company by domain — so feedback is tied to an account without manual linking.

## What Lane does with it

Raw feedback is noisy. Lane's processing turns each item into structured, comparable data:

* **Extracts insights** — the specific quotes, pain points, and requests buried inside a longer message
* **Classifies** each insight by type and sentiment
* **Routes** it to the relevant [Product Area(s)](/product-areas)
* **Clusters** related insights across many items into [Signals](/signals)

This is what moves you from an inbox of individual messages to a ranked view of what customers keep asking for. Processing runs automatically once the **Detect Signals** stage is enabled in Automation settings — until then, feedback is still captured and organized, it just isn't grouped for you.

<Note>
  Processing feedback uses AI credits from your workspace balance. See [Billing](/billing) for how credits work.
</Note>

## Anatomy of a feedback item

Each item carries a small, consistent set of fields so it can be filtered, grouped, and compared:

| Field            | What it's for                                                                 |
| :--------------- | :---------------------------------------------------------------------------- |
| **Title**        | A short summary of the request or problem                                     |
| **Description**  | The full context — the original message or note                               |
| **Status**       | Where it is in your workflow. Feedback from integrations starts in **Triage** |
| **Type**         | Feedback, Bug, or Praise                                                      |
| **Sentiment**    | Positive, Neutral, or Negative                                                |
| **Product Area** | One or more areas of your product the feedback touches                        |
| **Customer**     | The account and contact behind the feedback                                   |
| **Tags**         | Free-form labels for your own categorization                                  |
| **Source**       | Where it came from — auto-filled for integrations                             |

## Insights

When processing is on, Lane pulls **insights** out of each feedback item — the individual quotes and requests that matter — so a long message doesn't get flattened into a single label. Insights are what actually get clustered into Signals.

You'll find them in the **Insights** tab of a feedback item's detail view; a dot on the tab marks items where insights are ready. Each insight shows a short keyword for its core topic, the verbatim excerpt, its sentiment and type, and the product area it was routed to. You can adjust an insight's product area inline, and you can create insights yourself by selecting text in the description — useful when you want to pull out a point the AI didn't surface.

## From feedback to a decision

Feedback isn't the end state — it's evidence. Two paths take it forward:

* **Into a Signal.** Most feedback earns its weight by joining others. As insights cluster, the pattern shows up in [Signals](/signals) with its full customer and revenue context attached — which is what [Prioritization](/prioritization) ranks.
* **Into a Plan.** When a single piece of feedback is worth acting on directly, use the **Plan** action on its detail view. **Use Lane** drafts a structured brief from the feedback and its customer context; **Write it myself** opens a blank Plan seeded with the feedback linked. Either way the [Plan](/docs) stays connected back to the original request.

## Closing the loop

A feedback item is only truly resolved when the customer hears back. When every [Plan](/docs) linked to a piece of feedback reaches a shipped status, its detail view shows a **Loop closed?** prompt. Depending on the source, Lane can post back automatically — a reply in the original Slack thread, an internal note in Intercom or Zendesk — or you can follow up and mark the loop closed yourself. See [Closing the loop](/close-the-feedback-loop) for the full flow.

## Views

The Feedback surface has two tabs:

* **Feedback** — the working list of items, which you can filter, group, and save as [Views](/views). New integration feedback lands here in Triage.
* **Trends** — a read on what's moving: volume over time and where requests are concentrated across product areas.

## FAQs

**Q: What's the difference between feedback and an insight?**\
A: A feedback item is the whole captured message. Insights are the individual quotes and requests Lane extracts from inside it — those are what cluster into Signals.

**Q: Do I have to link feedback to a customer?**\
A: No, but it's worth it. Feedback with a customer attached carries revenue and tier into Signals and Prioritization. Feedback that arrives with a customer email is linked automatically.

**Q: Can I import feedback in bulk?**\
A: Yes — use [CSV import](/import) to bring in feedback from a spreadsheet or another tool, with customers linked by email.

**Q: What happens if I create a duplicate?**\
A: Delete duplicates manually for now. Automatic de-duplication isn't available yet.

**Q: Who can see feedback?**\
A: All workspace members have access to the full feedback list.