The platform
From the first message to a signed delivery — one system.
LabCourier is four jobs in one platform: take the order, dispatch it, move it, and prove it. Here's how each piece works — and how they hand off to each other.
StatDesk · intake & dispatch review
The order takes itself.
Whatever channel an order arrives on, AI drafts a structured version from the raw message — validated against a strict schema before it moves. The raw payload is stored first, so the source is never lost.
- AI extraction validated against a strict schema — no invented details
- Raw message preserved and shown beside the draft
- One pipeline across SMS, MMS, app, web, and API
- Dispatch on your terms — your rules decide how each order routes
“Need a stat pickup from Riverside lab to Mercy, whole blood, keep it cold — asap please”
Stat Trace · tracking & proof of delivery
A tracking number from minute one — and proof at the end.
Every order gets a server-issued tracking number the moment it's created. You, your driver, and your provider watch the same live map and milestone timeline, and the delivery closes with a signature and photo.
- Live map and status milestones in real time
- Signature and photo proof of delivery
- A chain of custody from pickup to handoff
- Shareable tracking your providers can watch themselves
LabRoute · recurring routes
The routes that run every day, handled like routes.
Standing lab routes — the daily hospital loop, the recurring clinic pickups — are planned, assigned, and tracked alongside your on-demand STAT work, not bolted on as an afterthought.
- Recurring schedules with assigned drivers
- Tracked with the same milestones and proof as STAT orders
- On-demand and scheduled work in one operational view
Developer API · connect your providers
A secure API and webhooks for the systems your providers already run.
Carriers connect their providers programmatically: scoped API keys, read order status and proof of delivery, submit orders straight into the review queue, and receive signed webhooks on every milestone. Every external request is access-logged.
- Scoped, hashed API keys — one provider, one key
- Read orders and POD; submit intake to the review queue
- Signed (HMAC) webhooks on every status change
- Per-request access log — the trail a HIPAA review expects
{
"trackingNumber": "26LABC-481920",
"status": "IN_TRANSIT",
"priority": "STAT",
"milestones": [
{ "type": "PICKED_UP", "at": "13:24" },
{ "type": "IN_TRANSIT", "at": "13:25" }
],
"pod": null
}Everything included
One platform, not a stack of point tools.
Intake, dispatch, drivers, tracking, settlements, and the developer surface — built to work together from day one.
Omnichannel intake
SMS and MMS over Telnyx, plus the app, web, and API — every channel lands in the same structured pipeline.
AI with guardrails
Extraction is validated against a strict schema. The model never invents an address, name, time, or priority.
Driver apps
A phone app for the road and a desktop portal for the desk — assignments, status, and proof of delivery.
Settlements & pay
Driver pay with standby, deductions, and per-provider charges — the accounting a courier business needs.
Multi-provider by design
One carrier, many labs and hospitals — each provider isolated, with its own orders, users, and tracking.
Custom tracking numbers
Set your own tracking-number format and carrier code; numbers are issued server-side and stay unique.
Audit everything
Every dispatcher action writes an audit log; every status change writes a tracking event. Nothing is silent.
On-time & exceptions
On-time performance, exceptions, and open conversations — the operational picture, not vanity charts.
Security & compliance
Built for protected health information, not retrofitted for it.
STAT couriers carry specimens, results, and patient data. Compliance isn't a page on this site — it's wired into how every order is taken, stored, and moved.
BAA with every carrier
A Business Associate Agreement covers each carrier that touches PHI on the platform.
AI under a signed BAA
Order extraction runs on OpenAI under a signed BAA — never a consumer endpoint.
Encrypted end to end
Database encrypted at rest (TDE), TLS in transit, and Ed25519-verified webhooks.
No PHI in email
A send-path tripwire blocks patient data from leaving over email — enforced in code.
Every source preserved
Raw inbound payloads are stored before processing, and every event is idempotent.
Full audit trail
Every dispatch action, status change, and API read is logged and retained six years.
Get started
Put your STAT operation on rails.
A 20-minute walkthrough of intake, dispatch, and live tracking — mapped to how your couriers actually work.