> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/evm/bot-features/rewards/suggestions.md).

# Suggestions

{% hint style="info" %}
Send ideas to Bloom and follow their status. Open it with `/suggestions`.
{% endhint %}

## Suggestions Screen

The suggestions screen lists the suggestions you sent and lets you create a new one.

| Button                      | Action                                                                                                                            |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **📝 Create Suggestion**    | Asks for your idea.                                                                                                               |
| **ID: 42 \| 🟡 In Review**  | One button per suggestion you sent, with the status **🟡 In Review**, **🟢 Approved** or **🔴 Rejected**, that opens its details. |
| **⬅️ Back** and **Next ➡️** | Turn the pages when you have more than 5 suggestions.                                                                             |
| **Page 1/3**                | Shows which page you are on.                                                                                                      |

The <kbd>⬅️ Back</kbd> on the bottom row returns to Home, <kbd>🔄 Refresh</kbd> reloads the screen and <kbd>🗑️ Close</kbd> deletes the message.

## Send a Suggestion

1. Send `/suggestions` and tap <kbd>📝 Create Suggestion</kbd>.
2. Send your idea as text, at least 10 characters.

## Suggest on Discord

1. Open the suggestions form channel on Bloom's Discord server and tap **Create Suggestion**.
2. Enter your idea in the form and tap **Submit**.

Your suggestion then appears in the suggestions vote channel, where everyone on the server can up-vote or down-vote it.

## Suggestion Details

Tap a suggestion to open its details.

| Field          | Description                                                                         |
| -------------- | ----------------------------------------------------------------------------------- |
| **ID**         | The number of the suggestion.                                                       |
| **Status**     | The status of the suggestion: **🟡 In Review**, **🟢 Approved** or **🔴 Rejected**. |
| **Created**    | The date and time you sent the suggestion.                                          |
| **Suggestion** | Your text.                                                                          |
| **Reason**     | Shows the reason, when Bloom added one.                                             |

<kbd>⬅️ Back to Suggestions</kbd> returns to the list and <kbd>🗑️ Close</kbd> deletes the message.


---

# 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://docs.bloombot.app/evm/bot-features/rewards/suggestions.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.
