It tells you when something is wrong

Who this is forAgencies, and anyone running this on a site they do not log into every day.

• One-click updates — new versions appear on your Plugins screen like any other plugin, from an update channel we host. Only the very first install is a manual upload.
• A health screen — API keys, embedding-model consistency, database tables, scheduled tasks, the streaming endpoint and whether the knowledge base has anything in it, all checked in one place.
• An error log you can actually read — recent failures with their area and message, in the admin, instead of an FTP hunt through a debug file.
• It emails you when the AI stops answering — an expired key or exhausted provider credits reach you within hours, debounced to at most one message every six hours.
• Settings export and import — move a configuration from staging to production, or reuse it on the next build. API keys are deliberately left out of the file.

You are not left guessing

A visitor never sees a provider error — they get a friendly retry — which means the owner needs a signal of their own. That is what the health screen, the error log and the alert email are: the same problem surfacing in three places you might be looking. A copy-for-support button collects your versions and configuration with no secrets in it, so a support email starts with the facts.

Set it up once, then get out of the way

The dashboard opens with a setup checklist — a key, an embedding provider, some knowledge, the widget switched on — that counts itself down and disappears once you are live. Each item links to the setting that satisfies it, and a connection test confirms a key works before a visitor finds out it does not.

Questions

Questions

How do updates work if it is not on WordPress.org?

The plugin checks its update channel and offers the new version on your Plugins screen, exactly like a plugin from the directory. Checks are cached for twelve hours, and any site can be pointed elsewhere or opted out entirely with one line in wp-config.php. The channel is no secret: it serves from ranakpik.com/updates/chatflint/, the domain of the developer who builds this, and moves to the product domain when that is live. A version check and a ZIP is all that passes over it.

What happens if my key is wrong or my knowledge base is empty?

The widget hides itself rather than showing a broken chat, and the health screen names the missing piece. A chatbot that can only apologise is worse than no chatbot at all.