Skip to main content
Feature requests are the core organizational unit in GTM Feedback. They represent specific features or improvements that customers are asking for.

​
Creating Requests

Create a new feature request through the web UI:
1

Open the request form

Click the “Add Request” button or navigate to the requests page.
2

Fill in request details

Complete the form with:
  • Title (required): Clear, concise feature name (max 200 characters)
  • Description (required): What the feature does and why it matters (max 1000 characters)
  • Product Areas (required): One or more areas this feature belongs to
  • Related Links (optional): Links to PRDs, design docs, etc. (one per line)
  • Linear URL (optional): Link to your Linear issue
3

Submit

Create the request - you’ll automatically become a follower.
Request titles must be unique. The system will generate a URL-friendly slug from the title.

​
Request Details

Each feature request page displays comprehensive information:

​
Header Metrics

Key metrics displayed at the top:

Feedback Count

Total number of customer feedback items linked to this request.

Open Opportunity ARR

Total ARR from all open sales opportunities associated with feedback.

Product Areas

Areas this feature belongs to (clickable to filter).

​
Feedback List

All customer feedback for this request, organized by:
  • Severity (High → Medium → Low)
  • Creation date (newest first within each severity)
Each feedback item shows:
  • Account name and logo
  • Customer pain description
  • Severity indicator
  • Creator and date

​
Status Management

Feature requests have three possible statuses:
Active requests that are being considered or planned.
  • Default status for new requests
  • Shown with blue badge
  • Visible in all standard views
Changing status to “Shipped” sends notifications to all followers. Use this thoughtfully.

​
Product Areas Assignment

Requests must be assigned to at least one product area:

​
Why Product Areas Matter

  1. Organization - Group related requests together
  2. Analytics - Generate insights per area
  3. Notifications - Route to area-specific Slack channels
  4. Ownership - Assign areas to product teams

​
Managing Areas

  • Select multiple areas when creating or editing a request
  • Areas are clickable badges that link to area pages
  • Filter requests by area in list views
Assign requests to the primary area first, then add secondary areas as needed.

​
Follower System

Stay updated on feature requests by following them:

​
Automatic Following

You automatically follow any request you create.
You automatically follow the request when adding feedback to it.

​
Manual Following

  • Click the “Follow” button on any request page
  • Unfollow anytime by clicking “Unfollow”
  • View your followed requests in your user profile

​
Follower Notifications

Followers receive notifications when:
  • Request status changes to “Shipped”
Notifications are sent via Slack DM to users with connected Slack accounts.

​
Editing Requests

Only admins and the request creator can edit requests.
Editable fields:
  • Title
  • Description
  • Product areas
  • Related links
  • Linear URL
Editing the title will update the URL slug. Old URLs will no longer work.
When AI detects that feedback might match multiple feature requests, it suggests related requests:
  1. Review suggestion - Check if the suggested match is better
  2. Accept - Link the feedback to the suggested request
  3. Dismiss - Keep the current assignment
This helps consolidate duplicate or very similar feature requests.

​
Request Insights

Each request page provides insights:

​
ARR Tracking

See the total ARR associated with the request from:
  • Open opportunities linked to feedback
  • Account ARR for all providing feedback

​
Feedback Distribution

Understand severity distribution:
  • Count of high/medium/low severity feedback
  • Visual indicators for severity levels
  • Quick scan of customer priority

​
Search and Discovery

Find requests through: Search across all requests by title and description at /search.

​
Area Pages

Browse requests within a specific product area at /areas/[slug].

​
User Pages

See requests created by a specific team member at /user/[userId].

​
Best Practices

Use concise, specific titles that clearly describe the feature:
  • ✅ “Export customer feedback to CSV”
  • ✅ “Support SSO with Okta”
  • ❌ “Better reports”
  • ❌ “Improve the thing”
Explain:
  • What the feature does
  • Why customers need it
  • What outcome it enables
  • Any constraints or requirements
  • Assign to 1-3 areas maximum
  • Choose the most specific area available
  • Create new areas if needed for better organization

Build docs developers (and LLMs) love

Get started for freeTalk to us