Aggregates only. This console shows counts, cost, model split, funnel and
health across all merchants. Raw transcripts never leave the merchant's own instance and are
not available here by design.
Platform overview — last 7 days
Model split (cost)
Conversion funnel
Merchants
AWS region this merchant's instance launches into — fixed once provisioned. New regions are added here by hand once their infra is deployed (see infra/README.md).
Becomes <subdomain>.hollou.ai — the instance hostname, separate from the merchant's own business domain above.
No Shopify app install needed — reads the storefront's own public products.json. Leave unchecked for a services merchant. Pre-checked/unchecked automatically by the merchant type above — override either way if needed.
Embed snippet — copy this now, it will not be shown here again. The merchant is also emailed it once their instance is up (tls-ready):
"Connect with our AI Agent" button — paste anywhere on the site:
Console login
Set-password link
Telemetry problems: these boxes are silent, refused or not reporting their usage
⚠️Merchants near agreed volume (80%+): Call merchant before it's awkward
Merchant
Plan
Status
Instance
AWS
Last seen
Month Traffic (Billable / Quota)
Sessions 7d
Cost 7d
Provisioning queue
Company
Domain
Plan
Requested
Audit log
When
Actor
Action
System Validation (Smoke Test)
View detailed log
Sessions / day
Per-model consumption
Configured models
Live, as last reported by the instance's own heartbeat — not what was assumed at provisioning time. Distinct instances can run different models.
Infrastructure
AWS tier, polled directly from the EC2 API — no code runs on the merchant's own instance for this.
Console login
Email
Set-password link
Go-live
A merchant goes live only with a privacy policy link and a channel of their own (WhatsApp, phone, contact page or the lead form) — never the platform's own number. These settings are sent to the merchant's instance and overwrite what is set there by hand. Going live releases the welcome email with the embed snippet once the instance is up.
Merchant type
Takes effect on the merchant's widget after their instance's next restart. Does not trigger a product sync — a retail merchant with no catalog yet still needs one triggered separately via their own instance.
Embed script
"Connect with our AI Agent" button — paste anywhere on the site:
The original embed script cannot be shown again — the key is stored only as a hash.
Regenerating issues a new key; the merchant's instance picks it up on its next heartbeat
(about a minute), and from then the merchant's current script stops working —
they must replace it on their site right after. An instance without config sync never picks
it up: it shows up under Telemetry problems and needs the key set by hand.
New embed script — copy this now:
Operational endpoints
Ready-to-run commands against this merchant's own instance — for when a customer reports
stale products or missing website content. Endpoints marked auth
are operator routes: X-Admin-Token authorises them — the box's own
APP_SECRET_KEY, which this control plane does not hold and which
never goes into this page — and X-API-Key (the same key embedded in their
live widget script) only names the merchant. The key alone is the public embed key and the
box refuses it. Set ADMIN_TOKEN in your shell first with the
command below; paste the merchant key below to fill it into every command, or regenerate the
embed script above to get a fresh one already filled in. The key is only kept in this
browser tab — it is never sent anywhere but into the commands below.
No transcript view exists for this merchant here — message content is not stored in the
control plane. It is visible only in the merchant's own console.