Freight exception management
Automation is only trustworthy when you can see exactly where it needs you. Fretie's exception management gives your operations team one queue for everything that needs a human — instead of problems hiding in log files, bounced emails, or a teammate's memory.
Every exception says what went wrong, why it matters, and links straight to the quote, mailbox, shipment, or rate involved. Work it, snooze it, or resolve it with a note — and Fretie auto-resolves the ones that fix themselves.
Everything that needs a human, in one place
Quote requests with no matching rate, quotes held below the margin floor, mailbox connectors that stopped syncing, bookings that failed to reach CargoWise or Magaya, carrier invoices that came in over the quoted cost, and rate cards about to expire — each lands in the queue with severity, context, and a deep link to fix it.
Deduplicated and self-healing
The same condition firing twice updates one exception instead of stacking duplicates. And when a condition clears on its own — the mailbox reconnects, a rate is renewed, credits are topped up — the exception resolves itself with a note saying why. The queue only ever shows real, current work.
Snooze, assign, resolve — with an audit trail
Exceptions can be assigned to a teammate, snoozed to a date, or resolved with a resolution note, so the queue doubles as a record of how your desk handles problems. Critical exceptions surface in real time over the same live feed as agent runs.
What you get
- ✓One queue for no-rate requests, margin holds, sync failures, TMS push errors, cost overruns, and expiring rates
- ✓Severity levels with counts: critical, warning, info
- ✓Deep links to the affected quote, mailbox, shipment, or rate
- ✓Assign to a teammate, snooze to a date, resolve with a note
- ✓Deduplicated — one exception per condition, never a flood
- ✓Auto-resolves when the underlying condition clears
Frequently asked questions
+What counts as an exception in Fretie?
Anything the automation cannot safely finish on its own: a quote request with no matching rate card, a quote held below your margin floor, a mailbox that stopped syncing, a booking that failed to push to your TMS, a carrier invoice above the quoted buy cost, or a rate card expiring within a week.
+Will I get flooded with duplicate alerts?
No. Exceptions are deduplicated per condition — the same problem firing repeatedly updates one entry rather than creating new ones — and many resolve themselves automatically when the condition clears.
+How is this different from email alerts?
Alerts get read once and lost. An exception queue is stateful: each item stays open until someone resolves it (or it auto-resolves), can be assigned and snoozed, and keeps a resolution note — so nothing slips and you can see how issues were handled.