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

# Overview

> Input fields are custom data fields attached to locations that collect information from visitors.

Input fields define what data is collected from visitors when they join a queue. Each location can have its own set of input fields, allowing different locations to collect different information.

There are 9 field types available:

| Type              | Description                                                    |
| ----------------- | -------------------------------------------------------------- |
| **FIRST\_NAME**   | Visitor's first name (built-in, one per location)              |
| **LAST\_NAME**    | Visitor's last name (built-in, one per location)               |
| **EMAIL**         | Visitor's email address (one per location)                     |
| **PHONE\_NUMBER** | Visitor's phone number (one per location)                      |
| **TEXT**          | Free-form text input                                           |
| **SELECT**        | Dropdown selection with custom options (supports multi-select) |
| **URL**           | URL input                                                      |
| **DATE**          | Date input                                                     |
| **NUMERIC**       | Numeric input with optional min/max constraints                |

Input fields can be configured with visibility and mandatory settings to control when and where they appear — such as before a ticket is added, before it is served, or in remote sign-in.

Each input field can be scoped to specific lines within a location using the `visibleForLines` property. If no lines are specified, the field applies to all lines.