> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/how-to-use/tickets/create-a-ticket.md).
# Create a Ticket
This tutorial will show how to manage tickets from start to finish
### Step 1 - Go to Contact Profile
Go to customer profile that you want to create. Click **+ New Ticket**
### Step 2 - Enter Ticket Details & Information
Enter ticket information as per below. You can customize your own ticket form in the settings.
Follow this tutorial to customize ticket fields
### Step 3 - Collaborate Tickets with Team Members
You can mention / comment to your team members on the tickets within your organization.
You can use @mention your team in the comments
### Step 4 - Resolved
After ticket is resolved, you can click **"Resolved"** button
### Done
For more about tickets reporting, visit the following tutorials
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.klink.cloud/how-to-use/tickets/create-a-ticket.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
