BotSpot · developer docs · observability
When an agent does not reply, or answers wrongly, you need to know where to look. BotSpot keeps two kinds of logs in two places, on purpose. This page shows which is which, and how to find the reason a message was not answered in under a minute.
The short answer
Find your question, then go to the screen next to it.
| I want to know | Open | In |
|---|---|---|
| My agent gives a wrong answer while I am building it | Agent, Runs, or Test Run | Workbench |
| A customer messaged my WhatsApp number and got no reply | My AI, Manage, Channels, WhatsApp, Customer conversations | MyCrew |
| Is my WhatsApp number connected properly? | Agent, Channels (health badge and Recent problems) | Workbench |
| What did one reply cost, and who paid? | Customer conversations, open the agent run under a message | MyCrew |
| I want to limit how much my channel can spend | Channels, WhatsApp, Who can chat | MyCrew |
| I am a customer and my message was not answered | Channels, WhatsApp, My messages | MyCrew |
| Which version of my agent is live for customers? | Agent page, Choose internal version | Workbench |
Workbench logs and MyCrew logs
Workbench is where you build. MyCrew is where your agent works for real people. The logs follow the same line, so you always know which screen to open.
Workbench · building
Nobody outside your team is in these logs.
MyCrew · live
This is where real customers appear.
Why not put everything in one place? Because customers are not part of building. Keeping their conversations in MyCrew means a test you run while building never mixes with a real customer's chat, and what a customer wrote stays with the people who serve them. Inside MyCrew, though, you do not hop between screens: each message shows its own agent run, so one thread answers the whole question.
If you sell your agent to other businesses: you see nothing of their customers. The business that bought it owns its number and its logs. If they hit a problem, they share that one conversation with you.
Versions
Before you connect WhatsApp, the agent should work in Test Run and be released internally. The channel then runs exactly that version. Edits you make afterwards do not reach your customers until you release them, and every release is recorded in the version history.

Step by step


You can only see these cards when you are signed into MyCrew as the organisation that owns the channel. If you belong to more than one organisation, pick the right one at sign-in.
Reference
These are the headlines you can see on a message, what each means, and who can fix it.
| You see | What it means | What to do | Who |
|---|---|---|---|
| This channel has no owner to bill | The channel never recorded which wallet pays for it, so Botspot cannot charge any reply and skips every message. This was a Botspot fault in channels created before October 2026. | Contact support with the channel name. New channels record the owner automatically. | Botspot support |
| The wallet that pays for this channel is empty | Replies are paid from the channel owner's BICS balance, and it ran out. | Add BICS in Settings, Plan. New messages are answered again straight away. | You |
| The run was refused because it could not be billed | The agent never started, because Botspot could not charge the run to the owner's wallet. | Check the owner's BICS balance. If it is fine, contact support with the reference code. | You |
| Your channel's daily spend limit was reached | The channel used its BICS limit for the last 24 hours, so new messages wait. | Raise the limit under Who can chat, or wait: the limit counts a rolling 24 hours, not a calendar day. | You |
| This person is sending messages too fast | One person went over the per-person limit for your channel. | Raise the per-person limit under Who can chat if this is a real customer. | You |
| This person has not linked their number | Your channel is set to "Only people who link their number", and this sender has not linked theirs. | Ask them to link their number, or switch the channel to "Anyone". | The customer |
| This person opted out | They sent STOP earlier. Botspot sends them nothing until they reply START. | Nothing to fix. This protects them and you. | Nobody, it is by design |
| The agent failed to run | The message reached your agent, but a step in the workflow failed. | Open the agent in Workbench, run the same message in Test Run, and read the failing step. | You |
| The agent ran but produced no reply | Every step finished, but the answer was empty, so nothing was sent. | Check the last step of the workflow in Test Run. | You |
| WhatsApp rejected the reply | The agent answered, but WhatsApp refused to deliver it. The usual causes are an expired access token, or a reply sent more than 24 hours after the customer last wrote. | Update the access token in Workbench, Channels, Update credentials. | You |
| This channel is not connected to a live agent | The channel is disabled or deleted, or its agent has no released version. | In Workbench, release the agent internally, then check the channel is enabled. | You |
| Message had no text | Photos, voice notes and files are saved but do not start the agent yet. | Nothing to fix. Customers need to type their message. | Nobody, it is by design |
Inside a message
When the agent did run, a box under the customer's message shows Agent run completed or failed, how long it took, how many BICS it cost and how many steps it had. Open it to see every step with its own time. It shows the shape of the run, never what a step produced and never what the customer typed.

If a message never started the agent, there is no run box. The red reason box tells you why instead, which is the whole point: a message that stops early creates no run, so Runs in Workbench never lists it.

Setting up a number
In Workbench, open the agent and its Channels tab. The badge says Connected only when the channel can really reply. If it cannot, the badge says Needs attention and a red card explains why. Below it, Recent problems lists the last few messages that were not answered.

Who pays
In MyCrew, on the WhatsApp tab, Who can chat has two choices:
Because on "Anyone" you pay for strangers, there are two limits, and you change both. The default is 20 messages per person per hour and 50 BICS per 24 hours for the whole channel. Turn a limit off and it is unlimited, which means anyone who messages your number can spend your BICS without a stop. The card shows what the channel used in the last 24 hours.

The 24 hours are a rolling window, not a calendar day, so the allowance never comes back all at once at midnight. The check is a soft limit. Two messages arriving at the same moment can both pass, so a channel can overshoot by one reply. Your wallet history is the exact record.
For customers
If you messaged an AI on WhatsApp and nothing came back, open it in MyCrew, then Channels, WhatsApp, and look at My messages. Each message says Answered or Not answered, how far it got, and what to do. You are never shown the owner's billing or settings. If a message failed, note the short reference code and give it to the AI's owner or to support.

Asking for help
With the reference code, support can read the exact step where the message stopped, so you do not need to describe it.
Troubleshooting
I do not see Customer conversations or Who can chat.
You are signed in as an organisation that does not own the channel. Sign out and in, and pick the owning organisation. Customers only see My messages.
An older message has no reason.
Reasons are recorded from October 2026. Messages sent before that show the text but not why they stopped.
The customer sees nothing when a limit is reached.
Today a customer who hits a limit gets no WhatsApp reply. You see the reason on your side.
Why is my Workbench Runs tab empty for WhatsApp?
Runs lists your own test and build runs. Real customer messages live in MyCrew, with the run inside each message.