> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/use/monitor-and-report/call-summary-and-missed-calls.md). # Reporting: call summary and missed calls Understand what the Call Summary and Missed Calls Today views show and which fields they include. Use these SharePoint views to review stored call records and focus on unanswered calls from the current day. ## Before you begin * Your administrator has enabled call-summary reporting for your contact center. * You can open the SharePoint site your organization uses for these records. For SharePoint-backed call-summary reporting, the UCC setting `WriteSummaryToSharepoint` controls whether call details are written to the **Call Summary** and **Missed Calls Today** views. Default `False`. ## Open the reporting views 1. Open the SharePoint reporting list in the Unified Contact Center (UCC) SharePoint site your organization uses for call records. 2. In that list, select **Call Summary** to review all stored calls or **Missed Calls Today** to focus on unanswered calls from the current day. ## Use the Call Summary view Use **Call Summary** when you need a complete list of stored calls and their metadata. ### Call Summary fields | Field | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Title` | Unique call record ID (`GUID`) created by AnywhereNow. Use it when you need to match one call record with another report or a support request. | | `StartTime` | Date and time when the call connected to the Unified Contact Center (UCC) | | `InQueueTime` | Date and time when the call entered the queue | | `AcceptedTime` | Date and time when an agent accepted the call | | `EndTime` | Date and time when the call disconnected | | `Accepted` | Whether the call was accepted | | `QueueTime` | Queue duration, calculated as `AcceptedTime - InQueueTime` | | `SkillChosen` | Skill required to answer the call | | `LastAgent` | SIP address of the agent who accepted the call. This helps you see who handled the call. | | `Customer` | SIP address of the caller. This is the voice endpoint identifier stored for the customer side of the call. | | `QualityMonitor` | First quality-monitor result returned by the customer. `0` means Quality Monitor was not triggered, and `-1` means the customer did not enter a value. | ## Use the Missed Calls Today view Use **Missed Calls Today** when you need to focus on calls that were not accepted on the current day. ### How this view is defined **Missed Calls Today** is a SharePoint view that is already filtered for unanswered calls from the current day. | Field | Value | | ----------- | ------- | | `Accepted` | `False` | | `StartTime` | `Today` | ### Fields shown in Missed Calls Today | Field | Description | | ------------- | ---------------------------------------------------------------------------------------------------------- | | `StartTime` | Date and time when the call connected to the UCC | | `Customer` | SIP address of the caller. This is the voice endpoint identifier stored for the customer side of the call. | | `SkillChosen` | Skill required to answer the call | ## Result You can review all stored calls in **Call Summary** and switch to **Missed Calls Today** to focus on unanswered calls from the current day. --- # 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://atlas.anywhere.now/use/monitor-and-report/call-summary-and-missed-calls.md?ask=&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.