Reports that arrive, instead of a dashboard you forget to open

Every tool has a dashboard, and most small businesses open it twice in the first week and never again. The useful shape is the opposite: the thing tells you what happened. Premium sends a short daily summary and a weekly report by e-mail, and Standard gets a monthly performance report - all built from real recorded activity rather than from estimates.

The daily summary

A short message covering the conversations that mattered yesterday: what people asked about, the requests that came in, and - the part worth reading - the questions the assistant could not answer. That last list is the work queue. Each entry is usually one missing fact, and fixing it takes a minute and improves every future answer on that subject.

It is deliberately short. A daily e-mail that takes five minutes to read gets filtered within a fortnight.

The weekly report

A wider view over seven days: requests received and what happened to them, problems opened and closed, and the state of whatever automations you have switched on. Weekly is the right period for noticing a trend - a question that keeps coming back, a day of the week that is busier than you thought, an automation that has quietly been failing.

Your days, not the server's days

Both are built on your own time zone and your own business day, which sounds obvious and is the detail most reporting gets wrong. If your business is in Los Angeles, "yesterday" means your yesterday - not a window that starts in the middle of your afternoon. A report whose boundaries do not match the way you think about a day produces numbers you cannot reconcile with your own impression, and numbers you cannot reconcile get ignored.

Generated once, and recorded

Each report is produced once per period and stored, with its delivery state - sent, waiting, or failed with the reason. Two consequences that matter: a restart or a retry cannot send you the same report twice, and a report that failed to reach you is visible as a failure rather than as an absence. An absence is indistinguishable from a quiet week, which is how a business discovers in month three that it has not had a report since month one.

The monthly performance report, on every plan

Standard and Premium both get a monthly report for the service period: conversations, AI replies used, requests submitted, follow-up requests, the questions that went unanswered, and the knowledge-update time used. It is built from recorded activity, so the figures reconcile with what you can see in the panel. The first real one for Allinaa's own bot covered ten conversations, thirty-three AI replies and three requests - small numbers, and real ones, which is the point.

What the numbers mean, precisely

• AI replies are counted once per successful visitor-facing reply. Retries, failures, internal checks and templated e-mails are not counted, so your allowance is not consumed by the product's own plumbing.
• Requests are confirmed submissions with consent, not conversations that mentioned wanting something.
• Unanswered questions are the ones the assistant itself marked as unfinished, with the question attached.
• Starting a new conversation never resets a usage count, and a period never resets early.

See measuring the results for how to turn these into a decision.

Who should get them

The daily summary should go to whoever is going to act on the unanswered questions - one person, not a shared mailbox everybody ignores. The weekly and monthly reports are for whoever decides whether the thing is worth paying for. Those are often different people, and sending both to both is how neither reads either.

They are off until you ask

The daily summary and the weekly report are Premium automations and ship switched off for every business, like the rest of them. That is deliberate: an e-mail nobody asked for is spam, even when you are the one paying for it. Switch on the one you will read, and leave the other off until you want it. See what visitors asked for and Standard against Premium.