Traheel runs freight. The driving part is the part you see. The part you don't see is the back office. Every load that leaves the yard generates a paper trail: dispatch, bill of lading, proof-of-delivery, invoice, payment. Lose the trail and you don't get paid.
The hardest piece, by a wide margin, is the proof-of-delivery. The POD. A photo or signed document confirming the freight arrived. Without it, a customer can refuse to pay. With it, the invoice clears. The whole business hinges on a back-office team chasing drivers for a photo.
"Most of the work isn't moving freight. It's catching the paper after the freight moves."
The work, before the AB.
Three people on the back office. Every morning, the same loop. Open the dispatch board. Cross-reference yesterday's deliveries against received PODs. Make a list of missing ones. Open WhatsApp. Message each driver. Wait. Re-message at lunch. Call the ones who didn't respond by 4pm. File the photos when they arrive. Update the customer portal. Send the invoice.
before
chasing
on the loop
It wasn't a process problem. It was a follow-up problem. The team knew exactly what to do. They just couldn't do it for fifty loads in parallel without something falling through.
The AB takes the seat.
We onboarded one AB. We called it Ops. Ops had a memory of every load, every driver, every customer SLA, and the specific WhatsApp tone Traheel uses with its drivers. The onboarding took an afternoon.
Ops's job description, in one sentence: keep the POD board at zero by end of day.
Here is what Ops does without being asked:
- Reads the dispatch board every hour. Knows which loads should have delivered.
- Cross-references against the photos already filed.
- Messages each driver missing a POD in the right tone. Asks for the photo. Confirms when it arrives.
- If the driver doesn't respond in a configurable window, escalates to a human. With context. Not a notification dump.
- Files the photo to the customer portal. Tags the load. Triggers the invoice flow.
- Logs everything in the company brain so the next AB doesn't relearn it.
The three people on the back office did not get laid off. They moved up the stack. Two of them now spend their time on what Traheel calls "exceptions": the difficult conversations, the customer disputes, the new lanes. The third runs the company brain itself, deciding which other tasks to hand to the next AB.
What surprised us.
Two things.
First, the part we were most worried about, getting drivers to talk to a non-human in a workflow tool, turned out to be the part nobody noticed. Drivers didn't care that the messages came from an AB. They cared that someone was on the other side and the messages were consistent.
Second, the part we thought would be easy, plugging into the dispatch board, turned out to be where most of our engineering time went. Logistics software is a museum. We learned to treat the AB's tool integrations the way a new hire would: assume nothing, ask first, document the API by hand. For the legacy systems with no API to document, the AB falls back to computer use. Pointing, clicking, filling forms. State of the art integrations where they exist, state of the art clicking where they don't.
What's next.
Ops is one of five. Traheel now runs a team of ABs across functions: PODs, supplier invoice reconciliation, driver onboarding, expense reconciliation, and customer billing chase. Same brain. Same memory. Different roles.
That's the shape of the bet. One AB earns trust. Then more. The back office quietly becomes a team where most of the team doesn't sleep.
If you run an operation that lives or dies on follow-up. Get access. We'll find your first AB together.