A worked scenario: a WhatsApp approval, two export containers and a £600 charge that needs to reach the customer invoice. The booking dates and deadlines below belong to this example.
The billing owner has the revised booking confirmation, but not the customer’s approval to pay for the change.
That approval sits in WhatsApp. The supplier’s charge is in an email. The shipment file shows the revised collection plan. Each person has finished their part, but the draft customer invoice still carries the original price.
The handover from operations to billing is where the approved recovery can disappear.
In The Loadstar, Zauber founder Erik Muttersbach argues that forwarders should look beyond faster administration to lost gross profit. An agreed supplier charge left unbilled is a concrete place to apply that thinking.
A readiness update changed the plan
At 11:20 on Tuesday 20 October, a Midlands supplier sent a WhatsApp update: cargo booked for loading on Wednesday 21 October would not be ready until Friday 23 October at 08:00. Two 40-foot high-cube containers were booked on carrier haulage to Southampton. Neither empty had been released.
The booking recorded Friday’s terminal gate-in deadline as 18:00 and the verified gross mass deadline as 16:00. Shipping instructions were due Thursday 22 October at 12:00. Friday loading might still work, but the carrier had to confirm the transport plan and space before anyone promised the sailing.
In this workflow, an authorised WhatsApp conversation connects to the shipment record. The agent matched the booking reference and container requirement, then checked the message against the current booking confirmation. It recorded Friday 23 October at 08:00 against the original Wednesday appointment, without asking the operator to re-enter the date.
At 11:25 the agent requested a quote for revised haulage. It left the Wednesday movement intact. The supplier’s written offer was £300 per container, £600 total, held until 13:00.
The carrier confirmed that Friday loading could meet the recorded deadlines and retained space on the booked sailing, with no further quoted charge for this option. The case also recorded shipping instructions as submitted and accepted ahead of Thursday’s deadline. Until those checks were complete, the sailing and total cost remained unresolved.
It prepared those details for the customer. At 12:10 the customer agreed to reimburse the £600 supplier charge. Approval identified the booking, revised haulage plan and customer charge. A reply to an earlier quote could not authorise a later price.
Approval followed the charge into billing
At 12:15, with that approval recorded, the agent submitted the amendment. Its account could request the agreed change; it could not accept a different sailing or additional cost on its own.
The submission timed out. Before sending anything again, the workflow checked the existing request reference. The status check confirmed receipt at 12:15, before the offer expired at 13:00. The agent monitored that request instead of creating another amendment.
The returned confirmation matched the approved sailing and two 40-foot high-cube containers. The carrier-haulage provider confirmed the revised loading appointment, and the customer update carried those confirmed details. Operations could mark the amendment complete.
Billing recovery remained open under a linked task. The agent retained the supplier charge, customer approval and recoverable customer amount together. When the invoice draft arrived, it could find no matching charge line.
It sent the billing owner the omission and the supporting records. The owner corrected the draft. The workflow checked the issued invoice before closing the recovery task. The £600 supplier cost now had its corresponding £600 customer charge. The operator did not have to reconstruct the approval from WhatsApp.
Give the agent authority to finish its part
The customer approved the commercial option and billing corrected the invoice. The agent handled the permitted follow-through, including recovery checks after operations had closed the amendment.
Tools restricted record access and permitted actions. A changed charge required fresh approval.
Before releasing this workflow, we would test stale approvals and confirmations containing the correct booking number but the wrong equipment. Either must block completion. Duplicate messages must update the same case without repeating the amendment. A submission timeout needs a status check before another request is sent. Model changes must pass those evaluations and review gates again.
Give each run a token allowance, tool-call limit and deadline. Run exact comparisons in code. Retrieve case evidence rather than replaying the chat archive; reaching a limit should mean handing over the records and outstanding decision.
Measure model and tool costs alongside the human work still required. A cheaper response offers little if someone still has to search WhatsApp at month-end. We expect current agents to carry out routine work within tested permissions without an approval at every step; correct completion and the intervention rate are what a pilot must establish.
This ocean freight workflow crosses operations and billing. For a team with the same gap, trace one amendment from customer approval to invoice. Which record tells billing what to recover? Let’s talk about making that handover hold together.
Questions from freight teams
Can an AI agent act on a WhatsApp message?
With an authorised account connection and the required freight-system access, a message can start a shipment workflow. The agent still needs to establish which booking it concerns and which actions the sender can authorise.
Can a booking amendment be complete while billing work remains open?
Yes. The returned confirmation and downstream instructions can satisfy the operational checks while a separately owned recovery task remains open. Closing one must not hide the other.
What stops an agent spending beyond its authority?
Execution tools should enforce the approved option, amount and permitted actions. A changed price requires a new decision; the agent cannot expand that approval itself.
What should an evaluation include?
Test the handovers and failures: ambiguous dates, old approvals, conflicting confirmations, duplicate triggers, timeouts after submission and an invoice missing the approved charge. Check correct escalation as well as successful completion.