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

# Zendesk

Use Screendesk inside Zendesk to request, send, and receive recordings and live sessions.

{% hint style="info" %}
Contact <support@screendesk.io> or [send us a recording](https://app.screendesk.io/recordings/new?ak=0ZMy1g\&key=4cWV2A\&src=sria)
{% endhint %}

Screendesk empowers customer facing teams with async and sync videos features. It also makes it easy to access these features directly in their favourite ticketing system (Zendesk, Intercom, Help Scout, etc...)

## Add AI to the recording workflow

Screendesk can analyze eligible customer recordings and use them to investigate a Zendesk ticket.

* **Report intelligence** summarizes the recording and surfaces useful evidence.
* **Data Sources** provides trusted documentation, procedures, and optional solved-ticket history.
* **AI Resolution** combines the current ticket and recording evidence with that knowledge to prepare a private note for the agent.

AI Resolution requires setup. It does not send public replies or automatically solve tickets. Your team reviews the evidence and any recommended reply before responding.

Start with [AI Resolution](/debug-with-ai/ai-resolution.md), [Data sources](/debug-with-ai/data-sources.md), or the [helpdesk workflow guide](/debug-with-ai/ai-in-your-helpdesk.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.screendesk.io/helpdesk-integrations/zendesk.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.