> For the complete documentation index, see [llms.txt](https://docs.zipchat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipchat.ai/tips/ignore-spam-conversations.md).

# Ignore spam conversations

You can instruct ZipChat to ignore entire conversations in order to reduce spam and avoid wasting AI responses.

To do this, go to **AI Training** in your ZipChat dashboard and select **Prompt & Tools**. Scroll down to the section called **Skip Conversation** and click **Activate**.

In this area, you can define rules that tell ZipChat to automatically skip specific conversations. For example, you can configure it not to respond to emails coming from a particular email address or even from an entire domain — such as any address ending in *@test.com*.

This ensures that valuable AI responses are not used on irrelevant or unwanted conversations.

You can also set rules to prevent ZipChat from replying to internal emails sent by members of your own team.


---

# 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.zipchat.ai/tips/ignore-spam-conversations.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.