foryn

Logistics insights / Perspective

Human-in-the-loop · Business authority

The quote is ready. Who can send it?

A junior pricing analyst can calculate a rate without being allowed to approve a margin exception. An operations coordinator can find a better routing without being authorized to spend money on it. Freight companies make these distinctions every day.

Replace the person preparing the work with an AI agent, and the conversation often skips straight to the last step: should a human click Approve?

It's a reasonable question, but not the first one. Before deciding where to put an approval button, the company has to decide which actions it is prepared to delegate. A correct calculation, a plausible recommendation, and a binding promise to a customer do not carry the same consequence.

Illustrative case / Ocean pricing

Three containers. One condition the quote missed.

A customer requests a price for three 40-foot containers from Busan to Long Beach. The agent finds a carrier rate, checks the equipment, calculates the costs, and produces a tidy offer. Nothing is wrong with the arithmetic.

But an amendment took effect the previous day. The rate now applies only to named accounts, and this customer is not on the list. The proposed price is correct against a rate the forwarder cannot use for this shipment.

If the reviewer sees only the finished total, an approval click adds very little protection. The decisive fact is buried in the agreement.

Where the human matters

The reviewer needs the facts that make the offer valid.

A pricing specialist may be the right person to authorize an exception, but only if the screen tells them what has changed: which agreement applies, whether the account is covered, what charges are included, and where the proposed margin sits against the company's limits.

That is different from asking someone to check a spreadsheet one more time. The work of finding, comparing, and explaining the evidence can be automated. The authority to deviate from a commercial rule still has to come from somewhere.

Sometimes the answer will be a person. Sometimes it will be a standing delegation that permits the software to act when the conditions are clear. Both are valid choices if the company made them deliberately.

Before the offer leaves the company

Applicable terms

The current agreement, amendment, and effective window.

Customer eligibility

Named-account conditions and other coverage restrictions.

Price basis

Included charges, exclusions, equipment, and margin.

Authority

The rule or person empowered to make this particular offer.

A more useful division of work

Reading, preparing, and committing should not share a single permission.

The difference is familiar to any commercial team. Software makes it easier to move between these steps, which makes it more important to keep the boundaries clear.

01 / Examine

Find the evidence.

Read an agreement. Compare an amendment. Locate a missing condition. These are the places where automation can remove hours of work without making a new promise.

02 / Prepare

Make a proposal.

Assemble a quote, suggest a booking, or draft a customer update. The result can be useful and ready for action while still remaining a proposal.

03 / Commit

Bind the business.

Issue the offer, buy alternate capacity, or change a delivery promise. These actions need authority. The business may grant it in advance within limits or give it in the moment.

Beyond the quote desk

A missed connection can create the same problem.

An agent spots a delayed shipment, checks alternative services, and drafts a message to the customer. Useful work. But there is a difference between reporting a delay, promising a new delivery time, and buying an expensive recovery move.

A forwarder might authorize routine delay notices automatically. It might also give operations a standing recovery budget for particular customers. Other decisions will depend on the value of the account, the cause of the failure, and the costs at stake.

This gets harder when the work crosses systems. One application may let the agent reserve space, another may authorize payment, and a third may send the customer an update. Each action is technically permitted. Together, they can create a commercial obligation that nobody actually considered as a whole.

The point of keeping a human involved

Give judgment a job worth doing.

Asking a specialist to approve every routine surcharge calculation is a good way to turn review into habit. Asking that specialist whether to make an exception for an important customer is a different use of their time.

The goal is not to place a person at the end of every automated process. It is to let software handle work it is equipped and permitted to do, and to make the consequential handoffs visible when judgment, discretion, or formal authority is required.

A human-in-the-loop design succeeds when the human knows what they are deciding and the software knows when it is not entitled to decide for them.

Foryn / Perspectives

More on evidence, judgment, and logistics decisions.