> 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/feature-highlights/agent-details-report.md).
# Agent Details Report
The agent details report shows each agent's interactions history. Simply put, it's all the interactions an agent has interacted with in some way.
By default, your report only shows interactions that the agent answered. This setup highlights direct interactions with contacts and gives you an idea of how often and well the agent handles them. But if you want a complete picture, including missed or rejected interactions, follow these easy steps.
#### Steps to Include More Interaction Types:
1. **Head to the Filters:** Click the filter button to explore different customization options.
2. **Turn on "Include Missed Interactions":** Just toggle that switch to include any interactions that didn’t get answered.
3. **Turn on "Include Rejected Interactions":** Flick this switch, too, to factor in interactions that got bounced.
Once you do this, your report will go beyond just answered interactions. You'll get a full view that shows all interactions, including those that were missed or rejected—ideal for a deeper dive into how interactions are being handled.
---
# 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/feature-highlights/agent-details-report.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.