By the Onsites AI team · Last updated · 5-minute read
Freight forwarding is a support desk wearing a logistics costume. The day of a forwarder's customer team is a queue in everything but name: RFQs arriving by email and WhatsApp, quotes to chase (rates expire in days), requotes when the 20ft becomes a 40ft, ETAs to relay, delays to apologize for, demurrage questions to answer, and PODs and invoices to chase at the end. And the tools — Outlook, a quoting spreadsheet, WhatsApp threads, a TMS somewhere — fragment the work so that quote chasing becomes a job description in itself. This guide designs the desk around the way freight actually flows: one thread per shipment from inquiry to invoice, quotes written from a rate card without retyping, requotes done in one message, and every exception joined to the thread it belongs to. Onsites is the tool the design assumes — three seats free, $15 beyond, AI at published credits — but the design is the deliverable; any desk can be judged against it.
Walk one week through the operations inbox and the patterns name themselves. The RFQ pile: inquiries arrive from the website, from email chains (CC'd buyers, attached spreadsheets), from WeChat and WhatsApp — each a potential shipment; without a queue, they are a triage problem answered by memory. The quote chase: quote #1042 sent Tuesday; Thursday the rate expired; the buyer replies on WhatsApp; version three of the sheet goes out — every version a chance to quote the wrong 20ft. The exception run: EISU-4821 rolls a week; thirty customers ask; the update goes to whoever asked from whichever window was open. The document tail: PODs, invoices, and "we never received" emails — each a copy-paste from a system that does not know the thread. Freight support is not harder than other support; it is more fragmented, which is why the desk design matters more here than anywhere.
Fundamental redesign principle: the customer's inquiry, the quote, the confirmation, every ETA, every delay, the delivery documents and the invoice all live in a single thread the whole team can see. Why: freight work is conversation-shaped (questions, updates, chasing), and every handoff between tools loses a fact that the exception month eventually bills for. How: the inquiry lands as a conversation (email, WhatsApp, WeChat, widget — all native channels); the quote is written from the catalog inside the same thread; the buyer accepts; the quote becomes an order and the order an invoice — numbered, tracked, paid, in place. The test: a year later, "what did we promise on the Rotterdam job?" is answered by scrolling that thread — answers, rates, deadlines, promises, all in sequence. Desks that fragment this into five tools do not just retyping costs; they lose institutional memory at every vacation.
The 20ft-to-40ft requote is freight's signature failure. In the tool stack, it means: find which sheet was sent, recompute the line, regenerate the PDF, email it as version four, and hope the buyer compares the right versions. In the thread, it is one message: the quote sits in the conversation, the line edits in place from the shared rate card, and the buyer sees version four beside versions one through three with both prices visible. The desk's product catalog makes requotes mechanical: the 40ft rate, the surcharge, the validity date — all lookup, none of it retyping; the AI drafts the covering note ("rates recalculated for the larger unit, validity 14 days") and the human sends it. Rates that expire become queue work that dates itself: a view of "quotes expiring this week" turns the chase from a memory exercise into a morning list. This is the design principle that pays for the migration: every requote that does not fork is a customer not comparing wrong versions.
Freight's hardest days are exception-shaped, and the desk design meets them. The delay: EISU-4821 slips a week; the update is drafted once (AI assist, human-reviewed per the copilot guide's discipline) and lands on every affected thread — not as a broadcast, but as replies in the conversations that carried the shipments; each customer's question about their cargo has its thread to be answered in. The demurrage question: "why are we charged per day?" — the answer cites the quote in the same thread, and the refund policy if it comes to that. The "we never received" question: the POD is attached to the thread; the reply attaches it forward. The angry buyer: the thread already carries the promise, the rate and the delay note — the channel playbook handles the tone. Exceptions are where freight desks lose customers; threads are where they keep them.
Forwarders' volumes breathe — Q4 surges, fair seasons, quiet Augusts — and the meter should breathe with the team. Onsites' shape: three seats free forever (a small agency rides $0 + credits), $15 per seat beyond (a customer-ops team of eight licenses the whole team — including the warehouse coordinator checking PO numbers — for $75/mo billed annually), storage 100 MB included with $1/GB for the POD-and-BL archives, AI credits prepaid at cents for drafts, translations and summaries — the Mandarin-to-Dutch translation on a WeChat thread bills at 3 credits, not an assistant subscription. Self-hosting exists for forwarders whose compliance requires it ($15/seat, 10-seat minimum, 60-day trial, your servers, your residency story). The worked examples in the pricing guide show the same desk on per-seat-plus-per-resolution stacks — the meter that punishes Q4 twice — and the flat meter that does not. For an industry built on thin margins and busy seasons, that difference is itself a line item.
Because "fragmentation" is abstract, price one forwarder's week. A five-person customer-ops team tracks the chase across a fortnight: 60 active quotes, each chased or re-quoted on average 1.6 times — finding "which sheet was version three" costs nine minutes average (nine hours), and five requotes of those become wrong-version customer replies costing another two hours of apology and redo. 25 exception weeks (vessel rolls) update 30-odd threads each from wherever the information lives (six hours); 40 "POD please" emails each cost a tab hunt (three hours); the PO-number question — "which thread had the PO for the Milan order?" — costs the team a further five hours monthly. The chase alone: nearly 25 hours a month, half a full-time colleague, none of it visible in any pricing sheet. The desk's thread design retires most of the line: the quote lives where the chase would happen, the POD attaches where the question arrives, and the PO number is a field on the thread the warehouse coordinator opens. The colleague it returns is the migration's payback, usually inside the first quarter — and the reason freight desks, once migrated, never fragment again.
Why do freight forwarders need a support desk instead of just email?
The freight day is a queue — RFQs, quote chases, ETA relays, exception replies, document requests — scattered across Outlook, spreadsheets and messaging apps. A desk makes the work sequential, ownable and searchable instead of memory-shaped.
What is a "one thread per shipment" design?
Inquiry, quote, confirmations, every update, documents and invoice live in one thread. Nothing retypes, nothing forks, and a year later the full history of what was promised and paid is scrollable in place.
How does the 20ft-to-40ft requote work?
The quote lives in the thread and edits in place from the shared rate card — one message produces the new version beside the old, with the covering note AI-drafted and human-sent. No version-four-of-a-spreadsheet, no buyer comparing wrong PDFs.
Can freight teams self-host the desk?
Yes — the self-hosted product runs from your Docker host with your storage and AI model or Onsites-hosted equivalent, on $15/seat monthly billed annually (10-seat minimum, 60-day trial, updates and support included, licenses final sale).
How does the meter behave in freight's seasonal peaks?
Seats stay $15 (three free forever regardless); the busy season rides only the credits line at about a cent per assist. No per-resolution meter bills your best quarter twice — the trap of seat-plus-per-resolution stacks worked through in the pricing guide.