Free Intro Class
    Botspot Logo

    BotSpot · developer docs · observability

    Where to check what your agent did

    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.

    Page version
    1.0
    Updated
    12 Oct 2026
    Shows
    Workbench and MyCrew, 12 Oct 2026 release

    The short answer

    What do you want to know?

    Find your question, then go to the screen next to it.

    I want to knowOpenIn
    My agent gives a wrong answer while I am building itAgent, Runs, or Test RunWorkbench
    A customer messaged my WhatsApp number and got no replyMy AI, Manage, Channels, WhatsApp, Customer conversationsMyCrew
    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 messageMyCrew
    I want to limit how much my channel can spendChannels, WhatsApp, Who can chatMyCrew
    I am a customer and my message was not answeredChannels, WhatsApp, My messagesMyCrew
    Which version of my agent is live for customers?Agent page, Choose internal versionWorkbench

    Workbench logs and MyCrew logs

    Why there are two places

    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

    Development logs

    • Test Runs and your own runs, step by step
    • Whether your WhatsApp number is wired correctly
    • The version of the agent you released
    • A short list of recent problems on a channel

    Nobody outside your team is in these logs.

    MyCrew · live

    Customer logs

    • Every customer who messaged your number
    • Each conversation, with the agent run inside each message
    • Why a message was not answered, and what it cost
    • Who can chat, and your spend limits

    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

    A channel runs the version you released

    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.

    1. 1
      Open the agent in Workbench and run it in Test Run until it answers as you want.
    2. 2
      At the top of the agent page, open Choose internal version and pick the version to go live.
    3. 3
      Now open the Channels tab and connect your WhatsApp number. Without a released version, Connect stays disabled and tells you why.
    The Choose internal version menu at the top of an agent page in Workbench
    Workbench, agent page: the "Choose internal version" menu. A channel runs the version you pick here.

    Step by step

    A customer got no reply: find out why

    1. 1
      Open MyCrew, then My AI, choose the agent, then Manage.
    2. 2
      Open the Channels tab, then WhatsApp.
    3. 3
      Under Customer conversations, find the customer. A red Last message not answered badge means the problem is in their latest message.
    4. 4
      Click the customer. The message that was not answered has a red box that says why and what to do.
    5. 5
      Open Steps in that box to see how far the message got. The last step is where it stopped.
    The Customer conversations card in MyCrew listing customers with a Last message not answered badge
    MyCrew, Channels, WhatsApp: every customer who messaged your number. A red badge means the last message was not answered.
    A customer conversation in MyCrew with a red box explaining why a message was not answered
    MyCrew, one customer: the red box says why a message was not answered and what to do.

    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

    Reasons a message is not answered

    These are the headlines you can see on a message, what each means, and who can fix it.

    You seeWhat it meansWhat to doWho
    This channel has no owner to billThe 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 emptyReplies 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 billedThe 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 reachedThe 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 fastOne 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 numberYour 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 outThey 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 runThe 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 replyEvery 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 replyThe 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 agentThe 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 textPhotos, 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

    See the agent run, and what it cost

    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.

    An expanded agent run box in a MyCrew conversation showing steps, timings and BICS cost
    MyCrew, one customer: the agent run that answered a message, with each step, its time and the BICS it cost.

    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.

    The Runs tab in Workbench listing recent test runs with status, time and cost
    Workbench, Runs tab: your own Test Runs and builds. Customer messages are not listed here.

    Setting up a number

    Check your number is wired correctly

    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.

    The Channels tab in Workbench showing a red Needs attention badge and a problem card
    Workbench, Channels tab: "Needs attention" appears when the number cannot reply, with the reason.

    Who pays

    Who can chat, and how much it can cost

    In MyCrew, on the WhatsApp tab, Who can chat has two choices:

    • Anyone. Customers just message your number. No account, no linking. You pay for the replies.
    • Only people who link their number. For a closed group. Each person connects their number to a BotSpot account first.

    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 Who can chat card in MyCrew with Anyone selected and two spend limits
    MyCrew, Channels, WhatsApp: who can chat, and the two spend limits you control.

    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 are the customer

    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.

    The My messages card in MyCrew showing a customer their own messages and whether each was answered
    MyCrew, as a customer: your own messages and what happened to each one.

    Asking for help

    What to send support

    • The reference code on the message that was not answered.
    • The time you sent it.
    • The agent name and which organisation you were signed in as.

    With the reference code, support can read the exact step where the message stopped, so you do not need to describe it.

    Troubleshooting

    Common questions

    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.

    Page version 1.0 · updated 12 Oct 2026 · screenshots from the 12 Oct 2026 release of Workbench and MyCrew. If a screen on your side looks different, tell us which one.

    Back to the node reference · Contact us