> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox.md).

# Inbox

Inbox is where you go to see what needs your attention: everything worth acting on, gathered in one place.

Instead of switching between products to piece together what's broken and what users want, Inbox brings that signal together under two lists:

* **Issues**: a unified view of the bugs, crashes, performance issues and other problems affecting your app.
* **Opportunities**: AI-generated themes surfaced from user feedback, highlighting feature requests, gaps, and enhancements worth prioritizing.

Both lists live side by side because they answer two sides of the same question: *what should my team work on next?* Issues tells you what's broken. Opportunities tells you what to build. Having them in one hub means you can triage and prioritize without jumping between separate tools.

Inbox is a central hub for this kind of actionable signal, a place your team can check regularly alongside the rest of your workflow. For details on how each list works, see the dedicated Issues list and Opportunities list pages below.


---

# 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.luciq.ai/product-guides-and-integrations/product-guides/inbox.md?ask=<question>&goal=<endgoal>
```

`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.