How to Automate CXT Software

Specimens are freight with a shelf life

A blood tube drawn at a clinic at ten past four has to reach the lab bench before its own chemistry drifts. That is the work CXT Software was built around: final-mile courier companies running scheduled medical and lab routes between draw sites, hospitals, pharmacies and diagnostic labs, alongside the retail and distribution deliveries that fill out the day.

The platform arrives in three pieces facing three different people. The Operations app is the dispatch board, where routes are built and drivers assigned. The Driver App carries shipment workflows, maps and job documentation out to the van. The Client Portal is white-labelled and handed to the hospital or the lab, who place orders on it, track them and look back through shipment history.

A courier running medical routes sells two things at once. One is the driving. The other is proof that the driving happened on time, at the right temperature, in the right hands.

The delivery ends and the evidence keeps arriving

The last route clears at six. The office work it created runs a good deal later.

Every hospital account wants the month in its own shape: on-time by stop, by site, by service level, against a window written into a contract nobody at dispatch has opened since signing. So somebody exports and reformats the same figures three times for three customers who each define lateness differently.

Then the exceptions, one at a time. A cooler comes back with a specimen still in it and nobody can say which stop it came from. A lab calls about a STAT draw that never showed. Each one means walking back through the board, the driver's timestamps and the lab's own receiving log, which sits behind the lab's login.

And the temperature. A cold chain box that sat forty minutes on a July loading dock is a genuine problem, but the logger's reading and the stop record are two stories that only line up when somebody sits down and lines them up.

CXT Software

Manifests that match the lab bench Last night's stops read back against the lab's own receiving record, so a specimen marked delivered but never accessioned surfaces as a name and a stop.

Cold chain gaps with the leg attached Temperature excursions tied to the driver, the stop and the dwell time they happened on, gathered for quality instead of reconstructed after a complaint.

On-time numbers your customer recognises Performance rebuilt against each account's own contracted window, so the figure you quote and the figure on their scorecard are the same figure.

Autonomous Dispatch and the Client Portal cover the delivery itself

CXT is not the weak link here. It covers the delivery thoroughly, and a courier still working from a whiteboard has a bigger problem to solve first.

Autonomous Dispatch assigns drivers from real-time data, with the choice of full automation, assisted dispatch or keeping it manual. Route Optimization and Route Management plan the day in advance and cut the miles driven. Advanced Tracking puts live GPS on a map, and parcel history is detailed enough for the strictest chain of custody requirements. The Client Portal fires automated shipment status alerts, so a hospital hears about its own order without ringing anyone. Accounting invoices from the same records, into QuickBooks or Sage.

All of that describes the parcel while CXT was holding it.

The lab's receiving log is not in CXT. Neither is the health system's supplier portal, where your on-time figure is published back at you by somebody else's arithmetic, nor the temperature logger's own cloud. Those screens decide whether the account renews, and every one of them belongs to a customer rather than to you.

A route that squares itself with the receiving bench

Every stop on last night's board has a counterpart somewhere else, and the counterpart is the half worth reading.

Last night's manifest read back against the lab's receiving record, so a specimen marked delivered but never accessioned appears as a name and a stop. Cold chain excursions matched to the leg they happened on, carrying the driver, the stop and the dwell time, ready to hand to quality. Proof of delivery packets assembled for the accounts that demand them, with the signature, the timestamp and the custody trail in one file.

The customer-facing side follows the same shape. On-time performance rebuilt against each contract's own window, so your number and the scorecard's number stop disagreeing. Missed pickup claims answered with the timestamps already gathered. STAT requests that came in through a hospital portal rather than the phone, lifted off that portal and raised while the window is still open.

This is medical courier work, so the boundary is firm. Reading, comparing and listing run unattended. Anything that alters a custody record, credits an account or reaches a clinic contact waits for the person responsible for it.

Reading a receiving log takes no medical training

It takes a login, patience and a free evening. That is why it mostly does not happen.

WebRun is an AI agent that drives a real Chrome browser, signed in the way your dispatchers and account managers are. It opens CXT Software, reads the routes and the parcel history, then opens the lab's system, the health system's portal or the logger's dashboard and compares what it finds there.

Runs happen on your schedule inside a private environment of your own, sessions are not shared between tools, and a workflow can be held to a named list of sites. You can watch a run and stop it part way.

The workflows below each say which screens they open and what comes back for review.