The inbox's new job
How your inbox changes when Fin handles the front line, and why organizing around expertise beats organizing around volume.
When Consensys deployed Fin across their support channels, more than 70% of customer conversations were fully resolved by Fin.
“We got to 50% containment very quickly. Over time we increased this to 70%, and we were still seeing very high customer satisfaction. That combination is rare.”
“The team isn’t strapped anymore. They’re doing the complex, valuable work humans are best at. Fin handles the volume.”
Yair Gal, Support Lead at Consensys
When that much volume shifts away from your team, it changes something fundamental about how your helpdesk is structured. Your inbox is where that shift begins.
Prerequisites
Before you start, make sure you have the following in place.
- An Intercom workspace: You need an active Intercom account to follow along. Start a free trial at intercom.com if you don’t have one yet.
Video transcript
Think about what your inbox has always been. It's the starting point. Every conversation arrives there, and your team handle it in real time. You've probably built team inboxes around how to manage that volume by channel, by tier, or by region. That logic made sense because everything landed in the same place and someone, probably you, had to figure out where it should go. And now you're here. You've chosen Intercom. You've seen what Fin can do, and you may already have a way of running support that works for your team. And that's okay. We're not asking you to unlearn anything. What we wanna do is show you what becomes possible when you're building from day one with Fin at the frontline so that when you're setting things up, you know where you're headed and why. When Fin handles the frontline, most of that sorting has already happened before your team sees anything. The routine questions, the "how do I do it"s, the password resets, the things that used to fill a tier one queue. Fin now handles them. What reaches your team are the conversations that genuinely need their expertise. They arrive with the context already attached, like what happened, what was tried, and what the customer actually needs. That changes how you might think about your team inboxes. Instead of organizing around volume, which channel, which tier, you can organize around expertise, an inbox for billing specialists, another for complex technical issues, and a dedicated inbox for enterprise customers. This structure reflects your team's strength and your customers' needs, and then Fin routes accordingly. Even if Fin starts on just one channel or one topic or one segment, or you don't restructure everything from day one, this idea that your inbox is becoming a place for specialized work and not general triage will shape how you set things up from here on out. With this foundation, all the manual triage and the hours spent routing conversations to the right person start to disappear. And what we hear from customers is that their time goes to work that's more creative, more impactful, and a lot more fulfilling. And that's the transformation. And the rest of this course will get practical. You'll set up these team inboxes and the knowledge and routing logic that makes all of this work possible step by step.
The inbox in an AI-first operation
In a traditional setup, team inboxes are organized around volume management: by channel, by tier, by region. When Fin handles the front line, a different organizing principle becomes possible: expertise.
Instead of splitting work by where it came from, you can organize around what your team is best at and what your customers need. That might mean inboxes built around specialism:
- A billing team / a technical team
- Customer segment (enterprise customers routed to your most experienced teammates)
- Issue type (refund requests in one queue, account security in another)
The conversations that arrive in those inboxes have already been triaged, summarized, and classified by Fin before an agent ever sees them. Your team picks up where Fin left off, not from the beginning.
That also changes what support managers spend their time on. Before deploying Fin, Rocket Money had a teammate spending two to three hours a day manually rerouting conversations. After implementing Fin, that manual triage was greatly reduced.
As Michelle McGowan, Director of Operations at Rocket Money, put it:
“This is what a modern support team looks like. It’s not about removing humans. It’s about redesigning the work so humans are focused where they add the most value.”
This doesn’t require a full restructure on day one. Even if you’re rolling Fin out gradually, starting with chat while email stays with your team or deploying on certain topics first, setting up your inboxes around expertise from the start means you’re building toward the right structure as Fin’s coverage grows.
What this shift looks like in practice
Imagine a Fintech company setting up their helpdesk for the first time.
Before: organized around volume:
| Team Inbox | Purpose |
|---|---|
| Chat | All live chat conversations |
| All email conversations | |
| Social | Facebook and X messages |
| EMEA | European customers |
| APAC | Asia-Pacific customers |
| Billing | Billing issues across all channels |
Six inboxes, mostly split by channel and region. Teammates are assigned by which channel they monitor, and volume is distributed based on availability.
After: organized around expertise:
| Team Inbox | Purpose |
|---|---|
| Billing & Payments | Refunds, disputes, payment failures |
| Account Security | Suspicious activity, access issues, verification |
| Enterprise Accounts | Dedicated support for high-value customers |
Three inboxes, organized by what the team is best at. Fin handles the front line across all channels: email, chat, social, in every language, 24/7. Volume from different regions no longer needs separate inboxes because Fin has already handled the triage, and what reaches your team are the conversations that need specific human expertise.
