Request a Recon →
The Command Dashboard

One board. Every unit reporting.

Automation without a place to watch it is a black box you are asked to trust. The command dashboard is the opposite: one screen that shows what every agent did, what it cleared without you, and the short list of things that need a person. It is not an add-on and it is not a reporting layer bolted on at the end. It is the foundation, and it is built first.

Try the board → Request a Recon
01 / Definition

What it actually is.

Three things it is not, first, because the category is crowded with tools that look similar from a distance.

Not a BI dashboard

A BI tool visualises data you already had. This runs the work. The numbers on it are a side effect of agents doing jobs, not the point of the screen.

Not a report you read on Monday

It is current because the agents feeding it are working now. There is no refresh cycle to wait for and no analyst assembling it.

Not another system to keep updated

Nobody types into it to keep it honest. It reads from the tools your operation already runs on, which is why it does not go stale the way a spreadsheet does.

It is a command post

The work happens underneath. The board tells you what happened, what is blocked, and what needs your decision, in the order that matters.

02 / The point

Why it exists.

Three problems, one screen. Each of these is a reason a business stops trusting its own automation.

01

You cannot supervise what you cannot see

An agent working invisibly is indistinguishable from an agent not working. The board makes every action attributable, so delegation is a decision rather than a leap of faith.

02

Judgement should be scarce, not constant

Most of the work does not need you. The board's job is to clear that away and put the few things that genuinely need a human in front of you, with the context to decide fast.

03

The business should not live in one person's head

When the schedule, the pricing and the exceptions are on a board instead of in somebody's memory, the operation can grow past that person, and survive them leaving.

03 / The loop

How a CIS uses it.

The dashboard is one leg of a loop that runs continuously. The model drives, the system executes, you command.

  1. 01

    Connectors read

    A CIS reads from the tools you already run, on a schedule and on events. Nothing is re-keyed and nothing depends on someone remembering to update it.

  2. 02

    Agents act

    Role-specific agents each own one job. They draft, generate, route, chase and reconcile, and every action they take is written down against their name.

  3. 03

    The board reports

    Everything lands on one screen: what ran, what cleared, what is blocked, and what is waiting. Sorted by what needs you, not by what happened last.

  4. 04

    You command

    You approve, hold or redirect. The decision goes back into the system, the agent proceeds, and the next loop starts already knowing what you chose.

04 / The dashboard

This is how your board could look.

A command view built for your operation. Click an agent to see what it owns, switch a unit on, or add a panel. Nothing here is real data.

Command

your operation
As of --:--:-- Illustrative
Panels
Cleared 42 no human touch +12
Open 18 in progress -4
Needs you 3 waiting on a decision +3
Automated 94 % of steps, no human +8

Role agents

1 needs command

Activity

streaming
06:41 INTAKE New records captured and routed to the right owner.
06:38 DOCUMENTS Documents generated from one source record.
06:35 COLLECTIONS Overdue accounts surfaced with follow-up drafted.

Illustrative only. Every figure here is invented to show the shape of the board. Convoy has no shipped builds yet and does not present demo numbers as client results.

05 / The panels

What is on the board.

Role agents

Every agent, what it owns, and its current state: running, cleared, or needing command. Click one to see exactly what it is responsible for.

Today

The handful of numbers that decide today's decisions, current rather than assembled. Which numbers those are is set during the recon, per operation.

Activity

A continuous record of what the system did, timestamped and attributed. This is the audit trail and the supervision surface at the same time.

Command queue

The short list that needs a human. Approve, hold or redirect, and the decision is logged against the item and the person who made it.

Units

Add-on agents you can switch on later. They install onto this board and start reporting into it immediately, without a rebuild.

Access

Role-based, so a technician, a bookkeeper and an owner each see the board that fits their job. Named accounts, never a shared login.

06 / Included

It is part of the build, not an upsell.

Every CIS includes the foundation and the command dashboard. It is the first milestone of the build, before any workflow is automated, because the workflows report into it and there is no sensible order that puts it last.

It is deployed into your environment, under accounts you control, and it is yours when the build is done. Adding a workflow later does not mean a new dashboard; the new agent reports into the board you already have.

The recon is what decides its shape: which agents you need, which numbers belong on it, and who should see what. That is a conversation about your operation, not a template.

Request a Recon → See the add-on units
Deploy

Start with a recon.

The recon decides the shape of your board: which agents you need, which numbers belong on it, and who should see what.

Rather just email us? Click here

Book a call

Thirty minutes on your operation. No cost, no obligation.

Book the recon call → Or send the brief first →