One Inbox, Four Statuses
A shared inbox only works if everyone agrees what "done" means. Here is a simple routine for running team conversations with open, pending, snoozed and closed — plus assignees and a response target.
A shared inbox fixes the obvious problem: client email no longer lives in one person's account. But it creates a quieter one. When everyone can see every conversation, nobody is sure which ones are theirs, which ones are finished and which ones are waiting on the client. The inbox fills up with threads that are technically read and practically abandoned.
The fix is not more discipline. It is a small, shared vocabulary.
Four statuses, no more
The Swelis One Inbox groups email, texts, calls and WhatsApp into one conversation per person, and every conversation has a status. There are four, and each means something specific:
- Open — it needs something from us.
- Pending — we replied and are waiting on them.
- Snoozed — not now; it comes back at a time you pick.
- Closed — nothing left to do.
The rule that makes it work: every conversation you touch leaves your hands in one of those four states. If you replied, it is pending. If it is a "let's talk next month", it is snoozed until next month. Nobody leaves a thread open just because they read it.
Every conversation has a name on it
Status says what is happening. The assignee says who is doing it. The views on the left show what is assigned to you, what is unassigned and what is unread — and the unassigned view is the one to watch. A conversation with no owner is a conversation nobody will answer. Who may open the Inbox at all is set per person or group in Team settings.
Because read state is shared, a conversation one person reads is read for everyone. That is deliberate: "unread" should mean nobody has looked, not that you personally have not.
A shared inbox is not shared because everyone can see it. It is shared because everyone agrees what each thread needs next.
Talk about it inside the thread
The worst habit in a team inbox is the side conversation — a chat message asking "who is answering the client about the invoice?" that lives nowhere near the invoice. Internal notes sit in the thread in yellow, are never sent, and an @mention notifies the teammate. The discussion stays with the conversation it is about. Outside the Inbox, the same idea works on every page with comment pins and live presence.
For answers you give every week, saved replies are inserted by typing /, with variables such as the contact's first name. Several drafts can be open at once, so a half-written reply does not block the next thread.
A five-minute routine
- Start with Unassigned. Give every conversation an owner before you answer anything.
- Then work Assigned to me, oldest ring first.
- Leave each thread in a status. Pending, snoozed or closed — never open by accident.
- End the day on Pending. Anything waiting too long on the client is a follow-up, not a mystery.
An inbox the whole team can see is a start. An inbox the whole team reads the same way is the point. And for the updates clients keep asking about, the client portal answers before they write. Calls you make from a call list land in the same conversations.
See it on screen: the Shared Inbox scene on our features page answers a WhatsApp from the same box as email.