Skip to content
Supa Brain

A common chatbot mistake

Your chatbot broke last week and nobody noticed

An expired key, a changed model, a moved page. The bot shows an error to every visitor, and it can go on for days.

Bots depend on things that change without warning: the AI provider, the plan, an API key, the pages they read. When one of them breaks, the widget often keeps loading and shows the error to customers.

Nobody on the team chats with their own bot every day. The first to notice is a customer, and most customers don’t tell you.

What time do you open on Sunday?

Something went wrong. Please try again later.

Your page says

Sunday 10:00–16:00

Contact page

Broken after an updateA mistake we found in a live bot, retold with a made-up business.

Why it happens

It isn’t random

01

Silent dependencies

An API key expires, credits run out, a model is retired. The widget still loads.

02

Website changes

A redesign moves pages. The bot keeps citing old links or loses the content it answered from.

What it costs you

  • Every visitor who opens the chat during the outage sees the error.
  • It reads as a business that doesn’t look after its own shop window.

How we check

  1. 01Assistant Care asks your bot a fixed set of questions every week and checks every day that it loads and answers, so a broken bot is caught by us, not by a customer.
  2. 02After every check you see what changed since the last one.

What the fix looks like

  • Monitoring, plus a fallback message that sends people to your contact page when the bot can’t reach its provider.

Where we see it

Other mistakes we find

See your assistant answer your customers first

Email us your store’s address. Within a working day you get five questions your customers ask and the answers your assistant would give, each with the page it comes from. Free, no call needed.