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

# FAQ

<details>

<summary>What is the difference between Zendesk Chat and Zendesk Support in Coupler.io?</summary>

Zendesk Chat is a standalone live chat product focused on real-time conversations, agent availability, and chat routing. Zendesk Support is a ticketing system for managing longer-running customer issues. They have separate APIs and separate Coupler.io connectors. If you use both, you can combine data from each using Coupler.io's Join or Append transformations in a single data flow.

</details>

<details>

<summary>Can I export full chat transcripts, or just metadata?</summary>

The Chats entity includes message-level data for each conversation, not just metadata. You'll get timestamps, agent and visitor messages, tags, ratings, and session details. The exact transcript content depends on your Zendesk Chat plan and data retention settings.

</details>

<details>

<summary>How do I get agent names into my chat export?</summary>

The Chats entity stores agent identifiers (agent\_ids), not names. To get human-readable names, add the Agents entity as a second source in your data flow and use Coupler.io's Join transformation to match agent\_ids to agent names, roles, and departments.

</details>

<details>

<summary>Why does my Chats entity return no rows when I run the data flow?</summary>

The most common reason is a missing or incorrect start date. The Chats entity requires a start date — use the date picker to set one. Also confirm that your API token has the correct permissions and that the account had chat activity during the selected period.

</details>

<details>

<summary>Can I pull data from multiple Zendesk Chat accounts into one destination?</summary>

Yes. Add multiple sources within the same data flow — one per account — and use Coupler.io's Append transformation to combine them. This is useful if your organization operates separate Zendesk Chat accounts for different brands or regions.

</details>

<details>

<summary>Which entities require Admin-level access?</summary>

Roles, Bans, Routing settings, and Accounts all require an Admin API token. Using an Agent-level token will result in 403 errors or empty responses for these entities. Generate your token from an Admin user account to avoid this.

</details>

<details>

<summary>Can I send Zendesk Chat data to an AI tool?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send chat records or agent performance summaries directly to these tools for analysis, summarization, or generating support insights.

</details>

<details>

<summary>How far back can I pull historical chat data?</summary>

This depends on your Zendesk Chat plan's data retention policy. Coupler.io will retrieve whatever Zendesk Chat makes available through its API for your account tier. Use the date picker to set your start date, and check your Zendesk Chat plan documentation for retention limits.

</details>

{% hint style="info" %}
For field-level details on what each entity returns, see the [Data Overview](/sources/category/crm/zendesk-chat/data-overview.md) article. For help with empty exports, authentication errors, or mismatched numbers, check [Common Issues](/sources/category/crm/zendesk-chat/common-issues.md).
{% endhint %}


---

# 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.coupler.io/sources/category/crm/zendesk-chat/faq.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.