> For the complete documentation index, see [llms.txt](https://docs.iadvize.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iadvize.dev/apps/public-apps/zendesk.md).

# Zendesk

<figure><img src="/files/d2QfjYX8q1C9eZdX3OeT" alt=""><figcaption></figcaption></figure>

## Description

The iAdvize Zendesk App allows your agents to trigger escalation tickets and to keep track of every conversation. The App is compatible with pro agents and ibbü experts.

Every ticket created through the App will be linked to an existing customer using the email as a mapping key. If the App finds no customer we will create a new customer in Zendesk.

Key features

* Auto-Save: Decide if you want to save every conversation in Zendesk or not. If activated a ticket will be created in status solved for each conversation handled by your agents.
* Escalation: Activate an option to allow your agents to escalate a ticket in Zendesk if they judge it to be necessary. Use the ticket form of your choosing directly in the iAdvize console as well as a private note.

## **Changelog**

* Update: 01/14/2019 - Version: 2.2.0


---

# 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://docs.iadvize.dev/apps/public-apps/zendesk.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.