> ## Documentation Index > Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt > Use this file to discover all available pages before exploring further. # Send feedback and follow it > Send a bug report, suggestion or question to the SRE Agent team, follow its status, read and answer our replies, choose when we email you, and do the same from an agent. Free plan Anyone who belongs to an organization, in any member or admin role, can tell the SRE Agent team about a bug, a suggestion or a question. What you send stays visible to you with its status and our replies, so you do not have to wait for an email to find out what happened to it. Guests and auditors have no Feedback page and cannot send: an auditor is not a member of the organization it reviews. ## Send feedback **1. Open Feedback** Click the speech bubble in the sidebar footer, or open **Feedback**. **2. Fill in the form** Choose a category (bug, suggestion, question or other), write a one-line subject of at most 255 characters and the details, at most 10,000. Name the page, what happened and what you expected. **3. Submit** Click **Submit Feedback**. A message thanks you and **Your feedback** below the form lists it. You can send up to 10 submissions an hour, and your organization up to 50 a day. Past that the page says when to try again. ## Follow it **Your feedback** lists what you sent, newest activity first, with a status badge: | Badge | What it means | | - | - | | Received | We have it. | | Acknowledged | We have read this. | | Accepted | We will build this. | | Planned | Work on this is scheduled. | | Shipped | It is live. The submission names the release and links its entry. | | Declined | We are not going to do this. We always say why. | Accepted, Planned and Shipped describe your suggestion only. You never see our internal planning cards, and a status can move back: a declined or shipped submission can be reopened as Acknowledged. A dot beside a row means we replied or changed its status since you last opened it. The feedback icon in the sidebar footer shows a dot too, until you open **Feedback**. When a submission is Shipped, its page shows **This is live** with the title and release of the What's new entry (open it from the version in the sidebar footer) that announced it, and a link to read it there. Open a row to read the conversation: our replies are signed **SRE Agent team**, status changes show as one line with their note, and your replies and your teammates' are in the same thread. Replying to a submission that is Received also marks it Acknowledged. Org admins see a switch above the list, **Mine** and **Everyone in** your organization, and can open and reply on a teammate's submission. A member sees only their own. A submission from another organization, or one you may not read, shows the same "not found" page as an id that does not exist. ## Reply Open the submission, write in **Reply** (at most 10,000 characters) and click **Send reply**. A conversation holds up to 200 messages; past that, send a new submission. You can send 30 replies an hour and 20 a day on one submission. ## Email updates We email the person who sent the feedback when the SRE Agent team replies, and when your submission is accepted, planned, shipped or declined. Details: * Only the sender gets the email, only about their own submission, and only while they are an active member of the organization. * Activity inside ten minutes is one email, and nobody receives more than ten of these a day. The dot and the list still show anything over that. * The email never contains internal notes or another submission, and it is signed SRE Agent team. * On a submission, turn **Email me about replies to this** off to stop the emails for that submission only. Only the sender sees this switch. ## Replies in your briefing Unread replies also appear in your personal morning briefing in Slack and on the Slack App Home, under "Replies to your feedback". An agent connected over MCP sees the same list when it calls `my_attention`. They are never shown in any Slack channel, only in your own DM, the morning briefing and App Home, and the team briefing never includes them. ## From an agent Agents connected over MCP with a personal token can read and answer feedback in your organization: * `submit_feedback` files a submission and answers its id. * `list_my_feedback` lists your submissions with status and unread replies. `scope: organization` lists everyone's and needs an org admin. * `get_my_feedback` reads one submission and its conversation, and marks your replies read. * `reply_to_my_feedback` adds a message. An API key is refused, because feedback records who to answer. See the [MCP reference](https://docs.sreagent.app/api-reference/mcp.md). ## Related * [Control data privacy and retention](https://docs.sreagent.app/guides/administer/data-privacy-and-retention.md): what feedback stores and who reads it. * [Organizations and roles](https://docs.sreagent.app/guides/administer/organizations-and-roles.md): what each role can do. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.