> 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/reports/abandoned-calls.md).

# Abandoned Interactions

Navigate to Analytics & Reports | Abandoned Interactions

Displays a list of abandoned interaction details.

For report options (e.g., filtering), See [Report Options](/appendix/report-options.md)

| Column               | Description                                                                                           |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| "..."                | Button that displays actions that can be performed on that record.                                    |
| Direction            | Direction of interaction (Inbound/Outbound).                                                          |
| Start                | Start date/time of interaction.                                                                       |
| End                  | End date/time of interaction.                                                                         |
| When                 | Approximate time difference between when the callback was created and now.                            |
| Callback             | Displays if the contact requested a callback. Agents can complete the callback by selecting the icon. |
| Callback Contact     | Callback phone number or UPN.                                                                         |
| Callback Description | Description of callback.                                                                              |
| Contact Name         | Name of contact.                                                                                      |
| Contact Id           | Id of contact.                                                                                        |
| Queue/IVR            | Name of Queue                                                                                         |
| Length               | Total length of interaction                                                                           |
| Wait Time            | Total time the interaction was waiting in queue                                                       |
| Leave Reason         | Reason why contact abandoned.                                                                         |
| OU                   | Displays the organization unit where the interaction detail record is stored.                         |
| OU Path              | Displays the organization unit path where the interaction detail record is stored.                    |
| Scenario Id          | Unique Id of interaction                                                                              |
| From                 | Displays if the interaction originated from another IVR or Contact Center Queue.                      |
| To                   | Displays if the interaction was transferred to another IVR or Contact Center Queue.                   |


---

# 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/reports/abandoned-calls.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.