> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/how-tos/sending-feedback.md). # Send Feedback We value and encourage user feedback. Hearing what could help make BugSplat better for you is one of the best tools we have for improving our product offering. Many of our best features over the years have come out of user feedback and participation. If there's something you think we need to know - make sure to pass it along! ### In-app The first way to provide feedback is to click the **Feedback** button (the megaphone icon in the left navigation), which opens our product feedback tool. Our support team gets alerted as soon as any feature request or bug is submitted. Note: The feedback tool loads through our Intercom integration. If clicking **Feedback** doesn't open anything, it is likely getting blocked from loading by some tool in your browser. ![](https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fgit-blob-73bba589311a828c86602a2f52c398faa3ab8a91%2Ffeedback-bs.gif?alt=media) ### Email Please also feel free to contact the support team with feedback via email by sending a note to l --- # 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.bugsplat.com/education/how-tos/sending-feedback.md?ask=&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.