14 Feature Request Templates (Copy, Paste, Ship)

Product teams that use structured feature request forms ship 40% fewer duplicate features than teams relying on freeform email inbound, according to a 2025 survey of 300 SaaS PMs (source). The difference isn't software, it's the form fields. A good template captures title, use case, and priority in a way that stops duplicate submissions before they start.

TL;DR:

• The best feature request form has five fields: title, description, use case, priority, and optional screenshot. Anything else adds friction without value.
• Templates should vary by product type, a mobile app needs OS and device fields, an e-commerce site needs order context, an agency needs client project scope.
• Embedding a form is 5 minutes of work with Feedbask, Canny, or Featurebase. The harder part is choosing which fields to include.

What Makes a Good Feature Request Form

A good form captures just enough context to make a shipping decision without annoying the user.

The five fields that matter most:

1. Title. A short, one-sentence request ("Bulk edit rows in table view"). This becomes the thread title everyone else votes on.
2. Description. Two or three sentences on what the user wants and why.
3. Use case. A specific example of when the user would use this feature. This is the field most forms skip and most PMs miss.
4. Priority. Low / Medium / High, or "nice to have / important / blocking." Always self-reported by the user.
5. Screenshot or attachment. Optional, but essential for UI-specific requests.

Fields to avoid: full name, phone number, company size, industry. If you have user auth, you already know all of this. Asking again on the form kills submission rates by roughly 30-50% per extra field, depending on the product.

Below are 14 templates split into four categories, with the fields to include and a filled-in example for each.

Generic SaaS Templates (4)

Template 1: Standard Feature Request

Who it's for: Any B2B SaaS with logged-in users.

Fields:

• Title (text, required, max 80 chars)
• Description (textarea, required, max 1000 chars)
• Use case (textarea, optional, "Describe a specific time you needed this")
• Priority (radio: Nice to have / Important / Blocking)
• Related workflow (dropdown, optional, e.g. "Dashboard, Reports, Integrations")
• Attachment (file, optional, max 10MB)

Example fill:

• Title: "Export dashboard charts as PNG"
• Description: "Right now I can only export data as CSV. I'd like to export visual charts too, for slide decks."
• Use case: "Monthly board meeting, I paste dashboard screenshots manually. Takes 30 minutes."
• Priority: Important
• Related workflow: Dashboard

Template 2: Power User Request

Who it's for: Tools with advanced users (analytics, dev tools, CRMs).

Fields:

• Title (text, required)
• Current workaround (textarea, "How do you solve this today?")
• Desired behavior (textarea)
• Frequency (dropdown: Daily / Weekly / Monthly / Rarely)
• Users affected (number, optional, "How many people on your team need this?")

Example fill:

• Title: "Regex support in search filter"
• Current workaround: "I export to CSV and grep manually."
• Desired behavior: "Let me type a regex in the search box, with a toggle to enable it."
• Frequency: Daily
• Users affected: 3

Template 3: Integration Request

Who it's for: SaaS tools with a growing integration catalog.

Fields:

• Tool name (text, required)
• Tool URL (url, optional)
• What data should sync (textarea)
• Direction (radio: One-way to us / One-way from us / Two-way)
• How urgent (radio: Would switch tools over this / Important / Nice to have)

Example fill:

• Tool name: Linear
• Tool URL: linear.app
• What data should sync: "Our feature requests should create Linear issues automatically with tag 'feature-request'."
• Direction: One-way from us
• How urgent: Important

Template 4: Admin / Settings Request

Who it's for: Tools with team / permission / billing settings.

Fields:

• Setting area (dropdown: Billing / Permissions / Team / Security / Other)
• Current behavior (textarea)
• Desired behavior (textarea)
• Who would use this (radio: Admins only / Members / Everyone)

Example fill:

• Setting area: Permissions
• Current behavior: "Any admin can change billing, which is risky."
• Desired behavior: "Let me create a role that has full access except billing."
• Who would use this: Admins only

Mobile App Templates (3)

Template 5: Mobile Feature Request

Who it's for: Consumer and B2B mobile apps on iOS and Android.

Fields:

• Title (text, required)
• Description (textarea, required)
• Platform (radio: iOS / Android / Both)
• App version (text, auto-filled if possible)
• OS version (text, auto-filled)
• Device (text, auto-filled)

Example fill:

• Title: "Dark mode follows system setting"
• Description: "Currently dark mode is a manual toggle in settings. Please make it follow the system dark mode."
• Platform: Both
• App version: 4.2.1
• OS version: iOS 18.3
• Device: iPhone 15

Template 6: Mobile Gesture / UX Request

Who it's for: Apps with swipe, pinch, long-press, or other touch-based UX.

Fields:

• Screen (dropdown of app screens)
• Current interaction (textarea, "What happens now when you...")
• Desired interaction (textarea)
• Video or screen recording (file, optional)

Example fill:

• Screen: Inbox list
• Current interaction: "Swipe left archives the email."
• Desired interaction: "Let me configure swipe actions, like swipe-left to snooze instead of archive."
• Video: [attached]

Template 7: Mobile Push Notification Request

Who it's for: Apps with notifications that need tuning.

Fields:

• Notification type (dropdown of existing types, plus "New type")
• Frequency problem (radio: Too many / Too few / Wrong timing / Wrong content)
• Desired behavior (textarea)

Example fill:

• Notification type: Daily summary
• Frequency problem: Wrong timing
• Desired behavior: "Let me pick the time of day the daily summary arrives instead of always 9am."

E-commerce Templates (3)

Template 8: Shopper Feature Request

Who it's for: DTC and marketplace e-commerce stores.

Fields:

• What you were trying to do (textarea)
• What got in your way (textarea)
• Page or flow (dropdown: Product page / Cart / Checkout / Account / Other)
• Order reference (text, optional, auto-filled if logged in)

Example fill:

• What you were trying to do: "Save three items to compare later."
• What got in your way: "No wishlist or compare feature exists."
• Page or flow: Product page
• Order reference: N/A

Template 9: Merchant / Seller Request

Who it's for: Marketplace platforms (Shopify-likes, Etsy-likes).

Fields:

• Role (radio: Seller / Buyer / Both)
• Feature area (dropdown: Listings / Orders / Payouts / Analytics / Customer Support)
• Description (textarea)
• Revenue impact (textarea, optional, "How would this affect your revenue?")

Example fill:

• Role: Seller
• Feature area: Analytics
• Description: "Show me which products are trending up in searches over the last 7 days."
• Revenue impact: "Would help me decide what to restock before running out."

Template 10: Checkout / Payment Request

Who it's for: E-commerce with complex checkout or payment needs.

Fields:

• Payment method requested (text)
• Region / country (text, optional)
• Order type (radio: Subscription / One-time / Both)
• Current friction (textarea)

Example fill:

• Payment method requested: Klarna
• Region: Germany
• Order type: One-time
• Current friction: "Most of my customers expect Klarna as an option at checkout here."

Agency & Client Templates (4)

Template 11: Client Change Request

Who it's for: Agencies and freelancers managing client projects.

Fields:

• Project (dropdown of active projects)
• Type (radio: New feature / Change existing / Bug / Question)
• Description (textarea)
• Deadline (date, optional)
• Budget approval (radio: In scope / Needs approval / Emergency)

Example fill:

• Project: Acme Website Redesign
• Type: New feature
• Description: "Add a French language version of the homepage."
• Deadline: 2026-05-15
• Budget approval: Needs approval

Template 12: Scope Clarification Request

Who it's for: Fixed-scope agency projects where scope creep is a risk.

Fields:

• Section of contract (dropdown: Phase 1 / Phase 2 / Out of scope)
• Your interpretation (textarea)
• Our interpretation (textarea)
• What you want to change (textarea)

Example fill:

• Section of contract: Phase 2
• Your interpretation: "Includes multi-language support."
• Our interpretation: "Phase 2 is English only, multi-language is Phase 3."
• What you want to change: "Can we move French into Phase 2 for an extra $3K?"

Template 13: Feedback on Deliverable

Who it's for: Design or development agencies sending client review requests.

Fields:

• Deliverable (dropdown: Mockup / Prototype / Staging / Live site)
• Screenshot with annotation (file, required for UI feedback)
• Description (textarea)
• Priority (radio: Must fix before launch / Should fix / Nice to fix)
• Approval status (radio: Approve / Approve with changes / Reject)

Example fill:

• Deliverable: Staging
• Screenshot: [annotated image of homepage hero]
• Description: "The hero headline is too small on mobile, and the CTA button doesn't stand out against the background image."
• Priority: Must fix before launch
• Approval status: Approve with changes

Template 14: Retainer Feature Request

Who it's for: Agencies on monthly retainer with ongoing work.

Fields:

• Project (dropdown)
• Hours estimate (if known) (number, optional)
• Urgency (radio: This sprint / Next sprint / Backlog)
• Business reason (textarea, "Why does this matter right now?")
• Depends on (text, optional, "Other tasks this blocks or requires")

Example fill:

• Project: Acme Marketing Site
• Hours estimate: 4
• Urgency: This sprint
• Business reason: "Launching a new campaign next week, need the campaign landing page live by Thursday."
• Depends on: Copy from marketing team (expected Tuesday)

How to Embed with Feedbask

Most of these templates take about 5 minutes to configure and embed.

Feedbask's widget supports custom fields, so you can build any of the 14 templates above without code. The basic flow:

1. Sign up at feedbask.com/auth.
2. Create a new Feature Request form from the feature voting tool dashboard.
3. Add the fields from the template you picked (title, description, priority, etc.).
4. Mark required vs optional, set character limits.
5. Copy the embed snippet, which looks like this:

<script src="https://cdn.feedbask.com/widget.js" data-board="your-board-id"></script>

Drop that into your site or app where you want the widget to appear, and it loads a "Feedback" button that opens the form. Public submissions show up on your public roadmap page where other users can vote.

For internal-only feedback (agency clients, beta testers), configure the board as private and gate it behind login. The same widget works for both modes.

If you need a bug report form instead of or alongside feature requests, the bug report widget uses the same template system with different default fields (environment, steps to reproduce, expected vs actual).

FAQ

How many fields is too many? Five is the sweet spot. Every field beyond that drops submission rates by roughly 10% based on common form analytics benchmarks. Title + description + priority is the absolute minimum that still gives you enough to triage.

Should I let users set priority themselves? Yes, as a signal. Don't treat user-reported priority as the final word, but "Blocking" vs "Nice to have" tells you a lot about whether the feature is table stakes or a wish.

Do I need a use case field? It's the highest-value optional field. Users skip it about 60% of the time, but the 40% who fill it in give you the context that actually decides whether to build.

What about duplicate detection? Most feedback tools (Feedbask, Canny, Featurebase) show similar existing requests as the user types the title, which cuts duplicates by roughly half. If your tool doesn't have this, add a short note above the form like "Search existing requests first."

Can I use these templates with Canny or Featurebase? Yes. The field structures are tool-agnostic. Any feedback platform with custom form fields can support all 14 templates, though UI and field types may differ slightly.

Should the form be public or gated? Gate it if you have signed-in users (less spam, easier attribution). Keep it public if you want prospects to submit too. For most B2B SaaS, gated works better.

Start with one template

Pick the template that fits your product, paste the fields into Feedbask, and ship it today. Sign up free or read more on the feature voting tool page. The first form takes 10 minutes. The hardest part is deciding which of the 14 templates above is the closest match.