Command Center
Command Center is a cross-client health rollup on /dashboard/agency, showing one row per client workspace in the agency group you own. It only renders once you own at least one Agency Group — with none, the page shows an empty state instead. Every row is read from a snapshot recomputed once a minute, never a live per-workspace query at the moment you load the page.
Every row here is agency-linked by construction — Command Center only ever lists workspaces already inside an agency group you own, and the snapshot behind each row is computed for exactly those workspaces. The distinction matters more on the Client Report page, which is reachable from any workspace, including ones outside an Agency Group.
Reading a row
Meridian Legal Group
Every row shows: a health score (this client's own Pipeline health scores, averaged), the workspace name, a risk reason if the row is flagged, one colored dot per non-zero Pipeline stage with its count, the total Estimated Value across that workspace's pipeline (labeled in that workspace's own configured currency — Agency Groups doesn't convert or sum currencies across clients), and a relative "Updated" time.
Grouping
Rows are split into three groups. Flagged rows (risk-flagged true) render individually, up front, in a fixed three-column 40/30/30 "needs attention" grid — the single worst flagged row (lowest real health score) always takes the wide 40% slot. Healthy rows (risk-flagged false) and gathering-data rows (risk-flagged null — see below) each collapse into their own "N clients healthy" / "N clients gathering data" toggle, two cards per row once opened.
38
Bright Path Legal
Bounce rate 6.2% over last 40 sends
52
Northwind Supply
1 inbox(es) blocked
67
Fenwick & Ames
Average health score dropped ~31% vs. 7 days ago, confirmed two days running
The wide card's border is thicker (4px vs. 3px) and its text sizes are larger throughout — a deliberate visual step up from the standard flagged-card treatment, not just "first in the grid."
Risk flagging
A workspace's risk flag is one of three values, evaluated in this order:
- True, immediately — if any "hard floor" signal is currently active: an active bounce-rate alert, an active suppression alert, one or more campaigns blocked at preflight, an at-risk or blocked inbox, or zero active campaigns.
- Null (not enough data yet) — if fewer than 10 non-disqualified pipeline records exist for this workspace. A brand-new client with barely any pipeline history reads as "gathering data," not silently green or red.
- Otherwise, a two-day persistence check — today's average health score must have dropped 25% or more compared to the value from 7 or more days ago, and that same drop condition must also have been true yesterday (against yesterday's own 7-days-earlier baseline), before the workspace is flagged. A one-day dip that recovers never flags anything.
Because that persistence check needs real daily history to compare against, a workspace can score well below 60 today and still read as null, not true — if there isn't yet a stored baseline from 7+ days ago, or yesterday's own comparison can't be confirmed either. The two-day-persistence rule is declining to flag on a single data point, not malfunctioning.
Expanded detail
Clicking a row expands it — collapsing whichever other row was previously open, since only one row can be expanded at a time.
Sending
Active campaigns
3
Inbox health
7/8
Sends today
212 188 capacity left
Replies awaiting action
6
Warmup cost (this mo.)
$14.20 142 emails
Blocked campaigns
0
The expanded panel adds sending status, active campaign count, inbox health, today's sends against remaining daily capacity, replies awaiting action, this month's warmup cost, and blocked-campaign count. If any campaigns are blocked at preflight, their actual names are listed underneath — not just the count — so you can act on it without switching into that client's workspace first. A Portal Access shortcut sits at the bottom of every expanded row.
Where to go next
Next: Client Report