> For the complete documentation index, see [llms.txt](https://helpdocs.ycloud.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.ycloud.com/help-center/journey/components-and-features-introduction/message-status-rule.md).

# Message Status Rule

A component for determining the status of template messages, supporting the judgment of read and replied statuses. It is used to divert customers who react differently after receiving messages.

Example scenario: After sending a welcome message, for customers who reply, we automatically send an activation message. For those who receive the message but do not reply, we refrain from further disturbance.

## Settings for Message Status Rule:

**Template to be Judged**: Select the template whose status needs to be determined.

**Waiting Time**: The status of the template message will be judged within the set time.

**Subsequent Connection Nodes**:

1. When the selected status is met within the waiting time.
2. When the selected status is not met after the waiting time ends.

<figure><img src="/files/Fr4Y0stnSUvpac8QNaHr" alt=""><figcaption></figcaption></figure>

## Addition Methods

### Method 1: Direct Connection After Sending Template

When you move the mouse over the connection node of Send template, two quick options appear, which are to judge whether the message has been read or replied. Clicking will automatically connect a new Message status rule component.

<figure><img src="/files/uvQnOS8FiJwh298h1OQJ" alt=""><figcaption></figcaption></figure>

### Method 2: Manually Adding the Component

Manually added Message status rule will not automatically configure the template and connect. You need to manually select the template and the status to be judged in the settings page. When selecting a template, you can only choose templates that have already been selected in all Send template components within the current Journey. After selecting the template, you need to manually connect the preceding process.

<figure><img src="/files/QfiUYumwh9pfezPd720h" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1xDAnsr9g2YUSBa50RGG" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocs.ycloud.com/help-center/journey/components-and-features-introduction/message-status-rule.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.