20 October 2026
Chat Flows "If no reply" gains an optional closing message the customer receives when a run is closed for inactivity; the inactivity reminder no longer counts as a message from your team, so a customer who answers late starts a fresh run; and on Business API numbers a free-text send outside the 24-hour window no longer vanishes — the composer locks and says why.
A refused send outside the 24-hour window says why
Fixed. On a WhatsApp Business API number, typing to a contact who had never written (or whose only "incoming" item was a missed call) left the composer open; the send was refused by the 24-hour rule and the message simply disappeared. Now the composer locks for such contacts with the explanation and the Pick a template button, in WASync Chat and in the CRM tab alike, and if a send is still refused the reason stays on screen until the customer replies. Templates on Business API numbers.
A closing message when a run stops for inactivity
New. If no reply has a fourth field, When the run closes, send this message, both in Flow settings and on each question. Write something like "We didn't hear back, so this conversation was closed. Whenever you want to continue, just send us a new message here." and the customer receives it the moment the run closes. Leave it empty to close silently, as before. The preview simulator plays it after the close. Inactivity reminders and closing.
The reminder is the bot's message, not your team's
Fixed. The inactivity reminder was stored like a message typed by a person. For a customer who answered only after the run had closed, that made their reply look like an answer to your team, and Flows do not start on a reply to your team kept the flow from starting again. Reminders and closing messages are now recorded as the flow's own messages: they never count as a colleague taking over, and a late reply starts a new run as the documentation always said.