Already a customer or driver? This page is for couriers looking at StatVault. Your sign-in is right here.
When a clinic asks what happened to its specimen, have the answer.
StatVault brings dispatch, driver activity, pickup proof and delivery history together for medical couriers, with a driver app for Android and iPhone. Built inside a working dispatch office, with dispatcher and admin quality of life as the design rule. Keep CXT while your team adds the visibility and evidence it needs.
See what happened, spot what needs attention while the work is still happening, and give the clinic a clear answer.
Trying it opens a simulated courier you dispatch yourself: drivers on the road, orders coming in, a coach beside you. Nothing to install, no data to bring. A demo is a 30-minute screen share of the live system, walked through your own pickup-to-delivery workflow. No slides.
StatVault is a full platform, but you do not buy a platform. You buy an answer to one of these. Start there; the rest is there when you want it.
A clinic says the box was empty. A lab says a bag never arrived. Today the answer is a phone call and a guess.
What we show you
Where is the driver, did the STAT get picked up, who is covering the 4 PM run. Every answer costs a call, and chasing drivers who do not pick up is the real hassle of the job. The quality-of-life upgrades below are built for exactly that.
What we show you
Invoices go out on what was declared. Pay is argued over from memory. Nobody can point at the evidence.
What we show you
An anonymized afternoon STAT. The record panels are illustrative; the screenshots are production screens with identifying details replaced. Notice what the record says when proof is missing, not only when it is there.
The order arrives from CXT or the customer portal: clinic, window, driver. That is the declared truth. StatVault keeps it exactly as given.
Illustrative pickup recordOne tap on the box tag with the phone they already carry, Android or iPhone: that proves the phone was at that tag at that time. A photo shows what was in the bag. A thermometer in the cooler reports through the same phone, and each reading is judged against the profile that specimen needs; a crossing raises an alert. The app keeps all of it in an outbox until the server has it, so a dead spot does not lose the tap.
Illustrative pickup recordThe board shows picked up because the box was tapped, not because someone typed it. On the next stop the driver forgot the tap. The record does not pretend; it says so, and dispatch can act while the driver is still there. Watch that moment below.
Illustrative pickup recordThe lab calls about that afternoon. You open the order and press play. Arrival, tap, photo, delivery, signature, in order, each event chained to the one before it. The answer takes a minute, not a day of phone logs.
What the record will not do
It will not invent a tap that did not happen, and it will not let a later edit overwrite what the field reported. A missing tap stays missing, visibly. And it will not overclaim: a tap proves a phone was at a tag at a time; it does not by itself prove which specimens were in the bag. That is what the photo, the piece count and the signature are for, and the record keeps each one as its own fact.
StatVault reads the CXT feed without spending API credits and pushes every driver action back, so your order numbers, your customers and your invoicing stay where they are. Read works with CXT.
Starting without a TMS? StatVault takes orders directly through the customer portal and its own order entry, and runs billing and pay on its own engine. The steps are the same, minus the connection.
These are the screens a regional medical courier runs its day on. Captured live, with people, clinics and numbers swapped for stand-ins. More on the in production page.
Zippy is StatVault with a voice. It answers from the live record and can pull any lever a dispatcher can. Every action is confirmed first and written to the record with Zippy named as the actor. This is the step-3 gap, as it actually plays out.
Built inside a working dispatch office, with one rule: every click a dispatcher makes all day should cost less, and every question they ask a driver should come back with an answer. The three below are the clearest examples; the full list is on the dispatch page.
One tap on a driver's map radial or a board row.
What comes back: one of five forced choices on the driver's phone: On my way, I'm on site, Running late, There's a problem, or Dismiss. The server chases silence on its own and escalates, and every open nudge sits in an amber count until it is answered.
Tick the warning box on a message to one driver, a saved group, or the whole fleet.
What comes back: a card the driver must answer with Acknowledge or I can't comply with a reason, re-shown on every app open until they do. Broadcasts show Seen by N, and Zippy lists who has not answered.
"Sign the log book before opening the lockbox," written once on the site's access point.
What comes back: every driver who stops there sees it, it gates the pickup until they tap Got it, and the acknowledgement is recorded per driver, per location, per stop. When a hospital asks whether your drivers were told, you open the Acks tab instead of searching a group chat.
Up to three names with a score, reasons on hover, Re-score live. It runs on plain data, not a chat model, so it is instant and free, and it never assigns by itself unless an admin has explicitly turned on a rule that does; otherwise a person clicks the name. Overrides are graded on a Scorecard, so you can see where it was wrong.
Three complaints from public reviews of courier dispatch and driver apps, quoted as written, and what StatVault does about each.
“It won’t sync offline. When my driver loses signal they have to wait until signal returns.”
Courier owner, public review of a dispatch platform
StatVault: the tap is kept until the server has it.
Every tap, photo and signature goes into an outbox on the phone and drains when signal returns, in order, with the time it actually happened. A hospital basement does not lose proof.
“GPS drift near hospital docks makes ‘Arrived’ flaky.”
Medical courier driver, writing about four apps he ran routes with
StatVault: arrival is evidence, not a guess.
The geofence says the phone was near. The tap says it was at the box. The record shows both, separately, so a drifting dot never becomes a false “picked up,” and a real pickup never looks like a miss.
“Medical couriers are often the first to be blamed for a missing specimen.”
Courier company staff blog on lost specimens
StatVault: the custody record answers for you.
Who was at the box, when, with what in hand, and where it was handed off, hash-chained so nobody can tidy it up later. When the lab calls, you send the record instead of defending a memory.
Quotes are from public reviews on Capterra, Software Advice and the Google Play store, and from a medical courier driver's own write-up, collected October 2026. Product names are omitted on purpose; links on request.
We walk one of your own pickups through the board, the driver app and the customer portal, talk through how it sits beside CXT, and leave with what we need to quote you.
What determines the quote
How many drivers are on the road on a typical day, the mix of routes and STAT work, whether your clients order through a portal, and whether you connect CXT. Dispatch, the driver app, customer portals, NFC proof, the custody record, billing and pay, and Zippy are included. SmartBox hardware is quoted separately for a pilot. Full list on the pricing page.
Dispatchers and admins land in the map. Customer users land in the portal. Drivers use the app, and this form for the web.
