> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/service-desk/create-tickets.md).

# Create Tickets

## Overview

Tickets can be created in several ways:

1. Via the ticket menu
2. Via an alarm
3. Via a template

### **What is the difference between the different ways of creating a ticket?**

This is primarily a convenience function. When an **alarm** occurs, it's likely that a ticket will need to be created afterward. When a ticket is created via an alarm, certain options of the ticket are already pre-configured, which speeds up the creation process.

When you create a ticket via the **ticket menu**, all available options in the configuration are empty and can be fully customized by you.

When creating a **ticket via a template**, a predefined set of configurations is used, which is particularly helpful if you need to create similar tickets regularly. This method saves time and ensures that recurring tasks are managed consistently and efficiently.

## Create via the Ticket Menu

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FJyINSS5p9ACV1GCCY1Qn%2FFB8112CD-DC3B-4E48-B6BE-95C994FDD068.png?alt=media&#x26;token=2c4174f6-f17a-4a38-8cb5-9b9d158e434a" alt=""><figcaption></figcaption></figure></div>

1. Click on **\[A]**\
   ▷ The ticket menu opens
2. Click on **\[M]**\
   ▷ The ticket configuration menu opens
3. Continue in chapter [-> Configure ticket](/collection/platform/service-desk/configure-ticket.md)

## Create via an Alarm

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FQrPQPuaQU0GUfjCP5MJc%2FCCB20167-4154-4006-9EE5-182A29718756.png?alt=media&#x26;token=f7372d29-9794-4657-be97-f35d9c40e833" alt=""><figcaption></figcaption></figure></div>

1. Click on **\[A]**\
   ▷ The alarm menu opens
2. For the alarm for which you want to create a ticket, click on **\[C]**\
   ▷ The **More Options \[D]** menu appears
3. Click on **Create ticket \[G]**\
   ▷ The ticket configuration menu opens
4. Continue in chapter [-> Configure ticket](/collection/platform/service-desk/configure-ticket.md)

## Create via Templates

<figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FbXcin91UKtUWF6p6VRF5%2FTicketing%20(5).png?alt=media&#x26;token=bca7a961-1a04-46d0-bdc6-a800a927bdaf" alt=""><figcaption></figcaption></figure>

1. Go to the **ticket menu** \[A].\
   ▷ The ticket menu opens.
2. Activate the **Templates** switch \[I].\
   ▷ The list of available templates is displayed.
3. Select the desired template from the list.\
   ▷ The ticket configuration menu opens.
4. Continue in chapter[ -> Configure ticket](/collection/platform/service-desk/configure-ticket.md)


---

# 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.buildings.ability.abb/collection/platform/service-desk/create-tickets.md?ask=<question>&goal=<user_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.