Skip to main content
The Multiple Choice field allows users to select multiple items from a predefined list of options. This field type displays as a checkbox group where users can check any combination of the available options. Use Multiple Choice fields when you need to collect multiple selections from a fixed set of possibilities — services required, features selected, categories, interests, or any scenario where “select all that apply” is appropriate.

When to Use

Use Multiple Choice fields for:
  • Services or products selected
  • Features or options enabled
  • Categories or tags
  • Interests or preferences
  • Coverage types or insurance products
  • Document types required
  • Affected areas or departments
  • Applicable regulations or requirements
Consider alternatives:
  • Use Choices for single selection only
  • Use Checkbox for a single yes/no option
  • Use Text for free-form input

Configuration Options

Options Configuration

Each option in the options array:

Examples

Services Selection

Allow multiple service selections:

Document Types

Select required documents:

Coverage Areas

Select applicable coverage:

Validation

Multiple Choice fields enforce selection validation:

Selection Count

  • min_selections - Minimum required selections
  • max_selections - Maximum allowed selections
  • User must select within range to proceed

Option Validation

  • User can only select from predefined options
  • No free-form input
  • Ensures data consistency
Common configurations:

Stored Values

Multiple Choice fields store an array of selected values: Example stored data:
Empty state:
This format enables easy checking in automations and data processing.

Multiple Choice in Automations

Multiple Choice fields enable conditional logic based on selections: Check if specific option selected:
Check if any selection made:
Check if multiple selections:
Trigger based on selection:
  • Show additional steps for specific services
  • Route to specialist based on selections
  • Calculate pricing based on options selected
  • Send targeted information based on interests
Learn more about Automations →

Best Practices

Keep option lists focused:
  • 3-8 options is ideal
  • More than 12 options becomes overwhelming
  • Group related options logically
  • Order by frequency of use or alphabetically
Use clear labels:
  • Labels should be self-explanatory
  • Avoid jargon or abbreviations
  • Be consistent with terminology
Consider min/max:
  • Use min: 1 when at least one selection required
  • Use max to prevent over-selection
  • Most use cases don’t need max limit
Name the field as a question:
  • “Services Required” → clear what to select
  • “Select Your Preferences” → action-oriented
  • Avoid vague labels like “Options”
Value vs Label:
  • Use short, technical values (life_insurance)
  • Use friendly, readable labels (“Life Insurance”)
  • Values are used in code, labels shown to users
Default selections:
  • Usually best to have no defaults
  • Let users make explicit choices
  • Pre-selecting can create unwanted selections

Choices

Use for single selection from options

Checkbox

Use for single yes/no option

Text

Use for free-form input without predefined options

Data Schema Overview

Back to Data Schema overview