> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/reporting/call-reporting.md). # Call Reporting The Reporting Tab includes a specific report on **our software** calls. Using various available filters, you can view the call source, duration, and more. You can also export the data if you need a spreadsheet/list of the information. Follow these simple steps to learn how: **Step 1: Accessing The Report** * Navigate to the Reporting section of **our software** * Click “Call Reporting” to view your Call Stats page. * You’ll see your Call Stats dashboard with some filters and options at the top of the screen. * Choose “All Calls” or a specific number to view data for. * Select a date period. * Expand the “Filters” to filter out any further filterable information you wish to set for the data. {% embed url="" %} * The filters include call duration, status, keywords, call status, and more. {% embed url="" %} * Click “Update Filters” to set your filters. **Step 2: Viewing The Report Data** * Once you’ve determined whether you want to view data for “All Calls” or a specific number, you’ve selected a date period, and set your filters, you can view the specific call data. * The first row shows a graph of Answered vs. Missed Calls, a graph of your top call sources, and a graph of your total call numbers. {% embed url="" %} * The second row shows number statistics for answered and missed calls, first-time calls, and the average call duration. {% embed url="" %} * The last section shows a log of “Latest Phone Calls”. {% embed url="" %} * You can click the arrow next to each to expand the log to view more information (including the call direction - whether it was inbound or outbound), and you can also listen to any call recordings. {% embed url="" %} * If you wish to export your Call Stats, simply click the export button in the top right corner. The icon looks like this: {% embed url="" %} You can come back to this reporting screen anytime, update the filters or the time period, and review the data as often as you want. ***NOTE:*** If you wish to view reporting metrics for one single day, be sure to check that date as the start and end date. You must have both selected in order for the stats to appear. The example below shows how you can run reports for January 1, 2022, by choosing January 1st as the start and end date: {% embed url="" %} --- # 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://software-help-docs.gitbook.io/knowledge-base/software-guide/reporting/call-reporting.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.