Track Feature Requests in Salesforce
Capture requests on accounts and opportunities, and see the pipeline behind every idea.
On this page
To track feature requests in Salesforce, UserVoice offers two integrations: the Salesforce Connector syncs accounts, contacts, and revenue, and the Feedback & Opportunity Sidebar lets reps log product gaps on the opportunity. Each capture lands on the idea with the customer's words and the deal's name, amount, and stage. Ideas then show the open, won, and lost deals behind them, and reports such as Feedback on Lost Opportunities show the gaps behind closed-lost deals.
Two integrations, two jobs
Salesforce feature requests reach UserVoice two ways. Most teams use both.
| Salesforce Connector | Salesforce Feedback & Opportunity Sidebar | |
|---|---|---|
| What it does | Syncs accounts and contacts into UserVoice, with status, revenue, segment, and custom fields | Lets reps capture feedback on Salesforce records, tied to the opportunity |
| Direction | Salesforce to UserVoice, nightly | Both ways: opportunity name, amount, and stage come in; feedback and idea status go back |
| Install | Sign in to Salesforce from UserVoice. No package. | A managed package your Salesforce admin installs, plus a component on the opportunity page |
| You get | Accounts and revenue behind every idea | Open, won, and lost deals behind every idea |
Before you start
Line up three people and three permissions before you install.
| Who | What they need |
|---|---|
| A UserVoice admin | Full access in UserVoice, to link your Salesforce org and see the token |
| A Salesforce admin | Rights to install a managed package and edit the opportunity page layout |
| Your reps | A UserVoice contributor or admin seat that can enter feedback on behalf of customers |
- The sidebar depends on your UserVoice plan. Your UserVoice rep can confirm whether it's included.
- It works in Lightning and in Classic. Lightning uses a component on the page; Classic uses a UserVoice Feedback button.
- Connect the account sync too. The sidebar ties feedback to the deal. The Connector ties the customer to their account and revenue.
Only one CRM syncs at a time. If HubSpot is connected to UserVoice, disconnect it before you connect the Salesforce Connector.
Install the sidebar
The UserVoice admin and the Salesforce admin each have a part. It takes about half an hour together.
- In UserVoice: open the Salesforce Feedback & Opportunity Sidebar settings and select Link account. Enter your Salesforce organization ID (it starts with 00D). UserVoice shows a token.
- In Salesforce: install the UserVoice Connector managed package.
- Open the UserVoice Configuration page, enter the token and your UserVoice address, and select Save and Authorize.
- Edit the opportunity page in Lightning App Builder, and drag the UserVoice Feedback component onto it. Save and activate.
- Give your UserVoice admins the UserVoice Admin permission set, which shows the UserVoice setup tab.
Put the component where reps already look. Near the opportunity's key fields or activity, not at the bottom of a long page. A capture tool nobody sees doesn't get used.
Capture on the opportunity
After a call, the rep opens the opportunity and selects Capture Feedback on the UserVoice card.
- Customer's email. Filled in from the opportunity's contact roles. Pick the person who asked, or add someone new.
- Customer's feedback. What they asked for, in their words. Only your team sees it.
- Link to related idea. Search existing ideas, or create a new one with a title, forum, and category.
- Subscribe the customer to status updates on the idea, if they should hear when it moves.
- Save. The customer is counted as a supporter of the idea.
Flag what matters most. After saving, select Flag idea as important and say, in your own words, why it matters to this customer. Product sees the reason on the idea.
Search before you create. One idea with twelve deals behind it tells product something. Twelve near-duplicates, one per rep, tell it nothing.
What shows up in UserVoice
Each capture lands on the idea with its source, its customer, and its deal.
| Where | What you see |
|---|---|
| The idea's feedback | The customer's words, with Salesforce as the source and the opportunity's name and stage, such as Opportunity (Open) |
| Supporters → Opportunities | Every linked deal, with its status (open, won, or lost), amount, and when it was last linked, and a link to Salesforce |
| The idea grid | A Salesforce column group with Potential Revenue: the amount of open deals behind each idea |
| Supporters and accounts | The customer as a supporter. With the Connector, their account and revenue too |
- Stage follows Salesforce. When an opportunity's name, amount, or stage changes, UserVoice updates it.
- Each opportunity counts once per idea, however many people on the deal asked.
- Only opportunities with feedback come in. UserVoice doesn't copy your whole pipeline.
Potential Revenue isn't a forecast. It's the full amount of every open deal behind an idea, at any stage. Treat it as exposure, and keep forecasting in Salesforce.
What reps see in Salesforce
Feedback goes back to Salesforce as UserVoice Feedback records, kept current as the idea changes.
| Where | What reps see |
|---|---|
| The UserVoice card | Feedback already captured on this record, and the most-requested ideas |
| UserVoice Feedback related list | Each request on the opportunity, with the idea's title, status, and supporter count |
| Opportunity fields | A feedback count, and whether the deal has feedback, for list views and reports |
| UserVoice Feedback reports | Ready-made reports on feedback by opportunity, owner, and time, covered on the next page |
Tell reps when a gap ships. Run Feedback with Recent Status Updates each week, and send it to sales leaders. A gap that cost a deal last quarter is a reason to call back.
Report product gaps in your pipeline
Revenue operations and sales leaders can see which product gaps sit in open pipeline, and which ones cost closed-lost deals.
| You want to know | Where to look |
|---|---|
| Which gaps sit in open pipeline | The idea grid in UserVoice, sorted by Potential Revenue |
| Which gaps cost us deals | The Feedback on Lost Opportunities report, next to your closed lost reasons |
| Every gap across the pipeline | The Feedback on All Opportunities report |
| Which reps capture feedback | The Feedback by Opportunity Owner report |
| How gaps trend | The Feedback over Time report |
| What changed on the ideas | The Feedback with Recent Status Updates report |
Make product gap a closed lost reason. When a rep picks it, ask them to capture the request on the opportunity before they close it. Then the reason and the idea behind it travel together.
Accounts and the account sync
The sidebar is built around the opportunity. Accounts come from the Connector.
| You want | Do this |
|---|---|
| Requests tied to a deal | Capture on the opportunity. That's the only place the deal's amount and stage come along. |
| Requests tied to an account | Connect the Salesforce Connector. People are matched to accounts by email, and each idea shows the accounts and revenue behind it. |
| An account's full list of requests | Filter the Idea Status Board in UserVoice by the account, or ask the UserVoice agent. |
| Capture outside a deal | The component can sit on an account page too, but captures there aren't tied to a deal. The browser extension works anywhere, and the Slack, Zendesk, and Jira integrations capture from those tools. |
Try it with your AI assistant
1 of 4 prompts in the PDFAttach the PDF to Claude, ChatGPT, or another assistant, then paste:
Using the UserVoice guide I attached, write a one-page guide for our sales reps on when and how to capture feedback on a Salesforce opportunity. Ask me about our sales process first.
Three more prompts and the checklist are in the full guide. Get it by email →
Read next
Get the full guide
We'll email you the 11-page PDF. It adds two things that aren't on this page:
- A six-step checklist to put the guide into practice
- Four AI prompts for Claude, ChatGPT, or your assistant of choice, including one that uses the UserVoice MCP to work with your own feedback data
