> 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/ivr-details.md). # IVR Details Navigate to Analytics & Reports | IVR Details Displays IVR detail records from the IVR perspective. 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 | Start time of interaction in relation to the current date/time. | | IVR Name | Name of IVR. | | Contact Name | Name of contact. | | Contact Id | Id of contact. | | Length | Length of time interaction was connected to IVR. | | To | Displays if the interaction was transferred to another IVR or Contact Center Queue. | | Transfer Type | Displays how the interaction was transferred out of the IVR. | | From | Displays if the interaction originated from another IVR or Contact Center Queue. | | OU | Displays the organization unit where the interaction detail record is stored. | | Scenario Id | Unique Id of interaction | | Callback Requested | Displays if the contact requested a callback. | | Score Status | Quality management score status. | --- # 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://cc.docs.landis.cloud/reports/ivr-details.md?ask=&goal= ``` `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.