Can Salesforce Feedback Management Replace a Dedicated Feature Request Tool
No, not as a straight swap. Salesforce Feedback Management is a survey product. It collects structured responses, maps scores back onto the Case or Account that triggered the survey, and layers Einstein Analytics on top so you can watch satisfaction trend over a customer's lifecycle. None of that is the same job as "someone asked for X, here's how many people, here's who." A feature-request tracker needs a record per distinct ask that multiple people can attach to and a count that goes up. Feedback Management's unit of storage is a response, not a request, and nothing rolls two differently-worded answers into one.
That distinction matters more than it sounds like, because the two systems look similar from a distance, both live inside Salesforce, both attach to Cases and Accounts, both cost real money on top of your Sales or Service Cloud license. The difference shows up the first time a feature request arrives as a paragraph of text in an open-ended survey answer instead of a clean field, which is most of the time.
What Feedback Management is actually built to do
Feedback Management shipped as an add-on layered onto Sales or Service Cloud, built around a record called Survey Subject that stores whatever makes a survey personal, a case number on a post-resolution CSAT survey, an account name on a renewal NPS survey. Salesforce Ben's comparison of Feedback Management against plain Salesforce Surveys lays out the rest of the shape: Response Field Mapping pushes survey scores back onto fields on the record that triggered the survey, so a CSAT score can land directly on the Case, and Customer Lifecycle Management overlays Einstein Analytics dashboards to track that scoring across Cases, Accounts, and Opportunities over time. It's a real analytics product, not a checkbox feature, and it comes with a real price: $42,000 a month, or $504,000 a year, on top of whatever Sales or Service Cloud already costs, per the same writeup.
The base Salesforce Surveys product it's layered onto caps out at 300 free responses before charging $300 per additional thousand, per the same writeup; Feedback Management bundles unlimited responses into that same annual fee. Two teams pay very different amounts for what looks like the same survey tool, depending on whether they need the Feedback Management add-on's volume and analytics or just a handful of NPS sends a quarter.
Where it stops looking like a request tracker
Everything above is built around scoring and routing responses to the record that generated them. Nothing in that architecture produces a backlog. Three specific gaps show up fast:
- Open-ended answers don't aggregate. A survey question like "anything we could do better?" produces free text on each response record. Six customers writing six versions of "let us export to CSV" stay six separate answers; nothing groups them into one themed ask with a count.
- There's no request object with a status. A feature-request tracker needs
New,Planned,Shipped, something a product team can filter by. Survey Subject and response records don't carry that; they carry whatever question and answer the survey asked, tied to whichever Case or Account it went out on. - A response belongs to one survey send, not a running request. The same customer asking for the same thing on two different surveys three months apart produces two disconnected response records, with no mechanism that says "this is the same ask as before."
SurveyVista's rundown of Salesforce survey limitations covers the mechanical edges that make this worse in practice: a 255-character cap per survey question, which forces long open-ended answers into a cramped box, and a mobile app that only gives read-only access to survey-related features, so a rep reviewing responses from a phone can't act on what they find. None of that is fatal on its own. Together, it means the honest way to read Feedback Management is a scoring and routing layer for structured questions, not a place a product team goes to see what customers are asking for and how often.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionThe renewal call where this became a real question
It came up on a QBR-prep call, not inside Feedback Management itself. Priya Desai handles customer success for a slice of the mid-market book at Fenwick Route, which sells dispatch and scheduling software to HVAC and plumbing contractors, and Fenwick runs quarterly NPS through Feedback Management on every account past a certain deal size.
The account executive on the call was prepping a renewal with a multi-location plumbing customer and remembered the customer's office manager asking, at some point, for a way to reassign a whole day's jobs across technicians at once. He wanted to confirm that before it went in the deck. Priya pulled up the account's NPS history and read through the open-text answers one at a time, because there's no way to search across accounts for a phrase. She found it, from April:
"would be great to move a whole day's jobs to a different tech all at once"
Nothing from that account since. Whether two or three other customers had typed some version of the same request into their own surveys, worded differently, wasn't something she could check without opening every response by hand, and the call started in eleven minutes.
That's the actual failure mode: a request can already be sitting inside Feedback Management's own data and still be effectively invisible, because the system was built to score satisfaction per account, not to notice that several people are describing the same missing feature in different words.
The build that would fix it, and what it costs to add
The fix looks like the same custom-object pattern that works for Cases: a Feature_Request__c object with a status field, a junction table so one request can attach to more than one account, and a Flow that lets a rep or CS person log a request from whatever record they're on, including one prompted by a survey response. We've walked through that exact build, fields and Flow logic included, in how to track feature requests natively in Salesforce without a third-party tool. Feedback Management doesn't replace that work; if anything it adds one more source, survey responses, that someone has to remember to read and manually promote into the request object, on top of the Cases and Chatter notes that already need the same treatment.
That's a second custom build, paid for and maintained separately from Feedback Management's own $504,000-a-year license, to solve a problem Feedback Management's pricing page doesn't claim to solve in the first place. The gap in native Salesforce feature-request tracking generally, not specific to survey tools, is worth reading in full at why doesn't Salesforce have a native feature request tracker; Feedback Management doesn't close that gap, it just adds a fourth place requests can land unread.
Where this actually stops working
For a team running the occasional CSAT survey with mostly numeric ratings and a light touch of open text, none of this matters much: read the handful of comments each quarter, act on what's obvious, move on. It stops being manageable once a company runs surveys at real volume across many accounts, because that's exactly when open-ended answers stop being something one person can hold in their head, and exactly when the same request starts showing up worded three different ways across three different response records with no link between them.
That's the layer Modem sits at. Instead of asking a CS lead to reread every open-text survey answer looking for repeated themes, Modem reads feature requests as they show up across Slack, support tickets, call transcripts, and yes, survey free text, matches differently-worded versions of the same ask to each other, and attaches the account and contact behind each one using Salesforce account and opportunity context it reads, not writes, through the same records Feedback Management scores. It isn't a survey tool and doesn't compete with Feedback Management on NPS or CSAT measurement; it picks up the counting and deduping job that measurement layer was never built to do. Modem is our product, so weigh that against your own volume before treating this as settled, and if you're comparing more than one way to connect feedback to Salesforce data, the best tools to connect customer feedback to Salesforce lays out the alternatives side by side.
What to check this week
Pull the last quarter of open-ended NPS or CSAT answers out of Feedback Management and read them as a batch instead of one at a time. If the same ask shows up more than once in different words, that's the signal Feedback Management isn't built to surface on its own, and it's the concrete test for whether this gap is costing your team anything yet.
