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

# Custom fields

> Details a ticket carries, such as an order number or a plan, with a label for your team and a label the customer is asked by.

Custom fields are extra details on a ticket: an order number, a plan, a visit date. Add them under **Settings › Custom fields**; they show on every ticket in the details panel, where your team can fill or change them.

## Two labels

Each field has an **Internal label**, which your team sees, and an optional **Customer-facing label**, which is what the agent asks the customer for ("your order number" for a field your team calls "Order ID"). Dropdown options have both labels too. Leave the customer-facing label empty to use the internal one.

## Types

**Text**, **Number**, **Yes / No**, **Date**, **Email**, **Image** and **Dropdown** (one option). A field's type can't change while any ticket holds a value for it.

## Collected at handover

When the agent hands a customer over (see [A person in chat & email](https://wiredesk.ai/docs/actions/request-a-human.md)), it asks for your fields by their customer-facing labels, in a sentence or two, and fills in what the customer gives. It never makes a value up: what the customer doesn't know or won't share stays empty, and an answer that doesn't fit the field (a word in a date field, a dropdown answer that isn't an option) is left out. Image fields are never asked for.

The **Collection instruction** tells the agent more about a field, such as "The number on the order confirmation email, like #1042."

## Archiving

Archive a field to stop asking for it; tickets keep their values. A field that no ticket has a value for can then be deleted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.