Moving a 25-person NVOCC from email threads to a tracked booking pipeline

A 25-person NVOCC headquartered in the UK, with teams in the USA, UAE, India, and Poland, ran every client and vendor conversation over email. Booking requests, shipping line quotes, document approvals, and invoices all lived in inboxes.

Why email breaks down for an NVOCC

An NVOCC sits between the shipper and the shipping line, so every booking pulls in clients, carriers, and agents across several countries and time zones. Cut-offs don't move, and a booking that slips through the cracks becomes a missed sailing. Email kept the record of what was said, but it couldn't show where each booking actually stood. Status lived in the head of whoever had last read the thread.

Two parts: the conversations and the bookings

The fix had two parts, because the problem did. The conversations with clients and vendors needed an owner and a status, and the bookings themselves needed a lifecycle that everyone could see.

A help desk for shared team inboxes

Like most NVOCCs, the company works from shared team addresses rather than personal ones. A client or shipping line writes to a team address, and anyone on that team might pick it up, or nobody might. We chose a help desk and ticketing platform that matched the team's requirements and routed those shared inboxes into it.

Every client and vendor thread now shows which team and which person owns it, whether it's New, Pending, In Progress, or Completed, and who sent each reply. A pending thread makes clear whether the team is waiting on the client or on a vendor, instead of the answer being buried somewhere in a mailbox five people read.

A custom dashboard for the booking lifecycle

Alongside the help desk, we built a custom dashboard that follows each lead through its full lifecycle: Proposal, Booking, Transportation, Documentation, Clearing Customs, Vessel Loading, and Invoicing. Anyone on the team can see where every booking stands and what it needs next. Because Invoicing is part of the same lifecycle, finished bookings don't sit waiting to be billed.

The dashboard also took on the slowest part of every booking. Shipping line rates change constantly, and every booking used to start with a round of calls to check availability and price. The dashboard now pulls live availability and rates directly from the shipping lines' APIs. The team enters the client's requirements and sees which containers are available, what they cost, and how that compares across lines.

Not every shipping line offers an API. When none of the connected lines can take a booking, the dashboard tells the team which other lines to contact and whether to call or email each one, so the decision takes seconds instead of a guess. Those manual contacts now come up only two or three times a week, where before every booking needed a call.

Six months of pilot before going live

We ran the new pipeline as a six-month pilot before switching it to production, so the help desk workflows and the dashboard were shaped by real bookings rather than by a whiteboard plan. It has now been running live for eight months.

What changed

Before, bookings depended on one person in a five-member booking team who knew where everything stood. Now all five work bookings in parallel, because the help desk and the dashboard show each of them what needs doing and where. The team has gone from handling 5–7 bookings a day to 20–30, and it's converting more of them into confirmed business.