AI runs the volume. Your team owns the moments that matter.
Every conversation lands in one inbox. The agent handles most of them end to end, and a person steps in to resolve, snooze, or escalate. Nine views, labels, multiple numbers, and the customer context one click away.
- MMariana GómezYes, the lighter plan sounds right for meAI
- DDaniel RivasJust sent the documents overAI
- PPriya SharmaCan someone from your team call me today?You
- LLiang WeiReminding me about renewal next week2h
- SSofía HerreraThanks, that cleared it up completelyAI
An inbox built for AI volume and human judgment
The inbox an operator already knows, with the AI doing the heavy lifting and a clean way to take over the conversations that need a person.
- 01
AI handles most of it
Conversations come in tagged Assigned to AI, and the agent works them end to end. It auto-resolves a quiet thread after about thirty hours so your views stay clean, and reopens if the customer comes back.
- 02
Clean states and a Done shelf
Resolve a conversation when it is handled, snooze it to surface again later, anywhere from thirty seconds to thirty days, and clear it to your own Done shelf. Each teammate has their own, so one inbox does not turn into everyone tripping over each other.
- 03
Escalate to a human in one move
When a conversation needs a person, escalating unassigns the AI and pings the team in Slack. A human has to own a conversation to reply, so nothing goes out under your name without someone behind it.
- 04
Views, labels, and many numbers
Nine sidebar views for the cuts you work daily, labels in eight colors to organize by hand, fast search across every thread, and a channels list so several numbers live in one inbox instead of several tabs.
Open an account without leaving the chat
Every reply, agent or human, reads the same account context, right in the chat.
- Resolves a conversation to a CDP person and related records
- Deep links into the records that matter
- Same context for the AI and the human
The thread stays put, the customer record is shared
WhatsApp, voice, and web chat land in the same inbox. The customer record is shared across them; state is kept per channel, so threads stay separate. One queue instead of one tab per number.
How a conversation moves through the inbox
- 1
Assigned to AI
A new conversation arrives and the agent picks it up, reading the customer context before it replies.
- 2
AI works it end to end
It answers, asks the follow-up, and resolves on its own when the job is done. Most conversations never need a person.
- 3
A human steps in when needed
Snooze it for later, or escalate to unassign the AI and pull in the team. The teammate who owns it replies.
- 4
Resolved, then Done
The conversation is resolved and clears to a Done shelf, ready to reopen if the customer comes back.
A generic shared inbox routes messages. This one runs the conversation.
Where the Boom inbox differs from a support inbox bolted onto a bot.
| Human-only inbox | Inbox plus a bot | Boom shared inbox | |
|---|---|---|---|
| Who handles the volume | Your team, every thread | Bot deflects, team mops up | AI end to end, team on exceptions |
| Handoff to a person | It is all people | Often a dead end | Escalate unassigns AI, pings Slack |
| Customer context | Look it up elsewhere | Bot has none | Context panel in the chat |
| Snooze and later states | Manual reminders | Rare | Snooze 30s to 30d, per-user Done |
Questions about the inbox
See the inbox on your own conversations
Book a 15-minute walkthrough and we will show the AI working a real queue with your team on the exceptions.