Running it day to day

Ten minutes a week, honestly.

See what matters at a glance

Tenant → Analytics turns the raw data into decisions: messages per day, which capabilities visitors reach for, the exact knowledge-base searches they triggered (a frequent query with a weak answer is your next document to write), busy hours, and where conversations come from. Country-level location appears when the platform runs behind Cloudflare - IPs are never stored.

Let staff help

Accounts (owner only) creates staff logins: staff can read conversations and usage and maintain the knowledge base, but cannot touch tenants, embed keys, or settings. The day-to-day loop below is exactly what staff accounts are for.

Read what customers ask

Conversations shows every chat, newest first. This is the most valuable page in the product: it's a diary of what your customers want to know.

Open one to read the full exchange, including which lookups the assistant used:

Fix a wrong or missing answer

When you spot the assistant saying "I don't know" to something it should know - or being vague - the fix is always the same: open Knowledge base, add or sharpen the fact, save. The very next question uses the new answer. No restarts, no waiting.

Watch the numbers

Usage shows messages per day per business, so you can see quiet weeks, busy launches, and how close you run to your daily cap.

If you hit the cap on normal days, raise it in the settings; if you hit it because something hammered the chat, the cap did exactly its job.

Get pinged when it matters

With a Slack webhook configured, each new conversation lands in your Slack as it starts, with the visitor's first message - nice for hopping in personally during opening hours. You'll also get one alert if the daily cap is reached.

The habit that compounds

Once a week, skim the conversations and add one knowledge-base fact for anything the assistant fumbled. After a month of that, it answers like your best barista.