Setup chats
Super Admin → Setup chats (/superAdmin/setupChats) is the record of every camera setup session on the platform: the step-by-step wizard and the newer conversation with the hub, side by side. It exists because setup is the part of an installation most likely to go wrong, and until now nothing could say how often it did.
How success is decided
Not by the session's own status. A session is marked expired the moment nobody touches it for a while, and most of those had in fact worked — the cameras were added and the installer simply closed the tab. So this page uses a harder test:
A setup worked if a camera stream appeared on that hub within 60 minutes of the session starting.
An install visit is one hub on one day, however many attempts it took. Three sessions on the same hub in the same afternoon are one visit, and it counts as successful if any camera landed. That is the number to watch — it is what an installer actually experiences.
The page
- The five cards summarise the window you picked: sessions, the share of install visits that ended with a camera, how many of those sessions were chats with the hub, what those chats cost, and how many messages the assistant steered back on topic.
- Week by week is the trend: visits, the share that ended with a camera, how many sessions each visit took, and how long from the first attempt to the first camera (median, and the slowest tenth). A rising success share with fewer sessions per visit is the whole point of the exercise.
- The session table is one row per session, newest first. Site, hub, who ran it, whether it was a chat or the wizard and from which app, the outcome, how many cameras came of it, and for a chat the number of messages, pictures and its cost.
Filter by window (7 / 30 / 90 days), by chats or wizards, by outcome, or tick Off-topic only to see just the sessions where someone wandered away from cameras. The search box matches hub serial, site name and person.
Reading a conversation
Click any row to open it. A chat is replayed in full: what the hub said, what the installer typed or tapped, the options they were offered, and a card for every command the hub ran — looking for cameras, signing in, testing a stream, reading a camera's settings — with how long it took and the pictures it brought back. Click a picture to see it full size.
Sessions run by the step-by-step wizard keep no conversation, so those open with a note saying so; their row still carries the outcome.
If the assistant steered someone back to the subject, the message they wrote appears at the end of the transcript with the time. Three of those in a day close that person's session until midnight.
Checking a camera is really being watched
Ask the assistant whether a camera is detecting and it asks the detection service itself, rather than judging by the last picture. It comes back in a second or two with, per camera, the decoder in use, the video format found, how many frames were pulled in the last minute and whether that counts as a dead spot. A stored picture only proves the hub could reach the camera at some point; this is the difference between a camera that is connected and one that is actually being watched.
It is worth asking after adding or changing a camera, and worth asking about a whole hub now and then — a camera can sit at a fraction of a frame a second, or waste bandwidth at twenty-four, without anything looking wrong on the tile.
Hubs on older software answer the question the slower way, from the last stored picture and its measurements.
What it costs
Only the chats cost anything: the assistant is a paid model call per turn (DeepSeek Flash, with Claude as the automatic backup when DeepSeek fails). The per-session cost is on every row and the window total is on the card, and the same spend also shows up under External spend against the control room that caused it. A typical setup conversation runs a few cents.
Who can chat, and who can read the chats
Two different answers.
Chatting with a hub is open to super admins everywhere, and to anyone who already manages a site's cameras once CleverCam has switched the Chat with the hub module on for a control room they belong to. The switch lives with the other modules under Company Admin → Company settings and, like them, only CleverCam can move it — each conversation spends a little of the control room's AI budget. One person drives a given chat: a colleague on the same site can read it but not type into it, because two people steering one hub would fight.
Reading them back here is super admins only, and the tab is only visible in super-admin mode. The conversations, the commands and the pictures are readable by nobody else — a control room can see that a setup session happened on its own site, but not the transcript.