STATvault Request a demoDemo

The Suite on One Page

The Suite on One Page: how it works in StatVault.

What this page is for

StatVault is a lot of screens. This page is the map: every surface in the help corpus, grouped by who uses it, and the path an order takes through them. Use it when you know what you want to do but not which page does it, or when you are new and want the shape of the whole thing before the details.
Every StatVault surface grouped by role: Customer Portal, Dispatch (with Zippy and the Driver App), Admin and money, with the six-step order lifecycle across the top
Card colour is the minimum role that can open the page: blue for customers, green for any team member, amber for dispatchers, red for admins. Roles and Access explains the roles themselves.

The life of an order

Everything in the suite exists to move an order through six steps. Each step has a home page, and most problems are "which step is this stuck at?"
The six steps an order moves through: order in, dispatch, on the road, custody, verify, settle
  1. Order in. Customers place orders in the Portal. Dispatchers use New Order from the rail or the Map. Orders that start in CXT arrive on their own through the ESV feed and show up on the board within about a minute. Orders and Routes covers what an order is, and how routes and stops differ from it.
  2. Dispatch. The Dispatch Board and the Dispatcher Map are the two places to assign a driver. They are the same orders widget in two settings. The Dispatch Scorer ranks candidates when you ask for suggestions, and Zippy can brief or assign for you. Stop Triage handles route stops that need a decision.
  3. On the road. The Driver App is where the driver accepts, navigates, scans NFC boxes, takes photos and delivers. Its GPS feeds the Map and the Command Center; its messages come through Chat, explained in How Messages Reach Drivers. Dispatchers can see the app's exact screens in the Driver App Emulator.
  4. Custody. Every pickup, scan, hand-off and delivery is recorded as an audited event. Custody explains what counts as evidence. Order Detail shows the trail for one order, Chronoshift replays a whole day, and Incidents is where gaps and exceptions are worked.
  5. Verify. Billing Verification checks price and driver pay against Billing Policies; Billing and Verification explains the rules. Pay Equity watches pay across the fleet over time.
  6. Settle. Confirmed values push back to CXT. Customers see the result as invoices and reports in the Portal.

The four groups of pages

Customer Portal. A separate login for your clients. They can place orders, track them live, pull reports and invoices, and keep an address book. Start at Portal: Getting Started. Nothing a customer does reaches the dispatch pages except as an order.
Dispatch. The live floor. Every page here shares the same left rail, and Search, Notes and Chat work from all of them. The pages split into watching and assigning (Map, Board, Command Center, Manifest, Routes) and the records behind them (Orders, Drivers, Coverage, Site Intelligence, SmartBox Dashboard). New dispatchers should read Getting Started (Dispatch) first.
Zippy. The AI dispatcher is not a separate product; it reads the same orders, drivers and custody events as the pages above. Ask Zippy is the chat, What Zippy Can Do lists every tool, Zippy's Dispatch Room is the dispatcher-only working session, and Zippy in Slack brings alerts and approvals to Slack.
Admin and money. Setup and the numbers: Users and Roles, Locations, Waypoints and Site Intelligence, SmartBox Devices and Sensors, the Smart Rules Playbook, and the billing pages listed under Verify above.

Ideas that run through everything

A handful of concepts show up on almost every page, and each has its own short explainer: Orders and Routes, Custody, SmartBox versus NFC Box, Service Day and Time, Roles and Access, How Messages Reach Drivers, Billing and Verification and The Dispatch Scorer. The Glossary defines the words.

Things that confuse people

Related