> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/dashboard-and-reports/reporting/call-reports/agent-call-activity.md).

# Agent Call Activity

{% hint style="info" %}
'Agent Call Activity' report is a summary report displayed in line graph, which makes it possible for you to query statistics of calls that have been made or received by a specific agent or agents within a specific group/organization. The report allows you to track changes of call activity over a specific period of time, or compare changes over the same period of time.
{% endhint %}

### Report details

\
The following table lists the related parameters for Extension Call Activity report.

| Parameter           | Description                                                                                                       |
| ------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Answered            | The total number of calls that the agents answered.                                                               |
| No Answered         | The total number of calls that were routed to the designated destination when the agents didn't answer the calls. |
| Busy                | The total number of calls that were routed to the designated destination when the agents were busy.               |
| Failed              | The total number of calls that were failed to be made by the agents.                                              |
| Voicemail           | The total number of voicemails that the agents received.                                                          |
| Total Ring Duration | The time between the call started and the call answered.                                                          |
| Total Talk Duration | The time between the call answered and the call ended.                                                            |

### Report example

The following report shows hourly call statistics of all the agents. 

You can filter by Hourly , Daily, Monthly, Assigned Agents , Inbound or Outbound<br>

<figure><img src="https://420146782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqqwHJh6YA4uvzfFRLnoR%2Fuploads%2F8LgMimUIk9NpfPuJqvnt%2FScreen%20Shot%202023-12-19%20at%209.24.17%20PM.png?alt=media&amp;token=3090e666-c676-4b6c-bf3a-83a1ff4f3315" alt=""><figcaption></figcaption></figure>


---

# 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://docs.klink.cloud/dashboard-and-reports/reporting/call-reports/agent-call-activity.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.