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
- Use Choices for single selection only
- Use Checkbox for a single yes/no option
- Use Text for free-form input
Configuration Options
| Option | Description | Type | Default | Example |
|---|---|---|---|---|
key | Unique identifier | String | Required | services_required |
name | Display label | String | Required | ”Services Required” |
description | Help text for users | String | Optional | ”Select all services you need” |
ai_description | Hint for Intelligence | String | Optional | ”Which services the customer selected” |
options | Array of available options | Array | Required | See below |
min_selections | Minimum selections required | Number | 0 | 1 |
max_selections | Maximum selections allowed | Number | None | 3 |
visibility | Display setting | String | always-visible | hide-when-empty |
section | Section this field belongs to | String | None | Section UUID |
Options Configuration
Each option in theoptions array:
| Property | Description | Type | Required | Example |
|---|---|---|---|---|
value | Internal value stored | String | Yes | health_insurance |
label | Display text shown to user | String | Yes | ”Health Insurance” |
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 selectionsmax_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
| Configuration | Use Case |
|---|---|
min: 1 | ”Select at least one” |
min: 1, max: 3 | ”Select 1-3 options” |
min: 0 | Optional selections (default) |
max: 5 | Limit selections |
Stored Values
Multiple Choice fields store an array of selected values: Example stored data:AI Descriptions
AI descriptions help Intelligence extract multiple selections from documents. For Multiple Choice fields: Be specific about:- What the selections represent
- Where options typically appear (checkboxes, lists, categories)
- How they’re labeled in documents
- The context for the selections
| Field | AI Description |
|---|---|
services_required | ”Which insurance and financial services the customer has selected or expressed interest in, typically shown as checked boxes or listed items in the application” |
required_documents | ”Which documents are listed as required for this application or case, often shown in a document checklist or requirements section” |
coverage_types | ”Types of insurance coverage selected, such as liability, property, health, etc., typically listed in the coverage section or policy summary” |
affected_areas | ”Which areas, departments, or categories are affected by this claim or request, usually listed in the impact assessment section” |
Multiple Choice in Automations
Multiple Choice fields enable conditional logic based on selections: Check if specific option selected:- Show additional steps for specific services
- Route to specialist based on selections
- Calculate pricing based on options selected
- Send targeted information based on interests
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
- Labels should be self-explanatory
- Avoid jargon or abbreviations
- Be consistent with terminology
- Use
min: 1when at least one selection required - Use
maxto prevent over-selection - Most use cases don’t need max limit
- “Services Required” → clear what to select
- “Select Your Preferences” → action-oriented
- Avoid vague labels like “Options”
- Use short, technical values (
life_insurance) - Use friendly, readable labels (“Life Insurance”)
- Values are used in code, labels shown to users
- Usually best to have no defaults
- Let users make explicit choices
- Pre-selecting can create unwanted selections
Related Field Types
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