Not included in your plan? Want to learn more about the benefits? Leave us a message! If you're viewing this on our Help Center, click the Support bubble in the lower-right of this page.
Custom questions let you collect extra details when ideas are submitted through the Contributor Extension. They’re answered by your internal team (contributors and admins), not your end users. So whenever someone captures feedback on a customer’s behalf, they also record the context your team needs: who the customer is, how much it matters, and what problem they’re trying to solve.
Setting up Custom Questions
Admins need the “Edit account settings” permission to create or edit them.
Every custom question is tied to a custom field. When you turn on “Make this a question” for a field, contributors see it as a question in the extension. Their answer is saved to that field on the idea.
Creating Custom Fields
- Open your Custom Fields settings in one of two ways:
- From the Idea Grid: click the settings icon in the top-right corner and select Custom Fields.
- From Settings: click the icon in the bottom-left corner, select General Settings › Ideas, then click Configure next to Custom Fields.
- Create a new custom field, or edit an existing one.
- In the dialog, click Enable next to Make this a question.
- Enter the question as you’d like contributors to see it.
- Choose whether the question is Optional or Required, then save.
Edit Custom Questions
Editing and deleting custom questions are done so through their Custom Field.
- To change the wording or the required/optional setting, edit the custom field.
- To remove the question from the extension, turn off “Make this a question” or delete the custom field. Remember that deleting a custom field cannot be undone.
Using Custom Questions
When a contributor creates an idea with the Contributor Extension, they’ll go through two steps:
- Idea details: Title, Forum, Category, and Description.
- Additional idea fields: your custom questions. Required questions must be answered before the idea can be submitted.
Best Practices
- Write questions for the person entering the feedback. Your contributor is the one answering, so word questions the way they’d think about them, for example “How critical is this for the customer?” rather than “How critical is this for you?”
- Ask what only the contributor knows. Your team member just talked to the customer, so ask for context that’s easy to lose later: the problem the customer is trying to solve, how they’re working around it today, how urgent it is, and whether it’s tied to a renewal or a deal. If an idea needs your product team’s attention, contributors can also flag it as important and add a reason.
- Skip details UserVoice already has. If the customer’s account, ARR or segment comes in automatically, don’t ask for it again. Focus on what has to be entered by hand.
- Prefer drop-downs and yes/no fields over free text. Picking an answer is quick between calls, and structured answers are easy to filter and report on.
- Make only the essentials required. Contributors log feedback during busy days. One or two required questions keep entries consistent without slowing them down.
- Use Admin Select to route ideas. Let contributors tag the CSM or product owner so the right person is notified right away. If routing always follows the same pattern, you can skip the question and have owners assigned automatically by forum and category instead. Learn more in Idea Assigned Owner.
- Align with your sales and support teams. Pick questions that match the details they already gather in tickets and calls, so filling them in feels natural.