The department inbox is the working surface. Everything inbound for your area, in one list, whatever channel it came through.
The buckets
| Bucket | Holds |
|---|---|
| Inbox | Open and needing attention |
| Mentions | Where you were named |
| Assigned | Owned by somebody |
| Unassigned | Owned by nobody |
| Snoozed | Hidden until later |
| Drafts | Written and not sent |
| Sent | Gone |
| Muted | Deliberately silenced |
The two that do the work
Unassigned is the one to watch. A thread with no owner is a thread everybody assumes somebody else has, and it is where things are actually lost. In a healthy team this bucket is close to empty by the end of each day. A team that never looks at it discovers a two-week-old complaint eventually, usually from the customer.
Mentions is your personal queue inside a shared one. Somebody named you because they need you specifically, and that deserves attention ahead of the general pile.
The other six are states rather than queues. You visit them when looking for something, not as part of the daily pass.
Assigning
Taking a thread makes you responsible for it, visibly.
Assign early rather than after resolving. The assignment is not a record of who did the work, it is a signal to everybody else that they can stop looking. Assigning at the end means four people read the same message and two of them started drafting a reply.
Assign to a person, not to a team. A thread owned by a team is unassigned with extra steps, and it will sit there looking handled.
Take it back off somebody who is away. An assigned thread is one everybody else has stopped watching, which is exactly wrong when the owner is on leave for a fortnight.
Reassign rather than forwarding. Moving the thread carries its history with it. Forwarding the content into a new message throws that history away and starts a second conversation about the same thing.
Snoozing
Hides a thread until a time you choose, then returns it.
Right for something genuinely waiting: a customer coming back on Monday, an answer due from a supplier, a callback promised for Thursday afternoon. Wrong as a way of tidying the list, which is what muting is for.
A snoozed thread comes back where it was rather than at the back of the queue, so nothing is lost by using it, and there is no reason to leave something sitting in the inbox as a reminder.
Muting
Silences a thread without closing it. It stops asking for attention and stays findable.
Use it for a conversation that is over but not formally finished, and for anything generating replies you do not need to read. An automated notification thread a colleague is handling is the usual case.
The difference in one line: snooze what you will act on later, mute what you will not act on at all.
Reading the list
Each row carries its channel as an icon with its own tint, so the list is scannable without being read. Email, WhatsApp, calls, SMS, voicemail, web chat, bookings and signature requests each look distinct at a glance.
Priority shows as a dot rather than as a coloured row, which keeps a busy list legible. A list where every urgent item shouts is a list where nothing does.
Searching rather than filtering
Buckets and filters answer "what needs doing". Search answers "where is that thing".
Reach for search when you know something concrete: a name, a number, a phrase from the message. Reach for a bucket when you are working, not looking.
The distinction matters because people try to use filters as a search and end up building a saved view for a question they will ask once.
Saved views
A scope and a filter, kept.
Two earn their place for most people. Unassigned in my department, the daily first pass. And assigned to me and not snoozed, which is what you actually owe today.
More than three or four saved views and you have built a second navigation, which is usually a sign the filters are doing work the buckets should be doing.
When the sender is not somebody you know
Plenty of inbound arrives from an address or a number attached to nobody.
Attach it to a record early if there is one to attach it to. A conversation floating free is one that will not appear on the account it belongs to, and nobody looking at that account will know it happened.
If there is no record yet, that is fine. A stranger asking a question is a lead at most, and creating a company record for somebody who asked about opening hours is how a database fills with noise. Attach it when there is a reason to.
The one to watch is the existing customer emailing from an address you have never seen. It looks like a stranger, it is not, and the conversation will be filed nowhere useful unless somebody notices.
Working it
Unassigned first, and assign rather than answer. Two minutes giving every orphan an owner is worth more than answering three things well while five sit unclaimed.
Then your own assigned threads, oldest first. Oldest first is not sentiment. The oldest open thread is the one most likely to have turned into a complaint while you were not looking.
Then mentions, which are usually quick because somebody has already done the thinking.
Snooze deliberately, mute freely, close what is finished. An open thread is a claim on somebody's attention, and an inbox full of resolved conversations stops meaning anything within a fortnight.
What it will not do
It will not route for you beyond the department. Getting a thread to the right person inside a department is a human decision, deliberately.
It will not create records on its own. A thread is a conversation. Turning one into a deal, a ticket or a task is an act somebody takes, and no channel does it automatically.
It will not show you other departments. By design, and it is the reason the surface stays usable at forty people rather than collapsing into a feed.
Did this answer your question?
No, ask a person