Most automation rules run the moment something happens: a conversation is created, a message arrives, a status changes. A rule that runs after a wait works differently. It starts a timer when something happens, waits for the time you set, and then checks the conversation again. It runs its actions only if the conversation is still in the state you were waiting for.
Use it for work that depends on something not happening:
-
Following up when a customer stops replying.
-
Escalating when a customer has been waiting and nobody on the team has answered.
-
Resolving, labeling, or reassigning conversations that have sat in one status for too long.
Before you start
-
Plan: Automations that run after a wait are available on the Business and Enterprise plans on Chatwoot Cloud. On self-hosted installations, a Super Admin turns on Delayed Automations for the account.
-
Permissions: Only administrators can create, edit, or delete automation rules.
Create a rule that waits
-
Go to Settings → Automation.
-
Click Create Automation.
-
Enter a Rule Name and a Description.
-
Under When should this rule run?, select Run after a wait.
-
Under Wait condition, choose what the rule waits for, how long it waits, and optionally which inbox it applies to.
-
Optionally click Add Condition to narrow the rule further.
-
Under Actions, add one or more actions to run when the wait ends.
-
Click Create.
If you click Create Automation while you are on the Runs after a wait tab, the form opens with Run after a wait already selected.

Wait conditions
Every rule that waits starts from one of three wait conditions. Each one has its own rule for when the clock starts and what stops it.
Conversation stays in a status
Pick a status: Open, Pending, Snoozed, or Resolved.
-
The clock starts when a conversation moves into that status.
-
The rule is skipped if the conversation changes status before the wait ends, even if it changes back. Moving from Pending to Open and back to Pending starts a new wait from the second move.
-
Typical uses: resolve conversations that have been pending for a few days, label conversations that have stayed open too long, or send the transcript an hour after a conversation is resolved.
Customer hasn't replied
-
The clock starts when someone on your team sends a reply.
-
The rule is skipped if the customer replies before the wait ends.
-
The clock restarts with each new reply from your team, so the wait is always measured from your latest message.
-
Typical uses: check in with a customer who has gone quiet, or move the conversation to Pending.
No teammate has replied
-
The clock starts when a customer sends a message that is waiting for a reply.
-
The rule is skipped if anyone on your team, or a bot, replies before the wait ends.
-
The clock does not restart if the customer sends more messages. The wait is measured from the first unanswered message.
-
Typical uses: escalate to another team, raise the priority, or reassign the conversation.
Set how long to wait
Enter a number and choose Minutes, Hours, or Days. The wait can be anywhere from 10 minutes to 30 days.
Chatwoot checks for waits that have ended every few minutes, so actions can run a few minutes after the exact time. Avoid rules that depend on minute-level precision.
Limit a rule to an inbox
Use the Inbox field in the wait condition to apply the rule only to conversations in one or more inboxes. Leave it empty to apply the rule to every inbox.
Add more conditions
Rules that wait for Customer hasn't replied or No teammate has replied can have more conditions. Click Add Condition and pick an attribute such as status, assignee, team, priority, labels, or a custom attribute. Combine conditions with AND or OR.
Rules that wait for Conversation stays in a status can only use the status and inbox in the wait condition. They do not have Add Condition.
Conditions that check whether an attribute changed are not available on rules that wait. The rule checks the conversation as it is when the wait ends, not what happened during the wait.

What happens when the wait ends
When the wait ends, Chatwoot checks the conversation again:
-
Is the wait condition still true? For example, the customer still hasn't replied, or the conversation is still pending. If not, the rule is skipped.
-
Do all the other conditions still match? For example, the conversation is still in the Support inbox and still open. If not, the rule is skipped.
-
If both checks pass, the actions run.
A rule runs at most once for each wait. After it runs, the next qualifying event starts a new wait. For example, a new reply from your team starts a new Customer hasn't replied wait.
Actions
Rules that wait can use the same actions as other automation rules, including:
-
Send a message, add a private note, or send an attachment.
-
Assign or unassign an agent or a team.
-
Add or remove labels.
-
Change the priority.
-
Change the status, including resolve, open, mark as pending, or snooze.
-
Mute the conversation.
-
Send an email to a team, send a webhook event, or send an email transcript.
Send the transcript to the contact
The Send an Email Transcript action has a Use contact's email button. It fills the address with {{contact.email}}, so the transcript goes to the conversation's contact. You can combine it with other addresses, separated by commas. This button is also available on the same action in macros.

Manage rules that wait
The Automation page has two tabs: Runs instantly and Runs after a wait. Each rule that waits shows how long it waits, for example Runs after 1d or Runs after 30m.

-
Turning a rule off cancels every wait that rule has started. Turning it back on does not bring them back. New waits start from the next qualifying event.
-
Editing a rule (its conditions, actions, wait, or active state) cancels the waits it had already started, so nothing runs under the old settings. New waits start from the next qualifying event.
-
Cloning a rule creates a copy with the same wait and conditions.
Waits that were already running resume when the feature is turned back on, and they still go through the checks above before any action runs.
Things to know
-
Only new activity starts a wait. A rule does not look back at conversations that are already in the state it waits for. Those conversations are picked up the next time something happens on them, such as a status change or a new message.
-
Actions can run a few minutes late. Waits are checked every few minutes.
-
Each wait runs once. A rule will not send the same follow-up twice for the same quiet stretch.
Examples
| Goal | Wait condition | Wait | Extra conditions | Actions |
|---|---|---|---|---|
| Check in with quiet customers | Customer hasn't replied | 1 day | None | Send a message, add the label follow-up |
| Escalate unanswered chats | No teammate has replied | 30 minutes | Inbox is Support, status is Open | Assign the Escalations team, change priority to High |
| Close stale pending conversations | Conversation stays in a status: Pending | 3 days | None | Resolve the conversation |
| Flag old wholesale orders | Conversation stays in a status: Open | 2 days | Inbox is Wholesale Orders | Add the label stale |
| Send a copy after resolving | Conversation stays in a status: Resolved | 1 hour | None | Send an email transcript to the contact |
Troubleshooting
My rule didn't run for a conversation that has been pending for days. The conversation was probably already pending before the rule was created or last edited. Waits start only from new activity. The next time the conversation changes status, it will be picked up.
My rule ran a few minutes after the wait ended. This is expected. Waits are checked every few minutes.
My follow-up didn't go out even though the wait ended. Something changed during the wait. The customer replied, a teammate replied, the status changed, or one of the extra conditions no longer matched. The rule was skipped on purpose.
I can't see the Runs after a wait option. The feature isn't turned on for your account. On Chatwoot Cloud, check your plan. On self-hosted installations, ask your Super Admin to turn on Delayed Automations.
I don't see Add Condition on my rule. Rules that wait for Conversation stays in a status only support status and inbox. Choose Customer hasn't replied or No teammate has replied if you need more conditions.