> 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/sentiment-report/how-its-delivered.md).

# How it's delivered

When reports arrive, where they arrive, what they're built from, and how to follow up.

## Where it arrives

| Channel      | How it works                                                                                                                                              |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email**    | If your agent has a work email, reports land in your inbox. Reply to the report email to ask questions, dig into a topic, or change your report settings. |
| **Web chat** | Without a work email, reports arrive in chat. You can also ask for one there at any time.                                                                 |
| **Slack**    | If Slack is connected, reports arrive as short summary cards.                                                                                             |

See [Chat, email and Slack](/eirin-ai-docs/working-with-eirin/chat-email-and-slack.md) to set up each channel.

## When it arrives

* **On your schedule:** daily, weekly, every two weeks or monthly. Just ask, for example "Send me a report every Monday morning."
* **When you ask:** say "Create a player sentiment report" and Eirin sends one within a few minutes.
* **Clear periods:** each report covers a set period (for example 14 or 31 days), compares it with the period before, and tells you when the next report is due.

## What it's built from

Each report is built from the sources you've connected: the App Store, Play Store, Steam, Reddit, Discord, YouTube and Instagram. The bottom of every report lists the sources used and how many items Eirin read. To add a source, see [Connect your sources](/eirin-ai-docs/connect-your-sources/sources-overview.md).

The report changes with your sources. For example, the YouTube section only appears when YouTube is connected.

## After it arrives

* **Follow up in chat or by email:** "Drill into the payment complaints", or "What are players saying about the new map?"
* **Change future reports:** "Break everything down by platform" applies to every report after that.
* **Find old reports:** every report is kept, and you can get any of them back, for example "Send me the monetisation section from March."

See [Requests and reports](/eirin-ai-docs/working-with-eirin/requests-and-reports.md) for everything you can ask.

## Report guardrails

Some topics are a known part of how your game is built or makes money. **Report guardrails** are rules your studio writes to keep those topics out of reports. Eirin applies them before it writes each report, so known trade-offs don't crowd out what actually needs your attention. See [Customising your report](/eirin-ai-docs/sentiment-report/customising-your-report.md).


---

# 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/sentiment-report/how-its-delivered.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.