Wati provides chatbot status updates in the Team inbox to help you track chatbot activity during conversations. These statuses show whether a chatbot has started, finished, expired, or was prevented from running.

By understanding these status updates, your team can quickly monitor chatbot behavior, identify issues, and troubleshoot conversations more efficiently.

Chatbot status updates give you visibility into what is happening during automated conversations.

With these updates, you can:

These insights make it easier for your team to manage conversations and resolve issues faster.

The Team inbox displays several chatbot status indicators to show the current state of chatbot activity.

Started means the chatbot has successfully begun running in the conversation. This usually happens when:

This status confirms that the chatbot has been triggered and is currently handling the conversation.

Ended indicates that the chatbot has completed its workflow and is finishing its process.

This status appears when the chatbot reaches the end of its conversation flow.

It helps you identify when an automated interaction has concluded and when a human agent may need to take over.

Expired means the chatbot stopped running because its allowed time window ended before the conversation was completed.

This can happen when:

This status helps you identify conversations that stopped unexpectedly or remained inactive for too long.

Blocked appears when a chatbot cannot start because another chatbot is already active in the same conversation.

For example:

Wati will block the second chatbot to prevent conflicts.

This behavior prevents issues that previously occurred when multiple chatbots tried to run simultaneously in a single conversation.

You can view chatbot status updates directly in the Team inbox while monitoring or handling customer conversations. These indicators provide real-time visibility into chatbot activity so your team can quickly understand what is happening in the chat.

You may want to review chatbot statuses when:

Checking these statuses helps you quickly identify the cause and adjust your automation setup if needed.

Chatbot status updates are indicators shown in the Team inbox that display the current state of chatbot activity during a conversation. These statuses help teams understand whether a chatbot has started, finished, expired, or was prevented from running.

Chatbot status updates provide visibility into automated conversations. They help teams confirm when a chatbot starts running, identify when a chatbot completes its flow, detect when a chatbot stops due to inactivity or time limits, and understand when a chatbot cannot start because another chatbot is already running.

Chatbot status updates can be viewed directly in the Team inbox while monitoring or handling customer conversations. These indicators show the current chatbot activity within the conversation.

The Started status means the chatbot has successfully begun running in the conversation. This can happen when a customer sends a message that triggers a chatbot, when a rule condition activates a chatbot, or when a chatbot is started manually.

The Ended status indicates that the chatbot has completed its workflow and reached the end of its conversation flow. This status shows that the automated interaction has finished and a human agent may need to continue the conversation if required.

The Expired status means the chatbot stopped running because its allowed time window ended before the conversation was completed. This can occur if the customer becomes inactive during the chatbot flow or if the chatbot exceeds the allowed time to complete the interaction.

The Blocked status appears when a chatbot cannot start because another chatbot is already running in the same conversation. Wati prevents multiple chatbots from running simultaneously to avoid conflicts in the conversation flow.

You may want to check chatbot statuses when a chatbot does not start as expected, when a conversation ends earlier than planned, when a customer stops responding during a chatbot flow, or when multiple chatbots are configured for the same conversation. Checking these statuses helps identify what happened during the automated interaction.