What is a shared inbox?

Shared inbox, explained

Many small teams start with a group address such as support@ forwarded to several people. That quickly breaks: two people reply to the same customer, or everyone assumes someone else did. A shared inbox fixes this by treating each conversation as an item with a status and an owner.

Typical capabilities include assignment, internal notes, statuses such as open, pending and closed, collision detection so two people do not reply at once, and a full history of the customer's previous conversations.

With AI chat, the shared inbox becomes the place where automated and human support meet. The bot handles what it can; conversations it hands off appear in the inbox with everything that was said, so the teammate can continue rather than restart.

The inbox is also a feedback loop. Handed-off conversations show exactly what the automation could not handle, which is the most direct input for improving the knowledge base.

Common mistake

How SuperBot relates

SuperBot includes a shared team inbox with human handoff and the full transcript, and every plan includes unlimited team members.

• SuperBot features
• SuperBot pricing
• The 2026 AI support stack for fewer tools

Related terms

• Human handoff (escalation)Human handoff is the point where an automated system such as a chatbot passes a conversation to a person, ideally with the full conversation history and context attached. Good handoff rules trigger on low confidence, sensitive topics, explicit requests for a human or signs of frustration, and tell the customer what happens next and how long it will take.
• Live chatLive chat is a support channel where customers exchange real-time text messages with a business, usually through a widget on its website or app. Traditionally the replies came from human agents; many live chat tools now put an AI agent first and bring in a person when needed, so “live” increasingly means immediate rather than necessarily human.
• Omnichannel supportOmnichannel support means serving customers across multiple channels, such as email, chat, phone, social and messaging apps, with a connected history, so a customer can switch channels without starting over. It differs from multichannel support, where channels exist side by side but each conversation is isolated from the others.
• First response time (FRT)First response time (FRT) is the time between a customer contacting support and receiving the first reply. It is usually reported as a median or average over a period. Automated acknowledgements are often excluded, because FRT is meant to show how long customers wait before someone, or something, actually starts helping.
• Service level agreement (SLA)A service level agreement (SLA) in customer support is a defined commitment for how quickly a team will respond to or resolve customer requests, such as a first reply within four business hours. SLAs can be contractual promises to customers or internal targets, and are usually set per channel and priority level.