Feature Request Management

Every feature request, counted once.

Requests arrive through support, sales, Slack and your portal. Murmur gathers them in one place, merges the duplicates, attaches the revenue and keeps every requester in the loop.

Start for freeSee live demo
Dedupe as customers typeAutopilot on every plan
Feedback boardAutopilot NEWAOLBMC
All boards TrendingTopNew
  • 31

    Google Sheets as a data source

    Integrations 12

  • 24

    Dark mode for dashboards

    Feature requests 9

  • 17

    Weekly email digest of top changes

    Feature requests 6

  • 11

    Timezone-aware scheduled reports

    Reporting 4

3 new from Discord & email

Capture feedback
The problem

Sound familiar?

If any of these ring a bell, you’re in good company. They’re the three problems small teams run into first.

01

Requests live in ten places

A ticket here, a Slack thread there, a note in the CRM. Nobody can say how many customers asked for the same thing.

02

Duplicates hide real demand

The same idea split across five posts looks like five small asks instead of one big one. The real priorities get buried.

03

Requesters never hear back

You shipped it three months ago. The customer who asked still thinks you ignored them, and says so at renewal.

The Murmur way

How Murmur handles feature requests

One board, honest counts and a loop that closes itself.

Email · from maya@ — Pro plan

09:14

“Loving it so far. If I could share a dashboard with a client without a login, I’d move the whole agency over.”

Autopilot extracted

Public share links for dashboards

SharingPaying customerNew request
AcceptMerge into…
Step 01

Capture from wherever customers speak

Customers post on your portal or in-app widget. Your team logs requests from calls in two clicks. Autopilot fills in the rest from forwarded emails and pasted notes, plus Slack and Discord on Team.

  • Widget, portal and API (Team)
  • Vote on behalf with priority
  • AI captures on every plan

Create a post

Connect a spreadsheet

Looks similar to

94%

Google Sheets as a data source

Vote · 31
71%

CSV import on a schedule

Vote · 6
Markdown supportedPost anyway
Step 02

Merge duplicates without losing anyone

Murmur suggests similar posts as people type and points your team to likely matches. Merging carries every vote and voter across, so they all hear when it ships.

  • Similar posts suggested as you type
  • Merging carries every vote and voter
  • Old post links to the new one

Something you asked for just shipped

Lumen · to maya@ — voted in March

Hi Maya — Google Sheets as a data source, which you asked for in March, is live in your workspace today.

CompleteRead the changelog
Step 03

Close the loop on every request

When status changes, voters hear about it. When it ships, they get a personal note and a link to the changelog. No list exports, no forgotten follow-ups.

  • Status emails on Solo & Team
  • Changelog entries linked to posts
  • Changelog in your in-app widget
Workflow

A request’s journey in Murmur

  1. 01

    Captured

    From the portal, widget, a teammate or Autopilot.

  2. 02

    Matched

    Merged into an existing post or created fresh.

  3. 03

    Prioritized

    Scored on votes, revenue and effort.

  4. 04

    Shipped & announced

    Status emails and a changelog entry go out.

A feature request isn’t done when it ships. It’s done when the person who asked finds out.
How we think about feature request management
Related features

Features that make it work

AI Feedback ManagementAutopilot captures, dedupes and routes feedback for you.Collect FeedbackBoards, widgets and a branded portal for every voice.Share UpdatesChangelog and status emails that close the loop.

Give every request a home.

Import from Canny or a CSV in minutes. Re-running an import never creates copies.

Start freeSee the live demo