How to Automate ProMiles

ProMiles decides where a heavy load is allowed to go

ProMiles is trucking software for routing, fuel tax and compliance, sold as ProMilesOnline and a set of products around it. The part of the business it owns is where guessing is expensive.

An ordinary truck takes the road the map suggests. A load sixteen feet wide, or too tall for a standard bridge clearance, or grossing well past the eighty thousand pounds a normal rig is allowed, cannot. It needs a route with clearances, restrictions and weight postings checked, and a permit from every state it crosses.

Get that wrong and the results are not paperwork problems. They are a truck held at a scale, a struck bridge, a fine, or a load on the shoulder waiting for a corrected permit.

So for a heavy haul carrier or a permit service this is not back-office software. It says whether Tuesday's job can legally happen at all.

Dispatch spends the day confirming a single load

The routing and the permit are an afternoon. The load is a week.

Somebody rings the escort company to ask whether two cars are free on Thursday, then rings again on Wednesday because nobody confirmed. Somebody checks the shipper's portal to find out whether the load is ready, since the last three were not. Somebody watches a state's travel restriction notices, because a holiday weekend turns a valid permit into a truck parked at a rest area.

Then it delivers and the second half starts. Detention hours have to be pulled off the customer's system and argued about. The accessorials agreed on the phone have to appear on the invoice. The invoice goes into whatever portal that broker uses and is then chased.

None of that is driving. All of it happens on a screen, usually while the person doing it is covering the phone.

ProMiles

Releases confirmed before the driver rolls Every open load checked on the broker's or shipper's own portal, so a dock that is not loading is known the night before.

Detention that does not quietly vanish Hours and accessorials read off the customer's system and set against what was invoiced, while somebody still remembers the move.

Certificates caught before they lapse Insurance certificates and driver credentials watched for expiry across every customer that insists on seeing one.

ProMiles knows every bridge between the yard and the delivery

ProMiles automates the hard technical parts properly, and a carrier should use them fully first.

PermitManager handles multi-state oversize and overweight permitting from a single point of data entry, submitting applications to several jurisdictions at once, with self-issuance around the clock rather than at a counter during office hours. Inside it, RouteManager is an interactive national map carrying vertical clearances, permanent and temporary restrictions and bridge and road weight postings. FuelTaxOnline and Automated Fuel Tax Reporting build the IFTA return from routing data rather than from a shoebox of receipts.

That is a serious stack, covering the two things most likely to cost a carrier money: an illegal route and a bad fuel tax filing.

What it covers is the truck and the road. The load belongs to a customer, and the customer's version of it lives on the customer's own system: the broker portal that says whether the load is released, the shipper's dock schedule, the escort company's inbox, the payables system where the invoice goes and detention gets disputed, the certificate of insurance a compliance team wants before the gate opens. None of that is road data, and none of it is reachable from a routing engine.

The same load exists in four systems that never speak

The customer's screens open to logins the office already holds, and that is where the other three versions of the load are kept.

Each open load checked on the broker's or shipper's own portal every morning, so a release that slipped a day is known before a driver deadheads to a dock that is not loading. Escort confirmations chased until the answer is yes or no in writing, which is the difference between a Thursday move and a Thursday of phone calls.

After the wheels stop, the paperwork can chase itself. Detention and accessorial charges read off the customer's system and set against what was invoiced, so hours agreed on the phone and quietly dropped get raised while somebody remembers the load. Invoices followed into each broker's payables portal until they show approved rather than received. Certificates of insurance watched for expiry across every customer that needs one, and driver credentials the same way.

Keep the line at the truck. Reading portals, comparing numbers and building the morning list can run unattended. Nothing dispatches a driver, accepts a load or applies for a permit on its own, because each commits money and puts a person on a road.

Watching a load takes no judgement at all

Three screens have to be open at once for one load: the broker's portal, the escort company's inbox and the customer's payables system. None needs a dispatcher's experience. They just have to be looked at.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the broker portal, the shipper's system, a customer's payables site or an insurer's certificate page, reads what each shows, and hands back a short list: what is released, what slipped, what was short-paid, what expires.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything that commits the company, a dispatch, an acceptance, a permit application, waits for a person.

The workflows below are already built, and each one names what it opens.