These entities let users make selections — from a simple yes/no to searching a database. They are essential for branching logic, personalization, and helping users feel in control of their journey.

​
Choice

Choice

When to use: Product preferences, service selection, insurance coverage
What users see: A list or grid of options. Can be single or multi-select.
Tips:
  • Keep option text short and clear
  • Add icons or images to make options more engaging
  • Offer “Other” or “None of the above” where needed

​
Boolean

Boolean

When to use: Yes/No questions, consent forms, simple eligibility checks
What users see: A toggle, button, or checkbox with two clear options
Tips:
  • Use specific labels (e.g. “I agree” instead of “Yes”)
  • Avoid double negatives
  • Make consequences clear (what happens if they choose yes/no)

​
Autocomplete

Autocomplete

When to use: Searching large lists like companies, cities, or categories
What users see: A search box that suggests options as they type
Tips:
  • Works best when there are many possible options
  • Always provide a fallback message like “No results found”
  • Use for external data sources like company lookup or address search

​
Best Practices

  • Keep it simple: Don’t overload users with too many choices at once
  • Guide the flow: Use responses to show only what’s relevant next
  • Be consistent: Style options the same way across your flow
  • Think mobile: Use large tap targets and simple layouts

​
Example Recipes

Consent form
Message → Boolean (Agree to terms) → Continue Service selection
Message → Choice (Select service type) → Redirect to relevant flow Company lookup
Message → Autocomplete (Search company) → Prefill details → Continue