> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/graph-transfer-reporting.md).

# Graph Transfer Reporting

{% hint style="warning" %}
This Feature is [Preview](/appendix/feature-states.md) and has known limitations. The Graph API used to gather this data is inconsistent. It may take **up to 2.5 hours** for this information to populate and in some cases **may not appear** at all. Microsoft is aware of this issue, but unfortunately there is no immediate solution.
{% endhint %}

The Graph Transfer Reporting feature indicates if an agent transferred a queue call to another user, queue, or IVR. This information appears in the Agent details report under the "To" column.

Follow the steps below to enable this feature:

1. Navigate to Administration | Settings | Grant permissions for call records API.
2. Navigate to Queues & IVRs | Edit queue(s) | Integrations Tab | Enable Graph Transfer Reporting


---

# 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://cc.docs.landis.cloud/appendix/graph-transfer-reporting.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.