# Follow up only when they have not replied

> Schedule a WhatsApp message that sends only if the customer has not replied, or only if their labels still match. If the condition fails when it is due, nothing is sent.

A conditional follow-up is a message you schedule now and Whatsable sends later only if it still makes sense. Use it when a reminder should not reach someone who already replied or already bought.

The condition is checked when the message is due, not when you schedule it. If it fails, nothing is sent, and the scheduled message records why.

Schedule the message, add a [condition](/features/conditional-follow-ups), and send a [template](/features/message-templates) when the 24-hour window will be closed. Whatsable checks the condition when the message is due. If it fails, nothing is sent. Read [Send only when it still makes sense](/features/how-it-fits-together#send-only-when-it-still-makes-sense).

Scheduled messages, conditions included, are on Work, Growth, Pro and Agency, on the Free plan, and during the [14-day trial, no card](/mcp/plans#the-14-day-trial-no-card). An older account on the legacy free tier has them too. The Bulk Message plan does not.

## The reply condition

`no_reply` sends only if they have not replied. It is one of three kinds:

| Value | What it checks |
|---|---|
| `since_last_message` | No reply since your last message to them. In the inbox this is **No reply since last message**. |
| `never_replied` | They have never replied to any message of yours. In the inbox this is **Never replied to any message**. |
| `20m`, `45m`, `3h`, `6h`, `12h`, `24h`, `48h`, `72h` | No reply within that time of your last message: 20 minutes, 45 minutes, 3, 6, 12, 24, 48 or 72 hours. |

Those eight windows are the only durations. There is no free-form interval.

If you have not sent them a message yet, the reply check passes. `since_last_message` is stored as a window of two years measured from your last message, and `never_replied` as two and a half years measured from your first message. A reply inside that window stops the send.

## The label condition

`labels` is exactly one of `include` and `exclude`. You can pass a label id or a name. A name matches ignoring case and accents, and extra spaces are collapsed. Whatsable stores the label's current name on the scheduled message.

- `include`: send if the contact carries any of the labels when the message fires.
- `exclude`: send if the contact carries none of them. This is how you skip someone who already bought: exclude the label you add when they pay.

An unknown label is refused before anything is scheduled, with `404 label_not_found`.

You can set `no_reply` and `labels` together. Both have to pass. To send with no condition, leave `send_if` out. An empty object is refused.

## A rename or a delete

The condition keeps the name, not the label id. Renaming a label, or deleting it, leaves the stored name pointing at nothing. Whatsable cannot tell a rename from a delete.

The message is then not sent, for **Has any of** (`include`) and for **Has none of** (`exclude`). An `exclude` stays withheld on purpose: the contact may still be in that group under the new name, and sending would break the exclusion. The scheduled message says the label no longer exists.

## A text or a template

A text, buttons or a file still need an open 24-hour window at the moment the message fires. If the window has closed, the message ends `suppressed` with `window_closed`, and nothing is sent. A follow-up that might land after the window should be an approved template. A template is not limited by the window.

The API accepts a text even when the window is already closed. The inbox asks for an open window when you schedule a text there. Either way, the window is judged again at send time.

## Follow-up sequences with conditions

There is no separate drip product. A sequence is several scheduled messages, each with its own condition. Chain them in the inbox, in Zapier, Make or n8n, or with the API.

1. **One reminder, only if they have not replied.** Schedule one template for one day later with `since_last_message`.
2. **Three steps.** Schedule three templates, for example one day, three days and six days later. Give each `since_last_message`. A reply stops every step that has not fired yet.
3. **Stop when a label appears.** On each step, `exclude` the label you add when they buy, book or reply the way you wanted. A step that finds that label is not sent.

## Where you set it

- [Inbox](/features/inbox-conversations#schedule-a-message): 
The clock in the composer. **Send only if** and **Only if labels match**. Example: remind Maria on Friday at 10:00, but only if she has not replied.

- [Zapier](/integration/zapier/fields#action-schedule-a-follow-up-message): 
**Schedule a Follow-Up Message.** Set **Reply Condition** to "Recipient did not reply after my last message".

- [Make](/integration/make/fields#action-schedule-a-follow-up-message): 
**Schedule a follow-up Message.** The same reply condition, on that module.

- [n8n](/integration/n8n/fields#action-schedule-whatsapp-message): 
**Schedule WhatsApp Message.** Set **Recipient Reply Status : Send Only If**.

- [API](/api-reference/v1/scheduled-messages/schedule-message): 
`POST /v1/scheduled-messages` with `send_if`. Example: `{ "no_reply": "since_last_message" }`.

- [MCP](/mcp/workflows#schedule-a-message): 
Ask for it, or call `schedule_message` with `send_if`. `get_scheduled_message` says why a skipped one did not send.

A condition created in Zapier, Make, n8n or the inbox can come back from the API as `{ "other": true }` when it is not one of the values above. That means a condition is set, and this API cannot show its rule.

## When it does not send

The message stays in the list with status `suppressed`. `suppressed_reason` is a code:

| Code | Why nothing was sent |
|---|---|
| `reply_window` | They replied inside the reply condition. |
| `label_condition` | The labels did not match, or a named label no longer exists. |
| `reply_gate` | A reply rule set by an older integration failed. |
| `window_closed` | A text fired after the 24-hour window had closed. |
| `template_not_approved` | The template was not approved when it fired. |
| `template_not_sendable` | The template could not be sent. |
| `number_not_sending`, `number_over_plan`, `plan_inactive`, `feature_not_in_plan` | The number or the plan could not send. |
| `other` | A refusal with no code, including a row stored before reasons were recorded. |

A message that fails while sending, rather than being skipped, ends `failed` and carries the same error as a message. Cancel a `pending` one before it fires. A row that is already firing cannot be cancelled.

## FAQ

<details>
<summary>Does a broadcast use these conditions?</summary>

No. A broadcast sends the template to the list you give it. It has no `send_if`. To skip people, build the list from a label, or schedule one message per person with `exclude`. See [Broadcasts](/features/broadcasts).

</details>

<details>
<summary>What if I rename the label after I schedule the message?</summary>

The message is not sent. The condition stored the old name. This is true for include and for exclude.

</details>

<details>
<summary>Can I pick any number of hours?</summary>

No. The windows are 20 minutes, 45 minutes, 3 hours, 6 hours, 12 hours, 24 hours, 48 hours and 72 hours, plus "since your last message" and "never replied".

</details>