foryn

Logistics insights / Perspective

AI agents · Delegated authority

The approval was valid on Monday. What about Wednesday?

A forwarder wouldn't ordinarily give every employee the right to discount any customer's freight or buy alternate capacity at any price. The software acting for that employee should not acquire those rights merely because it can reach the necessary screens.

Freight businesses already delegate judgment within limits. A pricing desk can issue standard quotes; a manager can authorize an exception. Operations may spend within a recovery budget. A customer may have agreed to automatic notifications but not to a change in service.

These permissions come with conditions: customer identity, trade lane, commercial policy, financial exposure, and time. A capable agent needs to work inside the same boundaries. Otherwise it can be perfectly competent at carrying out an action that nobody asked the business to take.

Illustrative scenario / Approval and execution

An approval can go stale.

A quote is reviewed, the underlying carrier terms change, and the agent sends the original offer. Every step has a valid record. The sequence still produces the wrong commitment.

Monday / Review

The quote is approved.

A manager confirms the rate and margin against the terms then in force.

Tuesday / Change

The rate is amended.

A surcharge changes effective immediately. The pricing basis has moved.

Wednesday / Action

The agent issues the offer.

It sees an approval but does not recheck whether the commercial conditions still hold.

Illustrative sequence; not a reported customer transaction.

The permission needs a shape

Authority is more specific than an approval status.

An approval is a record of a decision taken under a set of circumstances. It isn't necessarily permission to execute the same action indefinitely. If the carrier contract, customer eligibility, credit condition, or cost basis changes, part of that original judgment may no longer apply.

That does not mean every small update requires a manager. It means the business should know which changes matter. A standard quote within documented limits can move automatically; a proposed offer outside those limits must stop at the appropriate desk.

The stronger the delegation, the less routine work needs human intervention. Good authority controls should create room for automation, not a longer line of approval requests.

What the delegation should say

Who and for whom

The acting team or agent, customer, and business entity.

Which action

Draft, issue, book, amend, pay, or communicate.

Under what conditions

Evidence, commercial exposure, service limits, and customer instructions.

Until when

Validity period, changes that require review, and how to revoke permission.

Revocation matters too

An agent should know when to stop.

Imagine a customer placed on credit hold while an agent is partway through a booking, or a carrier withdrawing a rate the agent intended to use. The system may still be able to perform its next action. That doesn't mean the action is still authorized.

Sometimes the right response is to stop before the external commitment and return a prepared proposal to a person. Sometimes the agent can undo a reversible reservation and record the reason. The important point is that expired authority cannot be treated as a harmless missing field.

Enterprise autonomy will be useful when it handles the ordinary case without friction and makes the exceptional case legible to the right person. A list of enabled API permissions will never be a substitute for that business decision.

Foryn / Perspectives

A capable agent still needs an accountable mandate.