SBX Tools Outlook shared inbox control for operations and dispatch teams
Vendor confirmations, order changes, shipment updates, dispatch coordination, supplier follow-ups — every email in ops@, dispatch@, orders@, and logistics@ gets an owner, a status, and a history. Without leaving Outlook.
Sounds familiar?
When ops shares an inbox between dispatchers, vendor managers, or warehouse coordinators, the inbox itself doesn't tell anyone what's been handled. Color flags and "I'll grab this one" chat pings break down as the volume grows.
"Did anyone confirm the shipment date with ACME yet?"
"This order change has been sitting two days — I thought Mark was on it."
"Sarah handled the recurring vendor last quarter — what payment terms did she set?"
"How many dispatch confirmations went out this week?"
"The same supplier wrote twice — what did we tell them on Monday?"
"Outlook says Mark Complete — but did we actually update the dispatch board?"
How SBX changes the day
Ops teams coordinate dozens of vendors, customers, and internal handoffs through ops@ or dispatch@. Three dispatchers share the inbox; each one knows roughly which vendors are "theirs", but emails arrive unaddressed, and the team has no shared way to claim ownership. They tried color-flag categories (one color per dispatcher), but the flags don't sync across devices reliably, and when one dispatcher is offline the rest can't tell what they were on. The spreadsheet tracker for daily dispatch counts is updated end-of-day — too late for mid-day capacity decisions.
With SBX, every email in ops@ gets assigned to one dispatcher. Status moves from Open to Closed when the work is done — shipment confirmed, order change acknowledged, vendor question answered, dispatch board updated. Internal notes (Confirmed Tue dispatch, vendor invoice pending) stay on the email thread. Three dispatchers work the inbox in parallel without stepping on each other, and the ops lead has a real-time view of what's open, what's closing, and what's aging out.
One email, step by step
Below is one common example — a vendor confirming a shipment date — used to make the flow concrete. The same four steps apply to any email in this inbox: an order change from a customer, a delay notification from a carrier, an internal handoff from sales, a billing query from a vendor.
The email arrives
A vendor emails ops@ confirming a shipment date. SBX shows status Open.
- Visible to every dispatcher on the team
- Threaded with previous emails from the same vendor
- Default status:
Open
One dispatcher claims it
Whoever has bandwidth opens the Assignee dropdown and picks their own name. The vendor's email has a name on it.
- Claim it for yourself, or hand it off — the same dropdown lists the whole team
- Visible to the whole team
- Internal notes available for asking colleagues (
Anyone confirm warehouse capacity Tuesday?)
Confirm, update the system, then close
The dispatcher confirms the shipment date with the warehouse (internal forward, chat ping, dispatch-board update — whatever your team does), replies to the vendor with the confirmed slot, and clicks Closed in SBX. The timeline records who did the work and when, with the internal note as audit trail.
- SBX does not integrate with dispatch boards, TMS, WMS, or ERP — those workflows are unchanged
- The
Closedbutton is a status change; the email and its history stay searchable - Internal note (
Confirmed Tue 08:00 dispatch, vendor invoice expected Wed) stays on the email thread
Week-in-review
The ops lead pulls up SBX's Insights & Analytics view: how many emails came into ops@ this week, how many are still Open, who took the most volume, what aged out past N days.
- Status filters:
Open,Closed - Per-assignee filter
- Built-in indicator for emails that haven't moved status in N days — especially important for vendor coordination
What a typical week looks like in an ops@ inbox with SBX
Monday morning, ops@ has accumulated the weekend's mix — vendor confirmations for Tuesday dispatch, a carrier delay notification, two order changes from customers, an internal handoff from sales for a new account. Each dispatcher claims a batch — by vendor, by region, or just first-come — and works through it. Mid-week, a recurring vendor (the same one that asked last Friday) writes back; SBX shows the previous thread was Closed by Anna, with the internal note Confirmed Tue dispatch, vendor invoice pending. The current dispatcher can respond without re-asking colleagues. Friday afternoon the ops lead checks capacity: how many dispatches went out, what's still open, what aged past two days for follow-up.
Common questions from ops leads
Read next
See SBX in your own ops@ or dispatch@ inbox
1 month free, no credit card. Install from AppSource and try it on a single mailbox before rolling it out to the team.
Single tier. €6/user/month annual, €8/user/month monthly. See pricing →