Policy Engine
The rules agents work to — company-wide, per customer, or per site.
- Company, customer, or site level
- Approvals where you want them
- Same answer every time
The same load, four sets of rules
Rules are rarely one size fits all. You set them at whatever level they belong to, and Emulon works out which ones apply to the load in front of it. Where two disagree, the more specific rule wins.
- Your companyNever book below a 10% marginWhere every load starts
- This customerNorthline is a 12% accountNarrower than the company rule, so it takes over
- This siteDallas DC needs an appointment and a lumper receiptAdds requirements the others say nothing about
- This laneNever pay over $2,600 Kansas City to DallasA ceiling for one lane only
A Northline load running Kansas City to their Dallas DC. Without anyone writing a rule for this particular load, the agent works to all four:
- A minimum margin of 12%, because the customer rule beats the company one
- An appointment booked before dispatch, because the site requires it
- A lumper receipt collected, or the load cannot be billed
- Nothing paid above $2,600, whatever the market does that day
Change the Northline rule to 14% and every future Northline load follows it — nothing else needs touching.
Your way of doing business, written down once
Every operation has rules: what you will pay, who you will use, what a site demands, what a customer must never be told. Here they live in one place, and agents follow them before they act.
Set them where they belong
A rule can cover your whole company, one customer, a single site, a lane, or one person. When two rules overlap, the more specific one wins.
Not just about price
Margin is only the start. Set which carriers may be used, what paperwork a site requires, when calls may go out, and what an agent may offer or promise.
A person for the close calls
Any rule can ask for approval rather than simply refuse. The request arrives with the numbers, and the work continues the second someone decides.
The same answer every time
These are fixed rules, not the AI using its judgement. The same situation always gets the same decision, and every decision is written down.
How a decision gets made
Anything that matters goes through the same four steps.
It gets checked first
Before an agent agrees to a price, books a carrier, or sends a message to a customer, what it intends to do is checked.
The rules that apply run
Your company defaults, plus anything specific to that customer, that site, that lane, or that person. Each gives one of three answers: fine, not allowed, or ask a person.
It goes the right way
Approved actions carry on. Ones that break a rule stop. Close calls go to whoever you nominated, with the numbers they need to decide in seconds.
It gets written down
What was proposed, which rules applied, and what was decided are all saved to the load.
Where a rule can apply
Start with how your company works, then add the exceptions where they actually belong. Nothing has to be rewritten for every load.
The defaults everything else starts from.
Where most exceptions live. The more specific rule wins.
Narrow rules, for the situations that have earned one.
Why it matters
This is what makes it safe to let agents act on their own.
Your standards hold on every load
The same rules apply at 2 AM on a Saturday as on a Tuesday morning, rather than depending on who happens to be covering the desk.
Local quirks stop being tribal knowledge
The site that will not take a drop trailer, and the customer who must be copied on every delay, are rules the system knows — not things a new hire learns the hard way.
Questions have answers
When a decision is challenged weeks later, you can show exactly what was known at the time and which rule decided it.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.