SBX Tools Outlook shared inbox control for internal IT helpdesk teams
Password resets, laptop requests, VPN issues, software access, onboarding tickets — every email in helpdesk@, it@, support@, and tickets@ gets an owner, a status, and a history. Without leaving Outlook and without a separate ticketing tool.
Sounds familiar?
When IT shares an inbox with three people behind it, the inbox itself doesn't tell you who's on which request. Spreadsheet trackers, color flags and "I'll grab this one" chat pings stop working past a few requests a day.
"Did anyone reset Marko's password yet, or is he still waiting?"
"This VPN issue's been open three days — I thought Anna was on it."
"Sarah set up the new hire's laptop last month — what config did she use?"
"How many software-access requests did we close last week?"
"The same user wrote twice this week — what did we tell them on Monday?"
"Outlook says Mark Complete — but did we actually do the access change?"
How SBX changes the day
One of our customers is an internal IT team of four people behind helpdesk@. They tried a full ticketing tool, but configuring it took a quarter, the per-agent cost was three times their email-based budget, and most of their work — password resets, access tickets, VPN issues — was already coming in as email. Half their day became copying email content into the ticketing tool, and the other half was answering follow-up questions in two different threads (one in email, one in the ticketing tool). Half the team gave up and went back to working helpdesk@ directly; the other half kept the ticketing tool. Nothing was consistent.
With SBX, the team works helpdesk@ directly in Outlook. Every email gets assigned to one technician. The status starts at Open and moves to Closed when the request is handled — password reset done, VPN issue resolved, laptop config applied. Internal notes (e.g., Reset password via Azure AD, force change on next login) stay on the email thread. Four technicians work the inbox in parallel without stepping on each other, and the IT lead has a Friday-afternoon view of what came in, what closed, and what aged out.
One request, step by step
Below is one common example — a password reset request — used to make the flow concrete. The same four steps apply to any email in this inbox: a VPN issue, a software-access request, a laptop hardware question, an onboarding task.
The request arrives
A user emails helpdesk@ asking for a password reset. SBX shows status Open in the team's shared view.
- Visible to every technician on the team
- Threaded with previous emails from the same user
- Default status:
Open
One technician claims it
Whoever has bandwidth opens the Assignee dropdown and picks their own name. The 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 know if this user has 2FA enforced?)
Resolve, reply, then close
The technician does the work in the relevant Microsoft 365 admin or system tool (Azure AD, Intune, on-prem AD — whatever the team uses), replies to the user with the next step, 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 Azure AD, Intune, or other admin tools — the IT workflow inside the admin tool is unchanged
- The
Closedbutton is a status change; the email and its history stay searchable - Internal notes (
Reset via Azure AD, MFA still enforced) stay on the email thread for audit
Week-in-review
The IT lead pulls up SBX's Insights & Analytics view: how many requests came in this week, what categories appeared most often (password resets, access requests, hardware), 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
What a typical week looks like in an IT helpdesk@ inbox with SBX
Monday morning, helpdesk@ has accumulated the weekend's mix — a couple of password resets from people who tried to log in from a hotel, two VPN questions, a laptop-died report from a remote worker, an onboarding-week new hire whose access requests didn't all land in time. Each technician claims a batch — by topic, by priority, or just first-come — and works through it. Mid-week a recurring issue (the same VPN error from three users) gets flagged with an internal note for the IT lead to look at the network side. The IT lead checks the overview Friday afternoon: anything that sat in Open more than two days is reviewed in the weekly standup.
Common questions from IT leads
Read next
See SBX in your own IT helpdesk@ 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 →