One console. Your team leader runs it.
No command line, no model configuration, no engineering skill. Six module groups, and the two that matter most are the ones where a human decides. Module names below are taken from the live console.
Command Center
The console opens on the live operation — in the product's own words, what's waiting, who's on the road, and what the AI needs a human for. Rides waiting and how many are assigned or on trip, drivers online and how many are carrying riders, completed rides, revenue, open tickets against SLA, and the count awaiting your call.
Two actions sit at the top of it: Check SLA and Dispatch the queue. Below the strip, a rides-and-revenue chart over the last fourteen days, and the queue itself, longest waiting first.
- Live Dispatch — the board as it moves, ride by ride
- Bookings — the full record, searchable
- Global search on the / key
| Card | Reads | Watch for |
|---|---|---|
| Rides waiting | Assigned vs on trip | Anything unassigned |
| Drivers online | Online vs carrying riders | Supply thinning in a zone |
| Open tickets | Count and past-SLA count | Past SLA above zero |
| Awaiting your call | Decisions queued, AI runs today | The number that decides your day |
| The queue | Longest waiting first | “Nothing is waiting” is the target |
Illustrative rendering. No client or rider data shown.
The line the console puts above everything else
“Nine AI decisions waiting for approval. Nothing they propose has happened yet.”
That banner sits across the top of the Command Center whenever the review queue is not empty, and it is the clearest statement of the whole architecture. The crew proposes. Until a named person in your desk opens that queue and approves, nothing has reached a rider, a driver or a bank account.
| Lands here from | Decision | Note |
|---|---|---|
| Support Center | Approve, edit or overrule a drafted reply | Nothing sent until released |
| Refunds | Approve or refuse an adjustment | Named approval above the ceiling |
| Fare Engine | Release a reconstructed fare | Evidence attached |
| Live Dispatch | Act on a flagged trip | Safety items call you out |
| Driver Settlements | Release a settlement query | Reconciled before it arrives |
Illustrative rendering. No client or rider data shown.
Human Review, and the lanes that feed it
Human Review carries a live count badge in the rail, so an ageing queue is visible from every screen rather than only when you go looking. Everything the draft-only crew produces arrives here with its context and the action it proposes.
Alongside it sit Support Center, Refunds and SLA Monitoring — the three places a supervisor spends most of an ordinary day.
- Approve, edit or overrule, with the reason logged
- Overrules feed back into the rules at the weekly pass
- Safety-classified items do not wait in this queue — they call your rota
Queue ageing is the single measure that decides whether this run works for you, which is why the count is in the rail and the past-SLA figure is on the Command Center.
AI Operations and AI Task Center
AI Operations is the crew itself: every agent with its status, autonomy class, volume, accuracy and last run, each with a pause and run control. The prepaid operating balance sits here with its burn rate and per-charge ledger, alongside the desk server's processor, memory and storage load.
AI Task Center is the work: everything running, queued and failed, with retry and the full decision log behind each one. When an agent refuses an action, this is where you see the refusal and the rule that caused it.
- Stop the crew and hand everything to your team, in one control
- Top up the prepaid balance without raising a ticket
- Every decision logged with its inputs, retained 24 months
| Agent | Class | Control |
|---|---|---|
| Dispatch | Supervised | Pause / run |
| Support drafting | Draft only | Pause / run |
| Fare reconstruction | Draft only | Pause / run |
| Onboarding & documents | Supervised | Pause / run |
| Incident triage | Escalate only | Cannot be promoted |
Illustrative rendering. No client or rider data shown.
Fleet, demand and riders.
Your supervisor will not open these every day, but the crew works inside them constantly, and month-end reconciliation happens here.
Drivers · Vehicles · Maintenance & Docs · Driver Settlements
The driver and vehicle register, document and inspection expiry, and the settlement ledger the crew reconciles payout queries against.
Zones · Surge Pricing · Fare Engine · Promotions
Where fares are reconstructed from and where surge and promotion questions are answered. The crew reads these; it does not change them.
Customers · Corporate Accounts
Rider history and corporate books, including billing codes and cost-centre allocation for operators running a business account base.
What the console does not do
It does not let you change the crew's autonomy classes, edit a decision log, or clear a safety-classified item in bulk. Those are not settings that were left out of the interface — they are refusals in the action handler, and the console has no screen for them because no screen could grant them.
Every board image on this site is a rendering built for illustration and carries no figures. Module names and the review-queue wording are taken from the live console; no client, partner, rider or driver data appears anywhere. The working console is shown only in a supervised ride-along.
The board is the decision.
Fifteen minutes on a working desk answers more than any page here. Ask to see the review queue with something in it.