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

# Ticket fields

> Learn how to configure and manage ticket fields in the Thena ticketing system.

<img src="https://mintcdn.com/thena-840ce5ec/fnPhXvYfm-TNmZho/images/docs/Ticket-fields.webp?fit=max&auto=format&n=fnPhXvYfm-TNmZho&q=85&s=e0d8cd3191f85d09628f8611224e02bd" alt="Ticket fields interface" className="rounded-lg" width="7680" height="4800" data-path="images/docs/Ticket-fields.webp" />

Ticket fields are one of the most powerful and flexible features on the Thena platform.
They let you collect, structure, and act on the right data across your support workflows.

Thena supports both standard fields and custom fields, giving teams full control over
what data is tracked—without compromising speed or usability.

## Types of fields

### Standard fields

These are built-in and come with every ticket. They cover essential metadata and
identification info. Examples include:

<AccordionGroup>
  <Accordion title="Identification" icon="fingerprint">
    ID, Ticket ID, Title, AI-generated title, Description, AI-generated summary
  </Accordion>

  <Accordion title="Time metadata" icon="clock">
    Created at, Updated at, Due date
  </Accordion>

  <Accordion title="Ticket properties" icon="ticket">
    Is escalated, Is draft, Private, Sentiment, Story points, Source, Team, Parent team,
    Assigned agent
  </Accordion>

  <Accordion title="Lookup fields" icon="magnifying-glass">
    Account, Team, Source, Assigned agent, Sentiment, Customer contact
  </Accordion>
</AccordionGroup>

### Custom fields

Use these to collect additional structured inputs. You can create any number of fields
with various data types.

<img src="https://mintcdn.com/thena-840ce5ec/qw0IBJ-u1Oc1t24_/images/docs/Create%20ticket%20field.webp?fit=max&auto=format&n=qw0IBJ-u1Oc1t24_&q=85&s=ea55dc7daaa845303219d632f1f45c66" alt="Create ticket field interface" className="rounded-lg my-4" width="7680" height="4800" data-path="images/docs/Create ticket field.webp" />

#### Custom field types

<AccordionGroup>
  <Accordion title="Text fields" icon="text-size">
    Single line, Multi line, Rich text
  </Accordion>

  <Accordion title="Number fields" icon="calculator">
    Integer, Decimal, Currency
  </Accordion>

  <Accordion title="Date and time fields" icon="calendar">
    Date, Date & time, Time
  </Accordion>

  <Accordion title="Choice fields" icon="toggle-on">
    Single choice, Multi choice, Radio buttons, Checkboxes
  </Accordion>

  <Accordion title="Specialized fields" icon="puzzle-piece">
    File upload, Email, Phone number, URL, Address, Rating, Coordinates, IP address,
    Regex, Password
  </Accordion>

  <Accordion title="Advanced fields" icon="sliders">
    Calculated, Lookup, Toggle / Boolean
  </Accordion>
</AccordionGroup>

## Field settings

Customize each field with powerful controls:

* Required settings
  * Mandatory on creation
  * Mandatory on close
* Visibility settings
  * Visible to customers
  * Editable by customers
* Field settings
  * Placeholder text
  * Hint/help text
* Form behavior
  * Auto-add to all forms

This allows fine-grained control of how fields behave across workflows and customer-
facing forms.

## Managing fields

You can search, manage, and update fields anytime from the Ticket fields settings page.
Each field is clearly labeled by type and whether it's standard or custom.

## Why ticket fields matter

<CardGroup cols={2}>
  <Card title="Better triage and routing" icon="route" iconType="duotone">
    Collect the right information upfront to automatically route tickets to the right teams and prioritize effectively.
  </Card>

  <Card title="Power automations" icon="bolt" iconType="duotone">
    Build powerful SLAs and automated workflows based on field values to streamline support processes.
  </Card>

  <Card title="Smarter analytics" icon="chart-mixed" iconType="duotone">
    Generate insightful reports and track performance metrics with structured ticket data.
  </Card>

  <Card title="Relevant data collection" icon="filter" iconType="duotone">
    Collect only what matters, when it matters, creating a better experience for both agents and customers.
  </Card>
</CardGroup>
