# Callback Requests Navigate to Analytics & Reports | Callback Requests Displays a list of callback requests. 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 call (Inbound/Outbound). | | Start | Start date/time of call. | | End | End date/time of call. | | When | Approximate time difference between when the callback was created and now. | | Callback | Displays if the caller requested a callback. Agents can complete the callback by selecting the icon. | | Status | Current status of callback request. | | Callback Contact | Callback phone number or UPN. | | Callback Description | Description of callback. | | Callback Completed By User | The user that completed the callback. | | Date Callback Completed | Date and time when the callback was completed. | | Caller Name | Name of caller. | | Caller Number | Number of caller. | | Queue/IVR | Name of Queue | | Length | Total length of call | | Wait Time | Total time the call was waiting in queue | | Leave Reason | Reason why caller abandoned. | | OU | Displays the organization unit where the call detail record is stored. | | OU Path | Displays the organization unit path where the call detail record is stored. | | Scenario Id | Microsoft Teams Call ID | | From | Displays if the call originated from another IVR or Contact Center Queue. | | To | Displays if the call was transferred to another IVR or Contact Center Queue. | --- # Agent Instructions: 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: ``` GET https://cc.docs.landis.cloud/reports/callback-requests.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.