> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark.md).

# Ticket escalation with Spark

Ticket escalation enables Spark to route unresolved employee issues to the right IT team by creating a ticket in your organization's IT service management (ITSM) system. Employees can then follow the status of those tickets in Spark.

Spark resolves many employee issues through self-service. When an issue requires human intervention, Spark escalates the conversation using a predefined API call that creates an ITSM ticket and preserves the conversation context.

Nexthink offers two ways to configure ticket escalation with Spark:

* **Create a ticket**: Spark creates a ticket in your ITSM system when it cannot resolve an issue. Refer to [Configuring ticket creation with Spark](https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark/configuring-ticket-creation-with-spark.md).
* **Follow up on a ticket**: Employees check the status of their tickets, read agent comments, and reply in Spark. This includes tickets created elsewhere. Refer to [Configuring ticket follow-up with Spark](https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark/configuring-ticket-follow-up-with-spark.md).

## When does ticket escalation occur

Spark escalates a conversation when it cannot resolve the issue autonomously, for example:

* Technical issues that require service desk support
* Questions that Spark cannot resolve
* Requests that are not yet automated

Ticket escalation routes these conversations through existing ITSM processes and keeps them traceable.

## How ticket escalation works

Spark performs these steps when it escalates a conversation:

1. Spark identifies that the issue requires escalation.
2. The employee confirms that Spark should create a ticket.
3. Spark selects the category and assignment groups from your categorization, if you configured one.
4. Spark calls the API call and passes the mapped values, including the conversation context.
5. The API call creates a ticket in the ITSM system, which returns a ticket reference.
6. Spark shares the ticket reference with the employee and marks the conversation as **Escalated** in the Spark cockpit.
7. (Optional) The employee follows the ticket in Spark. Refer to [Configuring ticket follow-up with Spark](https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark/configuring-ticket-follow-up-with-spark.md).

If ticket creation fails, Spark sends fallback notifications to the employee.

This process ensures continuity and allows support teams to track and follow up on the issue without losing context from the original conversation.


---

# 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.nexthink.com/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark.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.
