See how your chatbot is doing

Once a chatbot is live, two buttons appear at the top of its canvas: Results, for the numbers, and Runs, with one row for each time the chatbot started with a customer.

Results: where customers give up

Click Results and every box shows its numbers for the last 30 days of the live version.

The canvas with Results switched on: above each box a small line of numbers — reached, answered, stopped and here now — The number to look for is 'stopped' — where customers give up. A question many people stop at usually needs rewording.

reached — customers who got to this step;
answered — of those, how many replied the way it asked (only on steps that ask something);
stopped — runs that ended here without finishing: the customer went quiet, typed something else, or someone on your team took over;
here now — runs waiting on this step right now.

Each run counts once per step, however many times it comes back to it.

Runs: every time it started

Click Runs to see every run the chatbot has had, newest first, and how each one ended. Use the buttons at the top to show only those in progress, finished, or gone quiet.

The Runs panel listing runs with customer names, when they started, where they ended and a status such as In progress, Handed over or Finished — Each row is one run: one customer, from the chatbot starting to how it ended.

Open one to read it step by step: what they picked or typed at each step, which way a condition went, what they told the chatbot, and how it ended. Open chat takes you to the conversation in your inbox.

One run's trail: what the customer told the bot (name and branch), then each step reached and answered with times, ending with the hand-over to the AI assistant — The answer to 'what did the bot tell this customer, and why'.

In your inbox

When a chatbot is in the middle of a run, the chat shows it above the messages: which chatbot, and where it's waiting.

Replying takes over. The moment someone on your team sends a message, the chatbot stops, and automated replies — Instant Replies, the away message, the AI assistant, other chatbots — pause on that chat for 24 hours, so nothing talks over you.
Stop ends the chatbot without you having to say anything.
Closing the chat, or Resume on the "Automated replies are paused" bar, hands it back to automation early.

Send the answers somewhere else

Each time a chatbot finishes a run or hands it over, Wap2b can send the customer's answers to your own system — a CRM, a spreadsheet tool, anything that accepts a webhook. Add an endpoint under Integrations → Webhooks and choose Chatbot completed; the API reference shows exactly what arrives.

Answers can also be kept on the contact itself — choose a contact field under "Also save on the contact" on a question — and from there they're in your contact list, your exports, and your broadcasts.

Still stuck?

If this page did not solve it, tell us what you were trying to do and we will pick it up from there.

Open a support ticket