> For the complete documentation index, see [llms.txt](https://distance.gitbook.io/distance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://distance.gitbook.io/distance/getting-started/tickets.md).

# Tickets

### **Introduction**

The **Tickets** feature organizes incoming customer requests from chat, SMS, calls, or social channels. Each ticket captures an inquiry, issue, or follow-up, making it easy to assign ownership, monitor progress, and ensure nothing is overlooked.

<div data-with-frame="true"><figure><img src="/files/TFgeAdMcoRsEUF07aCQo" alt=""><figcaption></figcaption></figure></div>

**Tickets** integrate with AI agents to log conversations, escalate issues, and resolve requests efficiently while maintaining clear visibility for your team.

***

### **Why Tickets matter**

**Track customer requests**. Maintain detailed records so no inquiry is missed.

**Document service issues**. Log and monitor issues for faster, more consistent resolution.

**Team collaboration**. Assign tickets to team members for clear accountability.

**Streamlined workflow**. Use the ticket pipeline to manage ongoing tickets through standard stages.

**Sync with contacts**. Tickets link to new or existing customers, keeping records accurate and centralized.

***

### **How tickets work together**

Tickets turn conversations into structured work your team can track and resolve.

When a customer inquiry needs follow-up, a [**ticket can be created**](/distance/getting-started/tickets/creating-a-ticket.md) to capture the request, link it to the relevant contact, and assign ownership so nothing falls through the cracks.

As ticket volume grows, [**customizing the tickets view**](/distance/getting-started/tickets/customizing-the-tickets-view.md) helps your team stay focused by organizing tickets by status, assignee, or priority.

Together, these tools make it easier to move from incoming conversations to clear action, ensuring customer requests are handled consistently, transparently, and on time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://distance.gitbook.io/distance/getting-started/tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.