Straight answers, no hold music.

The job order — also called the job file or job — is the operational and financial container for one shipment: the internal record that carries the customer, lane, cargo, buy and sell rates, documents and milestones under a single job number. Every revenue and cost line ties back to it, which is why a JO born wrong stays expensive for its whole life. Booking Desk AI creates it from the accepted quote, so it's born complete.

Both. It builds the job order from the accepted quote, then drafts the carrier booking from that finished job and pushes it to the carrier once your coordinator approves — on your own carrier account. Your team approves what goes out; the point is that nobody re-types what the quote already knew.

It reads your channels the way your team does — email threads, WhatsApp — and recognises acceptance in the wild: "ok pls proceed", "book it", a signed quote PDF, a PO attachment. It then matches the go-ahead to the specific quote it accepts, so the job starts from the right data even when the customer's message quotes nothing.

The desk asks once — a single, polite message listing everything needed (dims, HS codes, consignee details), rather than a five-email drip. The job holds at amber until answers arrive, and nothing half-blank gets pushed downstream to documentation or customs.

The carrier's booking confirmation is read onto the job with everything else it carries — booking number, vessel and voyage, ETD, and the deadlines the carrier has set. Working those deadlines stays with your team. What the desk owns is the stretch in front of them: the job file they are all worked from, built complete from the quote the shipment was won on. What each cut-off is, and what a missed one costs, is explained in the guide.

Yes. The desk runs alongside CargoWise, Logi-Sys, Kale, Shipsy, Magaya — or Excel and Tally with no TMS at all. Jobs and bookings post into whatever runs your operations today; nothing gets ripped out.

Approval of what leaves the building. The desk builds the JO, prepares the booking and drafts the customer confirmation — your team approves the send. Drafting earns more autonomy as trust builds; the commitment moments stay yours.

We scope the first workflow, integration requirements and implementation plan with your team. The stages are Discover, Design and configure, Validate, and Implement and expand — named, not timed, because the shape of them depends on your channels, your quote formats and whatever runs your operations today.