Skip to main content
Product areas help you organize feature requests into logical categories, enabling area-specific analytics, ownership, and automated routing.

​
What Are Product Areas?

Product areas are organizational units that group related feature requests together. Examples might include:
  • Authentication & Security
  • Reporting & Analytics
  • Integrations
  • API & Developer Tools
  • Mobile Experience
  • Admin & Settings
Each area has:
  • A unique name and URL slug
  • A description of its scope
  • An optional Slack firehose channel
  • A dedicated analytics page

​
Creating Product Areas

Create new product areas through the management interface:
1

Navigate to area management

Go to /manage/areas (admin access required).
2

Click Create Area

Open the creation form.
3

Fill in area details

  • Name (required): Clear, concise area name (max 100 characters)
  • Description (required): What this area covers (max 500 characters)
  • Firehose Channel (optional): Slack channel name for notifications
4

Submit

Create the area - a URL slug will be generated automatically.
Area names must be unique. The system generates a URL-friendly slug from the name (e.g., “API & Developer Tools” → api-developer-tools).

​
Area Configuration

​
Basic Settings

​
name
string
required
The display name for the area. Must be unique across all areas.Examples:
  • “Authentication & Security”
  • “Reporting & Analytics”
  • “Mobile Experience”
​
description
string
required
A clear description of what features belong in this area.Example: “Features related to user authentication, authorization, SSO, and security controls.”
​
slug
string
Auto-generated URL-friendly identifier based on the name.Used in URLs: /areas/[slug]

​
Slack Integration

​
firehoseChannel
string
Slack channel name (without #firehose- prefix) where new feedback should be posted.Input formats accepted:
  • api → posts to #firehose-api
  • firehose-api → posts to #firehose-api
  • #firehose-api → posts to #firehose-api
The system automatically adds the #firehose- prefix to channel names. Just enter the area identifier.

​
Assigning Requests to Areas

​
During Request Creation

When creating a feature request:
  1. Select one or more areas (at least one required)
  2. Choose all applicable areas
  3. The primary area determines default routing

​
Editing Area Assignments

Change area assignments by editing the request:
  1. Navigate to the request page
  2. Click “Edit” (admin/creator only)
  3. Update the selected areas
  4. Save changes
Changing areas updates:
  • Area-level analytics
  • Slack routing for future feedback
  • Related area insights reports

​
Multiple Area Assignment

Requests can belong to multiple areas when they:
  • Span multiple product domains
  • Impact different teams
  • Have cross-functional requirements
Assign to 1-3 areas typically. More than 3 suggests the request might need to be split.

​
Area Pages

Each area has a dedicated page at /areas/[slug] showing:

​
Area Header

  • Area name - Main heading
  • Description - Area scope and purpose
  • Analytics toggle - Expand/collapse insights

​
Analytics Section

AI-generated insights about the area (see Analytics & Insights for details):
  • Key themes and patterns
  • Top requests by ARR
  • Recent activity
  • Sentiment analysis

​
Request List

All feature requests assigned to this area:
  • Sortable by multiple criteria
  • Filterable by status
  • Shows request metrics (feedback count, ARR)
  • Links to full request pages

​
Firehose Notifications

When a firehose channel is configured, new feedback automatically posts to that Slack channel.

​
Message Format

Firehose messages include: 
🔔 New Feedback: [Feature Request Title]

Account: [Customer Name]
Severity: [High/Medium/Low]
Opportunity ARR: [$XXX,XXX]

Customer Pain:
[Description of the customer need]

→ View in GTM Feedback: [Link]

​
Routing Logic

  • Feedback posts to all areas assigned to the request
  • If request has multiple areas, message appears in multiple channels
  • Messages post when feedback is created, not on edits
Firehose channels help product teams stay informed about customer needs in their domain without monitoring all feedback.

​
Area Insights

Each area automatically generates AI-powered insights (refreshed weekly):

​
What’s Analyzed

Request Patterns

Common themes across feature requests in the area.

Customer Signals

Which customer segments are most engaged with this area.

Priority Indicators

High-ARR or high-severity feedback that needs attention.

Trends Over Time

Changes in feedback volume and sentiment.

​
Insights Display

On the area page analytics section:
  1. Summary sections - Key themes with importance ratings
  2. Visualizations - Charts and metrics
  3. Top requests - Ranked by impact
  4. Raw data - Detailed breakdowns
Insights are generated automatically via cron job. You can also manually regenerate them anytime.

​
Managing Areas

​
Editing Areas

Update area configuration:
  1. Navigate to /manage/areas
  2. Find the area to edit
  3. Update name, description, or firehose channel
  4. Save changes
Changing the area name updates the slug. Old URLs will redirect to the new slug.

​
Area Analytics Dashboard

View area-level metrics:
  • Request count - Total feature requests
  • Feedback volume - Total customer feedback items
  • ARR impact - Combined ARR across all requests
  • Status distribution - Open vs. shipped vs. deprioritized

​
Best Practices

Make area scope obvious:
  • ✅ “Authentication & Security” - Clear what belongs
  • ✅ “Mobile Apps” - Specific platform
  • ❌ “Features” - Too broad
  • ❌ “Misc” - Creates a dumping ground
Create dedicated Slack channels:
  • Use consistent naming: #firehose-[area]
  • Include relevant product/eng team members
  • Configure notifications appropriately
  • Review messages regularly
Map areas to team ownership:
  • Each area should have clear owners
  • Owners monitor area insights
  • Owners triage area-specific feedback
  • Consider team capacity when creating areas
Make area insights part of planning:
  • Review during sprint planning
  • Discuss top requests by ARR
  • Track trends over time
  • Share insights with stakeholders
Guidelines for area count:
  • Start with 5-10 core areas
  • Add areas as product grows
  • Merge areas that are too granular
  • Split areas that become too broad

​
Area Schema

Areas are stored with this structure: 
areas {
  id: string              // UUID
  name: string            // Display name (unique)
  slug: string            // URL slug (unique)
  description: string     // Area scope
  firehoseChannel: string // Slack channel (optional)
}

​
Request-Area Relationship

Requests link to areas via array: 
requests {
  id: uuid
  title: string
  description: string
  areaIds: string[]      // Array of area IDs
  // ... other fields
}
This enables:
  • Multiple area assignment
  • Fast area-based filtering
  • Efficient analytics queries

Build docs developers (and LLMs) love

Get started for freeTalk to us