SBX Tools Outlook shared inbox control for customer support teams
Customer questions, complaints, refund requests, follow-ups, escalations — every email in support@, help@, customers@, and service@ gets an owner, a status, and a history. Without leaving Outlook and without moving your team to a separate helpdesk.
Sounds familiar?
When customer questions land faster than your team can claim them, the inbox itself doesn't tell anyone what's being handled. Folders, flags and "I'll grab this one" chat pings don't survive past five emails a day.
"Did anyone reply to this customer yet?"
"This one's been sitting for two days — I thought Mark was on it."
"Sarah handled this last month — what did she say?"
"The same customer wrote twice this week — I have no idea what we told them on Monday."
"How many tickets did each of us close last week?"
"Outlook says Mark Complete — but did we actually answer?"
How SBX changes the day
One of our customers started with a shared mailbox and three people on support@. It worked until volume hit a few dozen emails a day — then they could not tell who was on what without messaging the team. They tried moving to an external ticketing tool, but every customer email had to either be turned into a ticket manually (slow and error-prone) or auto-converted (which generated tickets for every newsletter reply and unsubscribe request). The team was now copying answers between Outlook and the ticketing tool, and still didn't trust either system to be complete.
With SBX, every customer email stays in Outlook — same address, same inbox, same threading. Each email gets assigned to one teammate. The status starts at Open and moves to Closed when the customer's question has been answered — visible to the whole team, recorded in a timeline that shows who handled it and when. Three support agents can work the inbox in parallel without stepping on each other, and the customer never sees a ticket number.
One email, step by step
Below is one common example — a customer question about a delayed order — used to make the flow concrete. The same four steps apply to any email in this inbox: a refund request, a feature question, an angry complaint, or a follow-up to a thread from last week.
The question arrives
A customer email arrives in support@. SBX shows it in the team's shared view with status Open — the default for every incoming email.
- Visible to every agent on the team
- Threaded with previous emails from the same customer (Outlook's native conversation grouping is preserved)
- Default status:
Open
One agent claims it
Whoever has bandwidth opens the Assignee dropdown in the SBX panel inside the Outlook reading pane and picks their own name. The email now has a name on it — every other agent sees who is working on it.
- Claim it for yourself, or hand it off — the same dropdown lists the whole team
- Visible to the whole team — the assignee's name appears next to the email in the shared view
- Internal notes available for asking colleagues a question — never sent to the customer
Reply, then close
The agent replies to the customer directly from Outlook. When the question is answered, they click Closed on the email in SBX. The timeline records who handled it and when.
- Reply is sent from the team mailbox (
support@), not the agent's personal address - The
Closedbutton is a status change, not a delete — the email and its history stay searchable - Internal notes stay on the email thread for later reference if the customer writes back
Week-in-review
At the end of the week, anyone on the team can pull up SBX's overview: which emails are open, which closed, which sat untouched for more than three days, who is the busiest.
- Status filters:
Open,Closed(the only two statuses) - Per-assignee filter to see who is currently working on what
- Built-in indicator for emails that haven't moved status in N days
What a typical week looks like in a support@ inbox with SBX
Monday morning, the inbox has accumulated weekend emails — order questions, refund requests, a couple of complaints, a follow-up to a thread the team had hoped was closed. Each agent claims a batch — by topic, by priority, or just first-come — and works through it. Mid-week, a customer replies to a thread; SBX shows immediately whether the original was already closed and who handled it, and the email thread in Outlook shows the prior reply itself — so the agent picking up the new reply doesn't contradict the earlier answer. The support lead checks the overview on Friday: any email that sat in Open for more than two days gets flagged for follow-up.
Common questions from support leads
Read next
See SBX in your own support@ 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 →