Skip to main content
Product Areas are the map of your product — Onboarding, Billing, Reporting, Integrations, whatever the meaningful parts of your surface are. They’re the taxonomy everything else hangs off: when Feedback is processed, Lane routes it to the right area; Signals and Plans carry theirs too. That’s what lets you ask “where is demand concentrated?” and get a real answer. Because a single piece of feedback often touches more than one area, records can carry multiple product areas — a request about “exporting a report” can belong to both Reporting and Integrations.

​
Set up your areas

Product Areas has its own space in the sidebar, under Records, and a management view in Settings → Product Areas. Each area has three things:
  • Name — what your team calls this part of the product.
  • Colour — so areas are recognizable at a glance across the app.
  • Description — a short explanation of what belongs here.
The description isn’t cosmetic. Lane reads it when deciding where to route incoming feedback, so a clear description — what the area covers, what it doesn’t — directly improves routing accuracy. This is the single highest-leverage thing you can do to keep your feedback well-organized.
Write descriptions for a reader who doesn’t know your product. “Billing — invoices, payment methods, plan changes, and dunning” routes far more accurately than “Billing — billing stuff.”

​
Where product areas show up

Set your areas once and they work everywhere:
  • Feedback is routed to its area(s) automatically during processing, so your inbox is organized without manual tagging.
  • Signals carry the areas of the feedback behind them — so you can see which parts of the product are generating the most demand.
  • Plans inherit product areas from the Signal or feedback they start from, keeping delivery mapped to the same taxonomy.
The Product Areas view itself shows each area alongside how much is mapping to it, so you can read at a glance where attention is going.

​
Best practices

  • Keep the set small and stable. A dozen clear areas beat fifty overlapping ones. Product areas are most useful when everyone means the same thing by them.
  • Invest in descriptions. They’re what makes automatic routing accurate — treat them as instructions to Lane, not labels for humans.
  • Revisit as the product grows. When you ship a genuinely new surface, add an area for it so feedback has somewhere to land.

​
FAQs

Q: Can one item belong to more than one product area?
A: Yes. Feedback, Signals, and Plans can each carry multiple product areas. Q: How does Lane decide which area feedback goes to?
A: It’s routed automatically during processing, using each area’s name and description — which is why good descriptions matter. Q: Where do I manage product areas?
A: In the Product Areas view (under Records in the sidebar) or in Settings → Product Areas. Q: Can I edit or delete a product area later?
A: Yes. Edit anytime and the change reflects everywhere the area is used. If you delete one, reassign any affected records to another area. Q: What happens if I don’t set any up?
A: Feedback is still captured and processed — it just won’t be organized by area, and Signals won’t show where demand is concentrated.