> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wizflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choices & Decisions

> Entities that let users make selections and guide the flow of your chatflow

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

<CardGroup cols={2}>
  <Card title="Choice" icon="list">
    **When to use:** Product preferences, service selection, insurance coverage\
    **What users see:** A list or grid of options. Can be single or multi-select.
  </Card>
</CardGroup>

**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

<CardGroup cols={2}>
  <Card title="Boolean" icon="toggle-on">
    **When to use:** Yes/No questions, consent forms, simple eligibility checks\
    **What users see:** A toggle, button, or checkbox with two clear options
  </Card>
</CardGroup>

**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

<CardGroup cols={2}>
  <Card title="Autocomplete" icon="searchengin">
    **When to use:** Searching large lists like companies, cities, or categories\
    **What users see:** A search box that suggests options as they type
  </Card>
</CardGroup>

**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

<Note>
  **Address lookups now use RTB everywhere.** Danish address autocompletion is powered by RTB across all housing types, including rental and cooperative housing. The previous DAWA fallback has been removed, so address results are consistent throughout your flows.
</Note>

***

## 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

***

## Related Pages

* [Collecting Information](/features/collecting-information)
* [Files, Dates & Locations](/features/files-dates-locations)
* [Communication & Display](/features/communication-display)