A mailbox multiple agents work together, with assignment, statuses, and collision detection layered over plain email.
It’s the bridge between a raw Gmail inbox and a full ticketing system — when it stops scaling, see shared inbox vs ticketing.
How it works
One address — like support@ — feeds a single queue that the whole team works from. On top of plain mail it adds the coordination layer a forwarded mailbox lacks: each conversation can be assigned to an owner, carry a status (open, pending, resolved), and be tagged or filtered into saved views. Collision detection warns when two agents open the same thread, so customers don’t get two different answers. Many shared inboxes pull in more than email — live chat and web forms land in the same queue.
Why it matters
- No double replies or dropped threads. Assignment and statuses make ownership explicit instead of relying on who happened to reply first.
- Shared context. The whole team sees the full history, so a handoff doesn’t lose the thread.
- Measurable. A single queue is what makes metrics like first-response-time and resolution-time meaningful.
Common pitfalls
A raw forwarded mailbox has none of this — no owner, no status, no collision warning — so it breaks down past a few people. The opposite trap is over-process: heavy ticketing ceremony on low volume slows a small team down. The right fit sits between the two. As an example, an e-commerce store that started with three people sharing a Gmail login moves to a shared inbox once orders spike, gaining assignment and statuses without adopting a full ITSM tool. Cherryrise is built on this model — email, live chat, and forms in one queue with assignment, statuses, and collision detection; see the shared inbox or weigh it up in shared inbox vs ticketing.
How Cherryrise handles it
Cherryrise treats the shared inbox as the core surface: every channel feeds one queue, conversations carry an owner and status, and collision detection flags overlap before two agents reply. Saved views slice that queue into focused worklists, and automation handles routing and tagging so ownership is set the moment a ticket arrives rather than left to chance.