Whatsable
If your WhatsApp auto-reply or Zapier, Make or n8n automation stops working after someone on your team answers a chat, it is usually not broken. It is paused. Many setups stop sending a conversation to your automations for a while after a human reply, so the bot and your team do not both answer. Change the pause length, or set that chat to "Always send".
Last updated: November 12, 2026.
I get this question on support calls almost every week. Someone builds a simple flow: a new WhatsApp message comes in, Zapier adds a label and sends a quick reply. It works on day one. A few days later, some chats get the reply and some do not. The trigger looks fine, the Zap shows no error, and nothing seems to explain why one customer got the message and the next one did not. Most of the time, the answer is one setting that does exactly what it was designed to do.
Why does my WhatsApp automation stop working after my team replies?
Because your automation and your team are both trying to own the same conversation. If a bot keeps firing while a person is typing, the customer gets two answers, or a canned message in the middle of a real conversation. To prevent that, most WhatsApp tools stop the automation for a conversation as soon as a human replies.
In Whatsable this lives on each outgoing webhook, which is what Make, Zapier and n8n listen to. The option is called Pause when your team replies. When it is on:
- A reply typed by a person stops that one chat from reaching that endpoint. The default pause is 24 hours, and you can set it in minutes, hours or days.
- The timer starts again every time your team replies, so an active human conversation stays paused.
- Replies that come from your AI agent, a broadcast or the API do not start the pause. Only a person counts: a team member in the inbox, or someone answering from the WhatsApp Business app on a number that uses Coexistence.
- Other chats are not affected. The pause is per conversation.
So the pattern "it works for new leads but not for some older chats" is the giveaway. In those older chats, someone on your team wrote a message recently, and the automation is waiting for the pause to end.
How do I check if a chat is paused?
- Open the conversation in the Whatsable inbox.
- Look at the Automations section in the contact panel. It shows the mode for that chat and, if it is paused, the time it starts again, for example "Paused until 14:30 — someone from your team replied."
- If only some of your endpoints pause, it shows how many, for example "1 of 2 automations paused".
- Go to Settings → Webhooks and look for the "Pauses for replies" badge on the endpoint your Zap or scenario uses. That tells you which flow is set to pause.
A quick test: send "hello" from your own phone to the business number in a chat where nobody from your team has written. If the automation fires there and not in the chat you are worried about, you have found it.
How do I keep my auto-reply running even when my team answers?
You have three choices. Pick by what the automation does, not by what is easiest to click.
| Option | Where | Use it when |
|---|---|---|
| Keep the pause, shorten it | Settings → Webhooks → edit the endpoint → Pause for | The automation replies to customers, but you want it back sooner than 24 hours. |
| Turn the pause off for the endpoint | Settings → Webhooks → edit the endpoint | The automation never writes to the customer. It only logs, labels or updates your CRM, so it can never double-reply. |
| Set one chat to "Always send" | Inbox → contact panel → Automations | One conversation must always reach your automations, even while your team is replying. |
The per-chat setting has three modes: Automatic (follows the endpoint's pause rule), Always send (never pauses for this chat) and Never send (this chat never reaches your automations). The chat setting wins over the endpoint rule in both directions.
My rule of thumb: if the flow only records things (a label, a CRM note, a row in a sheet), turn the pause off, because you want every message recorded. If the flow talks to the customer, keep the pause, because a bot answering over your sales rep is worse than a late reply.
Should the AI agent and Zapier run on the same chats?
Usually not, and this is the second thing I check on these calls. If you have a Whatsable AI agent answering chats and a Zap that also sends an auto-reply, the customer can get both. Decide which one owns the first reply. Then either turn off the Zap's reply step, or keep the AI agent off for those conversations. The AI agent has its own pause: when a person replies, the agent steps back in that chat. After a reply from the inbox, someone turns it back on for that chat. After a reply from the WhatsApp Business app, it takes the chat back once the wait you set in the agent runs out. You can read more in the AI agents overview.
One more trap: if your Zap labels chats so you know which campaign they came from, and the label is missing on some chats, that is the same pause. The label step never ran. Turn the pause off for that endpoint, because labeling never writes to the customer.
What if the automation still does not fire?
If the chat is not paused and the mode is Automatic or Always send, check these in order:
- The endpoint's events. An endpoint can receive incoming messages, outgoing messages or both. An auto-reply needs incoming.
- The webhook URL. If you rebuilt the Zap or the scenario, it may have a new URL. Create a new endpoint with the new URL and remove the old one.
- Filters in Zapier or Make. A filter that checks for a keyword or a label will silently stop the run. Look at the run history in Zapier's Zap history or in Make's scenario history.
- The 24-hour window. A free-form reply only reaches a customer within 24 hours of their last message. Outside it, WhatsApp only accepts an approved template. Meta explains this in its WhatsApp pricing and customer service window docs.
If you want to build the flow from scratch, the guide to triggering a webhook from the WhatsApp Business app and the n8n integration page show the setup, and the docs list every field the webhook sends. Make, Zapier, n8n and webhooks are part of the Pro and Agency plans on the pricing page.
FAQ
Why does my WhatsApp auto-reply work for some chats and not others?
Most often because someone on your team replied in the chats where it fails. With "Pause when your team replies" on, those chats stop reaching your automation until the pause ends. Check the Automations section of the chat in the inbox.
How long does the automation pause after a team reply?
In Whatsable the default is 24 hours, and you can change it per endpoint in minutes, hours or days. The timer restarts each time your team replies.
Do AI agent or broadcast messages pause my automations?
No. Only a message typed by a person pauses them: a team member in the inbox, or a reply from the WhatsApp Business app. AI agent replies, broadcasts and API messages do not.
Can I turn the pause off for one customer only?
Yes. Open the chat, go to Automations in the contact panel and choose "Always send". That chat keeps reaching your automations even while your team is replying. Every other chat keeps the normal rule.
How do I stop automatic replies on WhatsApp for one chat?
Choose "Never send" in the same Automations section. Nothing from that chat is sent to Make, Zapier or n8n until you change it back.