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

# Create a ticket

> How to add a new service ticket and link it to a property and lift.

Creating a ticket records a service event — a callback, maintenance visit, inspection, or other work — against a property and the lifts that were serviced. Use this article to add a ticket by hand.

<Note>
  Creating tickets is limited to the **consultant** role.
</Note>

## Open the Add Ticket form

<Steps>
  <Step title="Start an upload">
    Select **Upload Document**, then choose **Add Manually**.
  </Step>

  <Step title="Choose Ticket">
    Pick **Ticket** from the list. The **Add Ticket** dialog opens.
  </Step>
</Steps>

## Fill in the ticket

The form has a **General** section and a **Ticket** section.

### General

* **Property** — the property where service was performed. Choosing a property determines which lifts and invoices you can select.
* **Invoice #** — optional. Link the ticket to an existing invoice. This field is available only after you select a property, and it lists invoices for that property.
* **Service Provider** — the provider who did the work. Required. If you linked an invoice, the choices are narrowed to that invoice's provider.

### Ticket

* **Ticket Number** — the ticket's identifier (up to 20 characters).
* **Entry Type** — the kind of service. See [Understand the ticket types](/tickets/ticket-types). Your choice changes the remaining fields.
* **Problem Type** and **Problem Description** — shown for callback types (Regular, Emergency/Entrapment, Deferred).
* **Corrective Action** / **Work Performed** — what was done. The label is **Corrective Action** for callbacks and **Work Performed** for scheduled work.
* The cars-serviced field — select one or more lifts. The options come from the property you chose.
* **Time fields** — for callbacks, **Call Time**, **Response Time**, and **Resolution Time**; for scheduled work, **Arrival Time** and **Departure Time**.
* **Time on Site** and **Travel Time** — optional regular and overtime hours.
* **Notes** — optional free text.

<Note>
  Required fields differ by type. Callbacks require a problem description; every ticket requires the work/corrective-action field, a service provider, and a property. Any lift you add under cars serviced must belong to the chosen property. The departure/resolution time must be after the arrival/response time, and times cannot be in the future. See [Edit a ticket and its fields](/tickets/edit-a-ticket) for the full rules.
</Note>

## Save

Select **Save**. Lift AI validates the form and shows an inline error if anything is missing or invalid. On success, the new ticket appears in the [Tickets table](/tickets/browse-tickets) and is reflected in the related performance numbers.

<Tip>
  To attach the source document — a service report or work order — see [Add attachments to a ticket](/tickets/ticket-attachments).
</Tip>