THE METHOD
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.
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.
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.
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.
The desk drafts the carrier booking from the finished job order — no swivel-chairing into a portal to re-enter what the JO already holds — and then holds it. Your coordinator reads it beside the job and approves; only then does it go to the carrier, on your own carrier account. The booking confirmation that comes back is read onto the job with everything it carries: the carrier’s reference, the vessel and voyage, the ETD, and the deadlines the carrier has set.
The confirmation lands on the customer’s own thread — booking number, next steps — not a cold message from a new address. The desk drafts it; your team approves it before it leaves the building, and it goes out in their name, from their own address. That’s the standing rule: every message a customer sees waits for a person.
HOW A START IS SCOPED
We scope the first workflow, integration requirements and implementation plan with your team. The stages are named, not timed — because what each one takes depends on your channels, your quote formats and whatever runs your operations today.
Where your yeses actually arrive, the quote formats behind them, and the job-file conventions your office already uses — numbering, field standards, who signs what.
Matching rules, the gap list the one ask is built from, your job numbering, and the bridge to whatever runs your operations today — or to none at all.
The desk shadows live traffic: it matches yeses to quotes and builds jobs in parallel while your team checks every call it makes against their own.
Live under approval on the first workflow — then more channels, more customers, and the desks either side of the yes when you want them.