What is a shared inbox?

How small teams answer support@ together without forwarded chaos, stepped-on replies, or things quietly falling through the cracks.

The problem: support@ belongs to everyone and no one

Every small team hits this. You set up support@ or hello@, forward it to two or three people, and for a while it works. Then one morning a customer gets two different answers from two teammates within an hour. The next week, a message gets no answer at all because everyone assumed someone else had it. Nothing broke; the system was just three people BCC-ing their guesses at each other.

Distribution lists and shared logins have the same flaw: there's no way to tell what's been handled, who's on it, or what was already said last month.

What a shared inbox actually is

A shared inbox is one queue for a team address where every conversation has a status and an owner. The pieces that matter:

• Assignment. A conversation belongs to someone. "Open and assigned to Maria" is a fact everyone can see, not a hope.
• Status. Open, closed, or snoozed until Thursday. The inbox shows what's waiting on you, oldest first. Not a thousand read-and-unread flags.
• Internal notes. Discuss a reply next to the thread itself, invisible to the customer, instead of in a side channel that gets lost.
• No double replies. If two people open the same conversation, the second one sees that someone else is already on it.
• History. The whole relationship in one place, so whoever answers can see what was promised in March.

Why it beats a help desk for small teams

Ticketing systems solve this too, for fifty agents. They bring ticket numbers, SLAs, macros, and an interface that makes your customer feel like a case file. If you're a team of two to ten, you don't have a ticket volume problem; you have a "who's got this?" problem. A shared inbox keeps the shape of email (real replies, from a real address, written by a person) and adds just enough structure underneath.

The CRM connection

The real payoff of a shared inbox inside a CRM: every conversation is attached to a contact. When a customer writes in, their timeline is right there. Past conversations, notes, what they bought, the follow-up task someone set. And when you send a broadcast, replies land in the same queue, next to the same history, instead of in one person's personal inbox.

In KruxCRM, the shared inbox works over your existing address. You forward [email protected] in, and replies go out from it. Messages from people not in your contacts wait in a separate area until you add them, so your CRM doesn't fill up with newsletter noise. The shared inbox guide covers the setup in about five minutes.