> For the complete documentation index, see [llms.txt](https://eirin-ai.gitbook.io/eirin-ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/requests-and-reports.md).

# Requests and reports

Everything you can ask your community manager, and what its reports include.

Talk to Eirin the way you'd talk to a team member. Every request below works over web chat, email or Slack.

## What you can ask

| To...                      | Say something like                                         | What happens                                                                         |
| -------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **Get a report**           | "Give me a report on player sentiment for the last 7 days" | Eirin analyses every connected source and replies with a summary and **View report** |
| **Set a schedule**         | "Send me a report every Monday morning"                    | Eirin confirms and runs it                                                           |
| **Drill into a topic**     | "Show me recent reviews mentioning bugs or crashes"        | Eirin replies with the matching reviews and posts, grouped by platform               |
| **Customize**              | "Break everything down by platform"                        | Applied to all future reports                                                        |
| **Add or remove a source** | "Also track Reddit"                                        | Eirin confirms and updates                                                           |
| **Retrieve past reports**  | "Send me the monetisation section from March"              | Eirin finds and sends it                                                             |

![A drill-down question, answered with reviews and posts by platform](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-1eb67444cc22d9e994b135bcbb37afcb1baf6c9d%2F43_Chat_question-answer.png?alt=media)

### More examples

* **Get a report** → "Create a sentiment report for Game 2"
* **Customize** → "Break down by platform" / "Show only negative reviews"
* **Drill down** → "Drill into the payment complaints" / "What are players saying about the new map?"
* **Schedule** → "Send me reports every Monday morning"
* **Update** → "Add Reddit to our data sources" / "Stop monitoring YouTube"

{% hint style="success" %}
**Preferences stick.** Eirin remembers your preferences automatically, so a customization like "break everything down by platform" applies to all future reports.
{% endhint %}

## What a report looks like

In chat, a finished report arrives as a short summary: the headline finding, sentiment by source with the number of reviews behind each figure, and a **View report** link that opens the full report as a PDF. Eirin may also offer to send the same report on a schedule; reply "yes, weekly" to accept.

![A report summary in chat](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-fc6fff34cf00a664463ac23b03081fc59787654b%2F45_Chat_report-summary.png?alt=media)

The full report opens with a scorecard and an overview, then works through what players said, what changed since the last report, and what to do about it, section by section.

![Page one of a report: scorecard and overview](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-fccce3e06fb3176962fed5b181b98b304e167e1a%2F46_Report_pdf-page-1.png?alt=media)

![Page two of a report](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-d519a978036c70089c6bf7c0cc256548c51ca252%2F47_Report_pdf-page-2.png?alt=media)

Every report is kept under **Reports** in the workspace, with the platforms it drew on and a link back to the conversation that produced it. See [Your workspace](/eirin-ai-docs/working-with-eirin/your-workspace.md).

## What Eirin can do now

{% columns %}
{% column %}

### Reports & analysis

* Daily, weekly, bi-weekly or monthly sentiment reports
* Multi-platform breakdown (Play Store, App Store, Steam, Reddit, Discord, YouTube, Instagram)
* Top risks and positives
* ASO-ready keywords
* Creator vs. player sentiment gaps

### Customization

* Set your own reporting schedule
* Customize report format
* Add or remove sources
* One-off requests
  {% endcolumn %}

{% column %}

### Follow-up analysis

* Drill into specific topics
* Cross-platform correlation
* Per-platform breakdowns
* Trending keywords

### Memory & retrieval

* Every report stored forever
* Retrieve any past report on demand
* Preferences remembered automatically
  {% endcolumn %}
  {% endcolumns %}

## Getting reports to the right people

Only the manager can configure agents and give instructions. Team members can receive forwarded reports. If different teams need different views of the same game, customize report formats and set up different schedules (e.g. one report for Leadership, one for LiveOps).


---

# 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://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/requests-and-reports.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.
