The booking desk for freight forwarders
The customer said yes.The desk does the rest.
Booking Desk AI catches the go-ahead in any thread, builds the job order from the accepted quote — zero re-keys — asks once for what’s missing, and drafts the carrier booking. It goes to the carrier the moment your coordinator approves it.
Zero re-keys · one ask · you approve every send · TMS or none
“ok pls proceed. same as discussed.”
— Cascadia Cargo · thread quotes nothing
⚙ why: same lane + party · quoted 3 days ago · “as discussed” = this thread’s only open quote
“To book right away we just need: HS code for the spares + consignee TRN. Everything else is on file.”
sent on the same thread · in Arjun’s name · booking no. + next steps
01 · THE YES-TO-JO GAP
You won the shipment. Then someone re-typed it.
Between the customer’s “yes” and a working job order sits fifteen to thirty minutes of pure data entry — lane, cargo, parties, rates — every field re-typed from a quote that already knew all of it. Multiply by every booking, every day, and the gap between yes and JO becomes a full-time job that produces nothing but transcription risk.
And because the job file is the operational spine — billing, documents, customs, tracking all hang off it — a JO born wrong stays expensive for its whole life.
of pure data entry to create one booking manually — re-typing data that already exists in the quote
Industry workflow descriptions, consistent with DCSA's characterization
interactions across ~30 organisations for a single container shipment
Maersk / IBM shipment study
of carrier bills of lading were digital in 2021 — the industry still runs on re-keyed documents
DCSA (Thomas Bagge, CEO)
possible reduction in documentation lead time with generative AI, including auto-generated shipping documents
McKinsey
FROM THE PRODUCT · TODAY’S BOARD
Seven yeses in. Seven jobs built. Zero fields re-keyed.
One arrived as a WhatsApp photo, one as reply #14 on a stale thread. Each is matched to the quote it accepts and built from that quote’s own data — and each booking waits for a person before it reaches a carrier.
- ⚙ 7 won quotes became jobs · fully filled in
- ⚙ 4 one-ask messages drafted from the gap list
- ⚙ 6 reminders and chasers ran on their own
- ⚙ 0 fields re-keyed · 0 jobs opened half-blank
PDF, Excel, Word, a forwarded email, a WhatsApp message, a photo, a scan. The yes arrives in whatever the customer had to hand, and the job is built from it — not from somebody reading it out to a keyboard.
JO-08219: the desk built the job from QT-16471, asked once for the consignee TRN, drafted the carrier booking — and held it. Priya approved 08:12, and only then did it go to the carrier, on Kestrel’s own account.
02 · THE METHOD
Five moves, wired together. Nobody types.
The go-ahead detected in email or WhatsApp — even when it's "ok pls proceed" on a stale thread.
Tied to the exact quote it accepts, with the reasoning shown. The job starts from the right data.
The JO fills itself from the quote: parties, lane, cargo, buy and sell. Zero re-keys, accruals set.
The booking is drafted from the finished job and held. Your coordinator reads it and signs — nothing reaches a carrier first.
Approved, it goes to the carrier on your own account, and the confirmation is read back onto the job.
The full method — acceptance detection, the one ask, the carrier push, and how a start gets scoped.
How the desk works →03 · THE NUMBERS
From “pls proceed” to a job already built.
MECHANISMS: THE FREIGHAI BOOKING AGENT AS PUBLISHED ON FREIGH.AI · THE INFINITY LOGISTICS FIGURES COME FROM A SIGNED CUSTOMER REFERENCE OF 15 MAY 2026 AND ARE PLATFORM-WIDE, QUOTING-SIDE RESULTS · RESULTS VARY BY DESK
04 · THE THREE CLOCKS
Every booking ships with three deadlines.
Miss any of them and the box risks rolling — a week of delay and a customer apology you didn’t need. And every one of the three is worked from the job file: the shipping instruction from its cargo data, the gate-in from its lane. A job order born complete is the cheapest cut-off insurance there is.
A ROLLED CONTAINER ADDS ~7–10 DAYS PER MISSED WEEKLY SAILING
Shipping instruction cut-off
B/L data submitted to the carrier — typically 24–72 hours before documentation deadline. Miss it and your box risks rolling.
Verified gross mass cut-off
SOLAS-mandated weight declaration, usually 1–3 days before ETD. No VGM, no loading — the terminal has no discretion.
Container yard / gate-in cut-off
The physical container into the terminal, typically 12–24 hours before ETD. The one deadline trucking delays love to threaten.
05 · FROM THE FLOOR
THE LOOP CONTINUES
The JO the desk builds is the one every other agent reads.
Booking Desk is one agent of the FreighAI platform. The job order it creates becomes the spine the tracking agent follows, the reconciliation agent matches invoices against, and the collections agent bills from. One record, born complete, trusted everywhere downstream.
READY WHEN YOUR NEXT YES ARRIVES
Forward us a real “pls proceed.”Watch it become a job.
Thirty minutes on a screen-share: your acceptance email, your quote, and a job order building itself in front of you — with the carrier booking drafted and waiting on your signature.