Loading...
Loading...
Automation
Your workflows, automated, streamlined and scalable.
Shipment Exception Handler
Draft • Last edited 2 min ago
Triggers
Logic
Actions
Email Trigger
Subject contains 'delay'
Priority Check
Is priority shipment?
Create Exception
In exception queue
Notify Customer
Send email update
Update TMS
Set status: delayed
Selected Node
Route based on shipment priority level
Condition
Field
shipment.priority
Operator
equals
Value
"high"
Valid configuration
Why rigid workflows fall over
Rigid workflows handle the easy part. The hard part is everywhere else.
An email lands. A driver checks in. The clock hits 6 PM. A rate con doesn't match. The workflow you built for that moment runs itself.
A tender from your customer, a check-in from a driver, a status update from a shipper — the right workflow picks it up and runs.
Friday afternoon billing audit. 6 AM check-call sweep. Monday morning load review. Same time, every time — no one has to remember.
If it's a new customer, route to the senior dispatcher. If detention is building, alert billing. If the rate's below threshold, ask before booking.
Inbox
Tenders, PODs, updates
Schedule
Hour, day, week
Event
Status, detention, billing
Trigger source
Delay on Load #4592 — new ETA Feb 15
"OOCL is reporting a delay on container MSKU7234821 due to weather routing — ETA pushed to..."
Atlas read this
What Atlas does
This is a delay on a hot load → fast-track to senior dispatcher.
Next steps
Loads in flight
12 active right now
#4592·Walmart Bentonville
I-40 W · Check call in 18 min
#4593·Costco Issaquah
I-5 N · Driver 30 min late
#4594·Target Minneapolis
I-94 W · POD requested
#4595·Amazon Newark
I-95 N · Alert sent to billing
#4596·Walmart Dallas
I-30 E · Pickup 8:45 AM
Today's activity
Rate con drafted for #4592
9:12 AM
Check call scheduled for #4593
9:42 AM
Detention alert sent on #4595
11:32 AM
POD requested from #4594
1:15 PM
47
Actions today
5
Caught early
Loads in flight. What's already handled. What needs a human. The board your dispatchers stare at all day — with everything happening in the background already accounted for.
Tender received at 9:12. Rate con drafted at 9:13. Dispatcher approved at 9:14. Check call scheduled for 11:00. Every step in one row.
Carrier's tracking is down? The workflow waits and tries again. Email bounced? It uses the backup contact. No one has to babysit it.
Months from now when billing asks why the rate con changed on a specific load — the timeline has the answer, the timestamp, and the dispatcher who approved it.
Live
Status on every load
Auto-retry
When carriers slip
Full history
On every action
Read events from your TMS, your accounting tool, your inbox, and your tracking provider — and write back to all of them. No middle layer, no rip-and-replace.
