Custom Questions That Make Ideas Actionable

Choosing, configuring, and scoping the questions you ask when ideas are submitted.

On this page

    Custom questions in UserVoice add a short, structured set of prompts to the idea form, so each idea arrives with the context your team needs to evaluate it: who is asking, how much it matters, and what problem sits behind it. Each answer is saved to a custom field on the idea, where it can be filtered, segmented, and reported on. You choose the wording, whether it's asked internally, on the portal, or both, and which forums use it. Only the person who posts the idea answers.

    What custom questions are

    A custom question is a custom field on ideas that you choose to ask at the moment an idea is created. The answer is saved to that field on the idea, so it can be filtered, segmented, and reported on like any other field.

    Each question has six settings

    Question text

    The wording people see on the form. If you leave it blank, the field name is shown.

    Where it is asked

    Internally (the browser extension, the contributor console, and the admin console), on your public portal, or both.

    Required or optional

    Optional questions are labeled “(optional)” on the portal form.

    Answer visibility

    Private (the default) or public.

    Forums

    All forums, or only the forums you select.

    Order

    The position of the question on the form.

    Who answers

    Only the person who posts the idea answers. People who vote on it later are not asked, so each idea gets one set of answers. To hear from everyone who supports an idea, such as when you recruit beta testers, post a status update with Email ticked; supporters who are still subscribed receive it.

    Why use custom questions

    A description tells you what someone wants. It rarely tells you how much it matters, who it matters to, or whether it duplicates something you already know about. Custom questions close that gap at the point of capture, when the submitter has the context and is most willing to share it.

    Better prioritization

    Structured answers turn a pile of free-text ideas into something you can sort. Asking how often someone hits the problem, what they do instead, or what their role is gives every idea the same context, without following up on each one.

    Less follow-up

    Product managers often spend their first interaction with a new idea asking the same clarifying questions. Asking them on the form means the answer is already there when the idea is triaged.

    Segmentation you can trust

    Answers live in custom fields, so they work everywhere fields work: filters, views, exports, and reports. A select question such as “Which platform are you using?” produces clean data. The same question as free text produces a dozen spellings of the same answer.

    Consistent intake from internal teams

    Sales, Success, and Support teams submit feedback on behalf of customers. Internal questions make sure that feedback carries the deal, renewal, or escalation context your team needs, in the same shape every time.

    What types of questions to ask

    Start from the decision you want to make, then work back to the question. If you cannot name what you would do differently with the answer, leave the question out.

    Question formats

    Structured formats (select, yes/no, number) are easier to filter and report on than text.

    FormatBest forExample
    Single select (dropdown)One answer from a fixed list; the best default for anything you will segment byWhich platform are you using?
    Multi-selectSeveral answers that can all applyWhich teams would use this?
    Yes / NoA simple qualifierDoes this block your work today?
    Short textA brief answer up to 255 charactersWhat are you using as a workaround?
    Long textContext that does not fit a listDescribe the outcome you are hoping for.
    Number or dollar amountVolume, size, or valueRoughly how many users are affected?
    DateDeadlines and timingWhen do you need this by?
    Link (URL)A reference the team can openLink to a screenshot, recording, or ticket

    Fields of the Assign admin type are internal-only and cannot be asked as questions.

    Check first

    Read your recent ideas before you choose. For 30–50 recent ideas, note what you would need to ask before acting on each. The gaps you see most often point to your questions. For a new forum, start with the questions below and review after a month.

    Questions that tend to earn their place

    • Frequency. “How often do you run into this?” with Daily, Weekly, Monthly, Rarely, and “It’s a one-time need,” so requests for a missing capability have an honest answer.
    • Workaround. “What do you do today instead?” as short text. A painful workaround is a strong signal.
    • Platform. A single select such as Web, iOS, Android, or API, when your product runs on more than one.
    • Role or team. Who is asking, when your portal serves several kinds of users.
    • Business context (internal only). Deal stage, renewal date, or escalation, for feedback logged by customer-facing teams.

    Questions to avoid

    • Anything your system already knows, such as the submitter's company, plan, or revenue. UserVoice already ties ideas to users and accounts.
    • Questions that repeat the idea description, such as “Describe your idea in more detail.”
    • Leading questions, such as “How much would this feature improve your experience?”
    • Free text where a list would do. If you expect a small set of answers, make it a select.
    • What the idea is about, such as product area or feature. Forum categories already group ideas that way, and a question would duplicate them.
    • How important the idea is to the person. Turn on Importance instead: it asks “How important is this to you?” on the idea itself, so you get a score from everyone who views it, not only the person who posted it.

    Should questions be required?

    Make a question required only when an idea is not useful to your team without the answer. Every required question is a reason for someone to abandon the form, and a forced answer is often a low-quality one.

    Make it required whenKeep it optional when
    Your triage or routing depends on the answer (for example, platform)The answer is nice context but not needed to act
    The answer is quick to give: a select or yes/noThe answer takes thought or research to write
    The audience is internal and the question is part of an agreed processThe audience is public portal users giving feedback voluntarily
    Rule of thumb

    Start with none. Make a question required only when your triage or routing cannot happen without it. On the portal, require at most one question, and make it a select. The fewer ideas a forum receives, the more each required question costs you. Internal submitters can carry more required questions, because the question reflects a process they have agreed to follow.

    Spam

    Required questions don’t stop spam. Spammers fill in fields like anyone else, so a required question only adds effort for genuine submitters.

    Should answers be visible?

    Each question's answers are either private or public.

    🔒 Private · default

    Only the person who submitted the idea and your team can see the answer. On the portal form, the question shows a Private label and the note “Only you and the [your company] team can see this answer.”

    Public

    The answer is shown on the idea to everyone who can see the idea.

    Keep answers private when

    They could include anything sensitive: business impact, revenue, internal tools, company names, or workarounds that expose how a customer operates. People also answer more candidly when they know only your team will read it.

    Make answers public when

    They help other visitors understand or find the idea, such as the platform it applies to. A public answer can also encourage voters to recognize an idea as theirs and add their support.

    Default

    When in doubt, keep answers private. You can make a question public later; once an answer has been shown publicly, making it private again does not undo what was already seen.

    How many questions to ask

    Fewer than you think. Every question adds effort to submitting an idea, and the people with the most useful feedback are often the least patient with forms.

    Public portal
    1–3

    Visitors are volunteering their time; a short form keeps submission rates up.

    Internal teams
    3–5

    Submitters are logging feedback as part of their job and can supply more context.

    Order

    Put the most important question first. If you find yourself wanting a sixth question, look at the answers you already collect and remove one that nobody filters or reports on.

    Tailoring questions by forum

    Questions can apply to all forums or only to the forums you choose. Use this to match the questions to the people and the kind of feedback each forum collects.

    When to scope a question to specific forums

    Different audiences

    A customer forum and a partner forum need different context. Ask partners which of their customers is affected; ask customers about their own workflow.

    Different products

    A platform question only makes sense when its options match the product the forum covers.

    Internal-only forums

    A forum used by your own teams can carry business context questions that would be out of place on a public forum.

    Beta or early-access forums

    Ask about the release or build being tested, and keep that question off your main forum.

    Keep shared questions consistent

    When a question applies to several forums, use one question for all of them rather than a near-copy per forum. One field means one set of answers you can report on together.

    Example setup

    ForumQuestionsRequiredVisibility
    Customer feedback (public portal)Platform; FrequencyPlatform onlyPlatform public, Frequency private
    Partner feedbackAffected customer; WorkaroundAffected customerPrivate
    Internal feedbackDeal or renewal context; WorkaroundDeal or renewal contextPrivate

    If your forum categories already split ideas by platform, skip the Platform question; categories already capture it.

    When you add or remove a forum

    A question set to all forums appears on a new forum as soon as the forum exists. A question limited to specific forums does not appear until you add the new forum to it. Before you open a new forum to submitters:

    1. Review every all-forums question and confirm it fits the new forum’s audience. If one does not, limit it to the forums where it belongs.
    2. Add the new forum to each limited question that should be asked there.
    3. Check the order of the questions the new forum will show, and that no more than one is required on a public forum.
    4. Submit a test idea on the new forum, from the portal and from your internal tools, and confirm the form shows what you expect.
    Watch out

    Deleting a forum can widen a question. If a question was limited to only the forum you delete, it applies to every forum afterwards. Review your questions after deleting a forum, and limit or turn off any that shouldn’t appear everywhere.

    Try it with your AI assistant

    1 of 4 prompts in the PDF

    Attach the PDF to Claude, ChatGPT, or another assistant, then paste:

    Using the UserVoice MCP, read the last 50 ideas in [forum], including their full descriptions, and note what context they're missing (read only). Then, using the UserVoice guide I attached, suggest two or three custom questions with a format for each that would fill those gaps. Ask me what decisions we make with feedback first.

    Three more prompts and the checklist are in the full guide. Get it by email →

    Free, by email

    Get the full guide

    We'll email you the 12-page PDF. It adds two things that aren't on this page:

    • A nine-step checklist to put the guide into practice
    • Four AI prompts for Claude, ChatGPT, or your assistant of choice, including ones that use the UserVoice MCP to work with your own feedback data
    Cover of Custom Questions That Make Ideas Actionable guide from UserVoice