Convarza AI
Troubleshooting

The AI bot is not answering

Almost always one of six things, and the first one accounts for most of them.

One cause dominates this list by a wide margin: the channel is not pointed at the bot. Check that first, every time, before anything else.

A channel routed to your agents accepts conversations perfectly happily and lets them sit unassigned — which, from the outside, looks like a bot that has stopped working.

Steps

Check the channel is pointed at the bot

A channel answers with exactly one thing. If it is set to your agents, chats arrive unassigned and nothing answers them.

The channel list states this on every row, so walking that list is the fastest possible version of this check.

Route incoming to, with the bot named. If this says something else, you have your answer.
Route incoming to, with the bot named. If this says something else, you have your answer.

Check whether the conversation is assigned

Assignment is the handover — the moment a human is assigned, the bot stops permanently for that thread. A conversation somebody picked up will not go back to the bot.

Check the channel is connected at all

If nothing is arriving, the problem is the channel rather than the bot. Send yourself a test message.

Check your AI message allowance

AI messages are metered: 1,200 a month on Starter up to 40,000 on Scaler. If the allowance is exhausted, the bot stops sending while your team is unaffected — which is a confusing pattern until you know to look.

AI messages against the allowance. If this bar is full, the bot has stopped.
AI messages against the allowance. If this bar is full, the bot has stopped.

For a call bot, check its call timings

A bot outside its permitted timings does not answer, and the call falls through to whatever is next in the flow.

Test the bot directly

Use the web widget's start-call test card, which exercises a bot without dialling or messaging anything. That isolates the bot from every channel question.

Check it worked

Once it is answering, send three messages that should each trigger a different handover condition. A bot that answers but never hands over is a different and worse problem.

Worth knowing

The parts people get wrong

  • Agents cannot see bot-handled conversations at all. An agent reporting "the bot is not working" is inferring it from silence — have a manager check with assignee set to None.
  • A bot in Draft answers nothing. Check its state as well as the channel's routing.

Rather be shown than read?

Thirty minutes, your numbers and your channels on the screen.

No setup fee. No per-conversation charge. Cancel from inside the product.