Skip to main content

Multi Select Responses

Multi select responses allow reviewers to choose multiple options from a predefined list, making them ideal for identifying multiple issues, categorizing content across several dimensions, or conducting comprehensive audits where multiple aspects need evaluation.

When to Use Multi Select

Multi select responses are perfect for:

Issue Identification

Identifying multiple problems or violations where content might have several issues simultaneously

Content Categorization

Tagging content with multiple categories, departments, or attributes that aren’t mutually exclusive

Audit Checklists

Quality assurance workflows where multiple criteria need to be verified or flagged

Feature Analysis

Evaluating multiple aspects or features of content, products, or submissions

Configuration Formats

Multi select responses support two different formats for the options array. Choose based on your needs:
Both formats work identically - choose based on your preference. The API automatically transforms simple strings to rich objects for mobile app compatibility. Response data is always an array of selected values.

Configuration Options

Required Parameters

array
required
Array of options (1-20 options maximum). Can be simple strings or SelectOption objects.

Optional Parameters

integer
default:"0"
Minimum number of options that must be selected (defaults to 1 when max_selections is provided)
integer
Maximum number of options that can be selected (required for multi-select)
boolean
default:"false"
Whether at least one selection is mandatory for completion

Implementation Examples

Content Violation Detection

Identify multiple policy violations in a single review:

Product Quality Assessment

Evaluate multiple aspects of product quality:

Customer Service Ticket Categorization

Categorize support tickets across multiple dimensions:

Response Format

When a reviewer selects multiple options, you’ll receive an array of the selected values:

Use Case Examples

1. Content Moderation Review

2. Quality Assurance Checklist

3. Feature Request Analysis

Validation and Error Handling

Automatic Validation

The mobile app automatically validates multi select responses:
  • Option validation: Ensures all selected values exist in the options array
  • Selection limits: Enforces min_selections and max_selections constraints
  • Required validation: Prevents submission when required=true and no selections made
  • Duplicate prevention: Prevents selecting the same option multiple times

Processing Validation

Your application should validate received responses:

Best Practices

Option Design

  • Organize options by category or theme when possible
  • Use similar language patterns for related options
  • Consider visual grouping with colors for option categories
  • Order options from most to least common/important
  • Ensure options are mutually non-exclusive unless intended
  • Use descriptive labels that clearly differentiate choices
  • Include descriptions for options that might be ambiguous
  • Avoid overlapping categories that confuse reviewers
  • Set max_selections to prevent analysis paralysis
  • Use min_selections to ensure meaningful evaluation
  • Consider cognitive load - too many options reduce decision quality
  • Test limits with actual reviewers to find optimal ranges
  • Use colors strategically to indicate severity or category
  • Red/orange for problems, green for positive attributes
  • Consistent color coding across similar request types
  • Consider accessibility with color-blind friendly palettes

Processing Best Practices

Common Patterns

Issue Escalation Matrix

Quality Scoring System

Next Steps

Rating Responses

Learn about numeric rating scales for quality assessment

Single Select Responses

See how to implement mutually exclusive decision workflows

Response Processing

Advanced patterns for handling and analyzing response combinations

Mobile Experience

See how reviewers interact with multi select responses on mobile