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

# Collecting Information

> Input entities that capture the essential details from your users

These entities let you ask users for the basics — names, numbers, amounts, dates, and files. They form the foundation of most flows by gathering the information you need in a clear and user-friendly way.

***

## Text Inputs

<CardGroup cols={3}>
  <Card title="Text" icon="text">
    **When to use:** Names, job titles, short identifiers\
    **What users see:** A simple one-line input field
  </Card>

  <Card title="Text Area" icon="align-left">
    **When to use:** Comments, explanations, longer responses\
    **What users see:** A larger box that grows with text
  </Card>

  <Card title="Email" icon="envelope">
    **When to use:** Collecting valid email addresses\
    **What users see:** An input that checks email format automatically
  </Card>
</CardGroup>

***

<Accordion title="Understanding Browser Autocomplete">
  ### What is Autocomplete?

  Browser autocomplete helps users fill forms faster by suggesting previously saved information like names, addresses, payment details, and more. According to Google, proper autocomplete implementation can **reduce bounce rates by up to 70%**.

  ### When to Use Autocomplete

  **Enable autocomplete** when collecting standard information users likely have saved:

  * Personal details (name, email, phone)
  * Address information
  * Payment details
  * Login credentials

  **Disable autocomplete** when:

  * Collecting sensitive unique information (reference numbers, case IDs)
  * Creating forms where pre-filled data causes confusion
  * Browser suggestions interfere with user experience

  ### Browser Autofill Options

  Select from these common autofill behaviors. For the complete list of all available values, see the [MDN autocomplete reference](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/autocomplete).

  | Behavior         | What It Does             | Example Use Case              |
  | ---------------- | ------------------------ | ----------------------------- |
  | `on`             | Default browser autofill | General text inputs           |
  | `off`            | Disables autofill\*      | Reference numbers, unique IDs |
  | `name`           | Full name suggestions    | "What is your name?"          |
  | `given-name`     | First name               | "First name" field            |
  | `family-name`    | Last name                | "Last name" field             |
  | `email`          | Email address            | Contact information           |
  | `tel`            | Phone number             | Phone fields                  |
  | `street-address` | Full address             | Delivery/billing address      |
  | `postal-code`    | ZIP/postal code          | Address forms                 |
  | `country`        | Country name             | Location selection            |
  | `organisation`   | Company name             | Business details              |
  | `cc-number`      | Credit card number       | Payment forms                 |
  | `cc-exp`         | Card expiration          | Payment forms                 |
  | `username`       | Username                 | Login forms                   |

  \* When `off` is selected, the system automatically rotates the autocomplete value to prevent browsers from overriding your choice.

  ### Quick Start Guide

  **For most use cases:** Select a standard behavior from the **Browser Autofill** dropdown

  **To enable helpful autofill:** Use `name`, `email`, `cc-number`, etc. to reduce bounce rates

  **To disable autofill (simple):** Select `off` - the system handles rotation automatically

  **To disable autofill (advanced):** Use the **Advanced Autofill** field with a variable that rotates values weekly/bi-weekly to outsmart Chrome's ML

  **For specific autocomplete values:** Use the **Advanced Autofill** field with a raw string. Refer to the [complete MDN autocomplete specification](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/autocomplete) for all available values.

  <Note>
    Contact [support@wizflow.io](mailto:support@wizflow.io) if you want to include a new autocomplete property.
  </Note>
</Accordion>

***

## Numbers and Money

<CardGroup cols={3}>
  <Card title="Number" icon="tally">
    **When to use:** Counts, IDs, reference numbers\
    **What users see:** A numeric field with simple validation
  </Card>

  <Card title="Amount" icon="dollar-sign">
    **When to use:** Loan amounts, income, premiums\
    **What users see:** A money field with proper formatting
  </Card>

  <Card title="Percentage" icon="percent">
    **When to use:** Interest rates, completion %\
    **What users see:** Input with automatic % handling
  </Card>

  <Card title="Age" icon="user">
    **When to use:** Insurance or eligibility flows\
    **What users see:** Age field with realistic ranges
  </Card>

  <Card title="Year" icon="calendar">
    **When to use:** Tax year, graduation year, policy start year\
    **What users see:** Input restricted to year values
  </Card>

  <Card title="Formatted Number" icon="calculator">
    **When to use:** Phone numbers, IDs, custom formats\
    **What users see:** Input that applies formatting as you type
  </Card>
</CardGroup>

***

## Files, Dates & Locations

<CardGroup cols={2}>
  <Card title="Date Picker" icon="calendar-days">
    **When to use:** Birth dates, appointments, policy start dates\
    **What users see:** A simple calendar interface
  </Card>

  <Card title="File Upload" icon="upload">
    **When to use:** Document submission, ID photos, attachments\
    **What users see:** Upload button with file size/type checks
  </Card>

  <Card title="Address" icon="map-pin">
    **When to use:** Any address collection in Denmark\
    **What users see:** Validated Danish addresses, powered by RTB
  </Card>

  <Card title="CPR/CVR Lookup" icon="id-card">
    **When to use:** Danish customer or company verification\
    **What users see:** Input that validates CPR or CVR numbers
  </Card>
</CardGroup>

***

## Best Practices

* **Keep it short:** Ask one thing at a time
* **Guide users:** Use placeholders and helper text
* **Validate gently:** Show clear messages only when needed
* **Think mobile:** Make sure inputs are easy to tap and type on small screens

***

## Example Recipe

**Basic Contact Form:**\
Message → Text (Name) → Email → Date Picker (Preferred time) → File Upload (Optional document)

***

## Related Pages

* [Input Validation](/features/input-validation)
* [Choices & Decisions](/features/choices-decisions)
* [Files, Dates & Locations](/features/files-dates-locations)
* [Communication & Display](/features/communication-display)
