Boolean Responses
Boolean responses provide the simplest form of human decision-making: true or false, yes or no, approve or reject. With customizable labels and colors, they’re perfect for binary decisions that don’t require complex analysis or multiple options.When to Use Boolean Responses
Boolean responses are ideal for:Simple Approvals
Basic approve/reject workflows, go/no-go decisions, or binary authorization processes
Binary Classification
Categorizing content as compliant/non-compliant, safe/unsafe, or valid/invalid
Feature Flags
Enabling or disabling features, settings, or capabilities based on human judgment
Quick Verification
Fast verification tasks where detailed analysis isn’t needed, just confirmation or denial
Configuration Options
Boolean responses support custom labeling and visual styling for both true and false states:Optional Parameters
string
default:"True"
Display text for the true/yes option (max 100 characters)
string
default:"False"
Display text for the false/no option (max 100 characters)
string
default:"#16a34a"
Hex color code for the true option visual styling
string
default:"#dc2626"
Hex color code for the false option visual styling
boolean
default:"false"
Whether a decision is mandatory for completion
Implementation Examples
Content Approval Workflow
Simple approve/reject decision for content moderation:Security Threat Assessment
Binary risk evaluation for security incidents:Feature Release Decision
Go/no-go decision for feature deployment:Response Format
When a reviewer makes a boolean decision, you’ll receive both the boolean value and associated label:Use Case Examples
1. Content Moderation
- Configuration
- Sample Response
- Processing
2. Financial Transaction Verification
- Configuration
- Sample Response
- Processing
3. System Health Monitoring
- Configuration
- Sample Response
- Processing
Validation and Error Handling
Automatic Validation
The mobile app automatically validates boolean responses:- Type validation: Ensures response is exactly true or false
- Required validation: Prevents submission when required=true and no selection made
- Null prevention: Blocks null, undefined, or empty responses
Server-Side Validation
Your application should validate received boolean responses:Best Practices
Label Design
Make Labels Action-Oriented
Make Labels Action-Oriented
- Use active verbs: “Approve Content” vs “Content is Good”
- Be specific about consequences: “Block Transaction” vs “No”
- Include outcomes: “Publish Article” vs “Yes”
- Consider what happens next: “Schedule Meeting” vs “Agree”
Use Visual Indicators
Use Visual Indicators
- Add emojis for quick visual recognition (✅❌🚨⚠️)
- Choose appropriate colors (green for positive, red for negative)
- Maintain consistency across similar decision types
- Consider colorblind accessibility with emojis/text
Balance True/False Options
Balance True/False Options
- Make both options equally clear and understandable
- Avoid biased language that pushes toward one choice
- Ensure both options are valid business outcomes
- Test label clarity with actual reviewers
Context-Appropriate Wording
Context-Appropriate Wording
- Match tone to the severity (formal for legal, casual for features)
- Use domain-specific language when appropriate
- Consider cultural differences in yes/no interpretation
- Keep labels concise but descriptive (under 50 characters ideal)
Processing Best Practices
Clear Branching Logic
Clear Branching Logic
Defensive Default Values
Defensive Default Values
Audit and Analytics
Audit and Analytics
Common Patterns
Progressive Decision Making
Consensus Building
A/B Testing Integration
Next Steps
Response Types Overview
Compare all six response types and choose the right one for your use case
Single Select Responses
When you need more than two options, upgrade to single select
Response Processing
Learn advanced patterns for handling and analyzing boolean decisions
Mobile Experience
See how reviewers interact with boolean choices on mobile devices