> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/reports.md). # Reports Reports allow you to retrieve and sort information from your AgileCase system. When you create a report, you specify certain pieces of information that will be pulled from your system when you run the report. For example, you could create a report to show all cases created by a certain user or all clients in a certain city. Reports can be used to help audit your system or can be used to dispatch batch emails or mail merges. Using a report to create a batch allows you to send a standard mail to contacts meeting certain criteria. For example, you could create a report to pick out contacts that have not paid their bills, then create a batch and send a standard email reminding them that payment is due in a single action. This section will show you how to create the basic report types in AgileCase, all of which can be combined to create more complex reports to pick out very specific information. Running a report once it exists is covered in [Working with Documents and Reports](/user-documentation/working-with-documents-and-reports.md) in the user documentation. --- # 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://docs.agilecase.com/administrator-documentation/reports.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.