BookingDesk AI

THE METHOD

Five moves between yes and booked.

The go-ahead arrives messy; the job order that leaves must be complete. The switchboard method closes that gap — wired end to end, with your approval on everything that leaves the building.

01 · YES

The go-ahead is caught in the wild.

The desk reads your channels the way your coordinators do — email threads, WhatsApp, the odd signed quote PDF or PO attachment. It recognises acceptance as it actually arrives: “ok pls proceed” as reply #14 on a two-week-old thread, “book it” at 18:40, a go-ahead that quotes nothing at all. And because the desk never goes home, the 02:14 yes is caught at 02:14 — not at nine the next morning.

email · whatsapp · signed pdf · “ok pls proceed” @ 02:14
02 · MATCH

Tied to the exact quote it accepts.

A yes is only useful once it’s tied to the quote it accepts. The desk matches sender, lane, references and thread history to the specific quotation — QT-16419, the Ajman express job — and shows its reasoning, not just its answer. If two open quotes could plausibly fit, it asks instead of guessing. The job starts from the right data, or it doesn’t start.

→ QT-16419 · sender + lane + ref · reasoning shown
03 · BUILD

The JO fills itself. Nobody types.

The job order builds from the quote’s own data — customer, parties, lane, cargo, buy and sell rates, terms. Zero fields re-keyed: the fifteen to thirty minutes of pure data entry a manual booking costs simply doesn’t happen. Accruals are set from the quote’s buy side, so the job is born financially honest. Anything missing — an HS code, a consignee tax ID — is gathered in one polite ask; the job holds at amber until answers land.

0 re-keys · accruals set · 1 ask · amber until answered
04 · BOOK

Pushed to the carrier, end to end.

The desk pushes the booking to the carrier itself — no swivel-chairing into a portal to re-enter what the JO already holds. The booking confirmation comes back with the booking number and its three clocks: SI, VGM and gate-in cut-offs, read straight onto the board. From there the desk works backwards — drafting the SI, chasing the VGM, nudging the trucker — and escalates with time to spare, not after the vessel closed.

BC returned · SI / VGM / CY clocks on the board
05 · CONFIRM

The customer hears back where they said yes.

The confirmation lands on the customer’s own thread — booking number, cut-offs, next steps — not a cold message from a new address. The desk drafts it; your team approves it before it leaves the building. That’s the standing rule: drafting earns more autonomy as trust builds, but the commitment moments stay human, and nothing external auto-fires on day one.

same thread · sent after your approval

THE FIRST 14 DAYS

DAY 1–3

We scope your channels and job-file conventions: email, WhatsApp, quote formats, how your job numbers and cut-off habits actually run.

DAY 4–10

The desk is configured and shadows live traffic — matching yeses to quotes and drafting JOs while your team checks every call it makes.

DAY 11–14

Live under approval: real go-aheads become real job orders and carrier bookings, with every outbound send signed off by your team.