> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints.md). # Spam Complaints - [How Batch Collects Spam Complaints?](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/how-batch-collects-spam-complaints.md): Learn how Batch uses feedback loops from 20+ mailbox providers to automatically reduce recipient frustration, protect your sender reputation, and give you actionable insight into your sends. - [How Does Batch Handle Spam Complaints?](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/how-does-batch-handle-spam-complaints.md): Learn how spam complaints impact your email deliverability and Batch handles complaints to keep your sender reputation safe - [Monitoring the Spam Complaint Rate](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/monitoring-the-spam-complaint-rate.md): A practical guide to understanding, tracking, and responding to spam complaints - [Troubleshooting High Spam Complaint Rates](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/troubleshooting-high-spam-complaint-rates.md): High spam complaint rates can permanently damage your sender reputation and email deliverability. Here are some strategies to locate the source of complaints and safeguard your reputation. --- # 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://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints.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.