The Agent Did Not Need Hands

Everyone is watching for robots. Meanwhile, agents are already moving technicians and trucks by changing the record that tells a person where to go.

That is the quieter route into the physical economy. A work order assigns a technician. A rate confirmation assigns a truck. A tracking milestone tells a shipper whether freight is moving. A proof-of-delivery document supports settlement. Software does not need to lift a tool or drive a vehicle when it can change the record that tells a person what to do next.

A small trades business shows the mechanism

The Grout Guy is an Australian property-services company with technicians working across the country. Its agent, Walter, sits at the beginning of the service chain.

Incoming work orders arrive as email text or PDF files. Walter reads the material, checks whether a job already exists for the property and stops if it finds one. Otherwise, it creates a Salesforce opportunity and links the source file.

Anthony Messina, chief technology officer of The Grout Guy, supplied operating details in on-record email correspondence with the show. He said Walter usually turns a work order into a Salesforce opportunity in about fifteen seconds, can take up to two minutes and handles a few dozen work orders each day. He put the share of created records requiring no later change at roughly 98 percent.

Those are company figures, not an independent audit. The 98 percent refers to Walter-created Salesforce records, not completed physical jobs.

Every Walter-created record enters a human review queue. Messina said the recurring problem is not extracting text from the work order. It is matching the correct billing contact, primary contact and account. The agent can read the request accurately and still connect it to the wrong people.

The company also tested a scheduling workflow through a voice agent and chose not to ship it. Messina said the technology worked but the experience was subpar. A functioning workflow was not automatically a deployable one.

Messina also narrowed the labor claim. He said conventional Salesforce automation accounted for most of the company’s move from roughly one dispatcher per four technicians to roughly one per 25. He credited AI only with the effort to move beyond that ratio. The agent entered a business that had already automated much of its coordination layer.

The truck moves after the record changes

Freight makes the physical consequence easier to see.

FreightWaves reported that C.H. Robinson uses coordinated agents to investigate missed pickups. One contacts carriers for information; another interprets the response and determines what should happen next. C.H. Robinson says unnecessary return trips fell 42 percent.

The physical claim is specific: when the coordination layer establishes that freight is unavailable or already collected, a truck can avoid returning unnecessarily. The evidence remains company-supplied. No named carrier or shipment in the reviewed reports supplies an independent end-to-end record.

Descartes describes a related workflow inside its MacroPoint network. Its September 30 logistics-AI preview says OpsForce agents restore interrupted tracking, confirm shipment milestones and collect missing proof-of-delivery documents. The company’s March 4 announcement says the system connected more than 435,000 additional drivers and produced 15 percent faster settlement through automated proof-of-delivery capture.

Those are Descartes portfolio claims, not a named driver’s independently documented outcome. The mechanism is still legible: recover the missing record, and settlement can move sooner.

The missing receipt

Neither the companies contacted nor the public reports reviewed supplied an independent transaction-level record connecting an agent’s action to a verified physical outcome and completed repair.

The Grout Guy described Walter’s workflow and known failure point, but said it could not share a redacted job record because the tenant, property and contact data were not the company’s to disclose. The freight companies and independent routes contacted for the episode did not supply a shipment-level chain before the reporting deadline.

That describes the evidence available for this episode. It does not establish that no such record exists.

A useful record would preserve the original document, the agent’s authority, what it changed, who reviewed the change, what a person or vehicle did because of it and how a mistake was repaired. A model can generate a plausible explanation after the fact. An operational receipt has to preserve the chain while it happens.

Physical agency without embodiment

The robot has become a distraction in the argument about AI and physical work. A body is one way for software to alter the world. Control over assignments, schedules, tracking and proof of delivery is another.

The near-term labor question is not only whether a machine can grout a shower or drive a truck. It is whether the system deciding who goes where can be inspected when it points at the wrong person, property or load.

Each win begins with a record. So does each failure. An agent does not need hands when it can hand instructions to people who do.

Listen to Episode 68

Episode 68, “The Agent Did Not Need Hands”, is available now.

Download the episode or subscribe to the feed.

Sources

Anthony Messina’s operating details came from on-record email correspondence with the show. The correspondence is attributed in prose, never linked or identified by a private or internal reference, and is not reproduced as a document.

If an agent has changed a work order, dispatch decision, route, service visit or payment in your workplace, tell the show what changed, what went right and what happened when the record was wrong. Email [email protected]. Use the subject line “The physical handoff.” Anonymous notes and source-protection requests are welcome.