> 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/other/zendesk-talk/faq.md).

# FAQ

<details>

<summary>Which Zendesk Talk entities support date filtering?</summary>

Only **Calls** and **Call legs** support a start date parameter. All other entities (Agents activities, Agents overviews, Account overviews, Current queue activities, IVRs, Phone numbers, etc.) return their full current dataset regardless of any date setting.

</details>

<details>

<summary>Can I connect multiple Zendesk Talk accounts to the same data flow?</summary>

Yes. You can add multiple sources within a single data flow — one per Zendesk account. Use the **Append** transformation to combine call data from different accounts into a single output, which is useful if your organization runs separate Zendesk instances for different regions or brands.

</details>

<details>

<summary>How do I link Zendesk Talk calls to Zendesk Support tickets?</summary>

The **Calls** entity includes a `ticket_id` field that maps directly to ticket IDs in Zendesk Support. If you also have Zendesk Support connected to Coupler.io, use the **Join** transformation on `ticket_id` to combine call data with ticket details like resolution time, priority, and agent notes.

</details>

<details>

<summary>Why do Agents overviews and Current queue activities change every time I run the data flow?</summary>

Both of these entities reflect the **live state** of your Zendesk Talk account at the moment the data flow runs. They are not historical — each run overwrites the previous output. If you need to track changes over time, consider appending each run's output to a separate log sheet rather than replacing it.

</details>

<details>

<summary>Can I export call recordings through Coupler.io?</summary>

No. The Zendesk Talk API only provides a `recording_url` link in the Calls entity — it does not stream or export audio files. You'd need to access the recording URLs directly in Zendesk or download them via a separate tool.

</details>

<details>

<summary>What's the difference between Calls and Call legs?</summary>

A **Call** is the full interaction from start to finish. A **Call leg** is a segment within that call — for example, the initial inbound ring, a transfer to a different agent, or an external forwarding leg. If a call is transferred twice, it will have one Call record and three Call leg records. Use Call legs when you need to trace exactly how calls were routed.

</details>

<details>

<summary>Can I use Zendesk Talk data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You could, for example, send a weekly export of agent activity metrics to ChatGPT to generate a plain-language performance summary, or feed missed call trends to Claude for root-cause analysis.

</details>

<details>

<summary>Why are my IVR menus and IVR routes empty?</summary>

These entities only contain data if Interactive Voice Response is configured in your Zendesk Talk account. If your setup uses direct-to-agent routing without IVR menus, these entities will return no rows. Check under **Admin Center → Channels → Talk → IVR** to confirm whether IVR is enabled.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](/sources/category/other/zendesk-talk/data-overview.md) article. For help with authentication errors or missing data, check [Common Issues](/sources/category/other/zendesk-talk/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/other/zendesk-talk/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.