Multiple Choice

The Multiple Choice question type is used to present a set of predefined options from which the participant can select one or more responses. It supports both single selection (radio button or dropdown) and multiple selection (checkbox or tap-based UI).


Purpose

This question type is ideal for:

  • Capturing structured feedback
  • Offering mutually exclusive choices (e.g., satisfaction level, product category)
  • Allowing multiple responses (e.g., service channels used)
  • Driving logic or branching based on specific selections

Configuration Options

  1. Options Setup

    • Define Labels (visible to users)
    • Assign Values (numeric or text, used for logic/analytics)
    • Add Short Codes (optional internal identifiers for API exports or filters)
  2. Display Style
    Choose how the options are displayed:

    • Radio Buttons – single selection (inline or stacked)
    • Checkboxes – multi-selection
    • Dropdown – single selection with compact UI
    • Tap Options – large buttons, ideal for touch interfaces
  3. Selection Type

    • Single Select – allows only one option to be selected
    • Multi Select – enables selection of multiple options
  4. Default Answer
    Pre-select one or more options based on survey logic or typical defaults.

  5. Random Order
    Shuffle the display order of choices for each participant to avoid bias.

  6. Pre-populate
    Use embedded participant data to auto-fill options dynamically (e.g., location, segment).

  7. Reset Options
    Use “DELETE ALL OPTIONS” if you want to clear the current list and start again.


Question Settings (Advanced)

These additional toggles in Zykrr’s editor enhance analytics, personalization, and automation:

Setting Function When to Use
Require an answer Prevents participants from skipping the question Core demographic or screening questions
Location question Captures geo-data (city, state, country) Mapping, regional analysis, or routing logic
Response tag question Tags each selection for downstream filtering Segmentation by channel, e.g., tagging “Email” vs. “SMS”
PLM reverse-feed question Sends responses into product-lifecycle workflows Syncing survey inputs to defect or PLM tools
Demographics question Flags question for profile grouping in reports Age, gender, income, and other standard demographic items
Dimension Adds responses as filters in Segment-Score dashboards Slice NPS/CES/CSAT by this attribute
Show in NPS Distribution Includes responses in the NPS® report view Define sub-groups within NPS analysis
Satisfaction-score question Treats options as satisfaction levels and calculates average score Questions where each choice reflects a satisfaction rating
Distribution-mode question Maps choices to delivery channels (e.g., e=Email, s=SMS, w=WhatsApp) Automate communication follow-up based on selection
Language-controller question Dynamically sets survey language based on response Multi-lingual surveys where language is participant-controlled
Hidden in Zykrr Insights escalation/response popup Stores metadata without showing in popups Internal fields required for backend logic but not relevant to the UI

How to Configure in Zykrr

  1. Input the Question Text
    Example: “How would you rate your experience with our product?"

  2. Add Options

    • Manually add each label, value, and short code
    • Or use “ADD OPTIONS IN BULK” to paste a list in tabular form
  3. Choose Display Style

    • Example: select “Dropdown” for compact UX
  4. Adjust Behavior

    • Enable Multiple Selections if required
    • Set a Default Answer (optional)
    • Enable Random Order to reduce selection bias
  5. Advanced Settings

    • Enable any applicable Question Settings to support data analysis, segmentation, or automation as per your use case

Example

Question:
“How would you rate our service?”

Options:

  • Good (value = 1, code = G)
  • Bad (value = 2, code = B)

Display Style Examples:

  • Dropdown
  • Radio Buttons
  • Checkboxes
  • Tap (mobile-friendly)

Best Practices

  • Keep labels short and clear
  • Avoid overlapping meanings between options
  • Randomize only when option order doesn’t imply hierarchy
  • Use pre-population carefully to avoid anchoring responses
  • Leverage advanced settings to drive smarter analytics and personalization

This is part of the Question Types Guide in Zykrr’s Documentation Hub.
For assistance configuring logic, styling, or custom data integrations, contact support@zykrr.com.