> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/hints/automatically-mark-incoming-whatsapp-messages-as-read.md).

# Automatically mark incoming WhatsApp messages as read

Learn how to automatically mark incoming WhatsApp messages as read using the auto\_read\_messages channel setting

The `auto_read_messages` channel setting allows Whapi.Cloud to automatically mark every new incoming message as read.

This is useful for chatbots, AI assistants, support automation, and other workflows where no human operator opens the chat manually.

When automatic reading is enabled:

* The sender sees blue check marks;
* The unread message counter disappears from the chat on the connected WhatsApp account;
* Your automation does not need to send a separate API request to mark each message as read.

### When this setting is useful

Automatic reading is especially helpful when:

* A chatbot handles conversations without human involvement;
* You want users to see that their message was received and processed;
* An AI assistant replies automatically;
* Unread counters should not accumulate on the connected WhatsApp account;
* Your workflow does not require manual message review before marking messages as read.

For automated conversations, read receipts can make the interaction feel more responsive and natural. They confirm that the message has reached the system, even before the automated reply is sent.

### Enable automatic message reading

Use the [**Update channel settings**](https://whapi.readme.io/reference/updatechannelsettings) method:

`PATCH https://gate.whapi.cloud/settings`

Example request:

```bash
curl -X PATCH "https://gate.whapi.cloud/settings" \
  -H "Authorization: Bearer <CHANNEL_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "auto_read_messages": true
  }'
```

### Parameter values

* `true` — every new incoming message is automatically marked as read;
* `false` — incoming messages are not marked as read automatically.

The default value is:

```json
{
  "auto_read_messages": false
}
```

When the setting is disabled, messages must be marked as read manually through the API.

### Disable automatic message reading

To return to manual read management, send:

```bash
curl -X PATCH "https://gate.whapi.cloud/settings" \
  -H "Authorization: Bearer <CHANNEL_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "auto_read_messages": false
  }'
```

Use `false` when a human operator must review messages before the sender receives a read confirmation.

***

### Mark individual messages as read

If you do not want to mark every incoming message as read automatically, you can manage read receipts selectively.

Use the [**Mark message as read**](https://whapi.readme.io/reference/markmessageasread) method for a specific message:

`PUT https://gate.whapi.cloud/messages/{MessageID}`

Replace `{MessageID}` with the ID of the message you want to mark as read.

This approach is useful when your workflow should only confirm selected messages after they have been processed by a bot, reviewed by an operator, or matched specific conditions.


---

# 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://support.whapi.cloud/help-desk/hints/automatically-mark-incoming-whatsapp-messages-as-read.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.