How the Shared Inbox Routes and Assigns Conversations

Three states and two actions

The Shared Team Inbox is deliberately simple. A conversation is queued, assigned, or resolved. You assign it or you return it to the queue. Everything else is detail.

That simplicity is the point. Support workflows tend to accumulate statuses until nobody is sure what “pending, internal” means, and the shared inbox for a small team needs to be legible at a glance on a Tuesday morning.

How a conversation arrives

Conversations reach the inbox through a handoff. A flow escalation, a refusal threshold, a turn limit, a timeout, a provider error, or a visitor asking for a person can each trigger one. The handoff stops bot ownership, so the automation steps back and a person takes the conversation.

Crucially, the history comes with it. The visitor’s original question, whatever the AI answered, and anything a Form or One field step collected are all attached. That is what makes an assignment useful rather than a mystery to unwrap.

Assigning without ceremony

Assignment gives a conversation an owner. In a team of three that sounds like overhead; in practice it is what stops two people writing the same reply and stops the awkward one going unanswered because everyone assumed someone else had it.

Return to queue is the other half. It is the explicit version of “not mine”, which is far better than an unread conversation sitting in a list while everyone assumes it is handled.

Use assignment as a signal about who is working, not as a management report. The value is coordination in the moment.

Resolve and reopen

Resolve when the customer’s need is met. Reopen when they come back. That second one matters more than it sounds, because reopening keeps the whole history in one thread rather than starting a new conversation with none of the context.

A resolved conversation is not a deleted one. It stays in retained history and stays searchable.

Search is the underrated feature

Search covers contact details, messages, notes and tags, and older conversations load through pagination. In week one that seems unimportant. In month six it becomes the feature you use daily.

The pattern is always the same: a customer references something from before, and the person answering was not the person who handled it. Searching by their email or a phrase from the original message turns a five-minute reconstruction into a ten-second read.

Two habits make search work better. Tag consistently, even if your tag list is only four items long. And keep private notes factual: “customer confirmed the address is the rear entrance” is findable and useful, while “sorted” is neither.

What retention means for all of this

Search, reopening and reporting all draw on retained history, and retention is set by your plan: 30 days on Free, 90 on Starter, 365 on Pro, and unlimited as configured on Business. If your team routinely needs to look back further than your retention allows, that is a plan consideration rather than a workflow one.

Note that idle conversations remain in retained history. A conversation going quiet does not remove it.

A workable team convention

For most small teams, four rules are enough:

1. If you reply, assign it to yourself
2. If it is not yours, return it to the queue rather than leaving it
3. Resolve when the customer’s need is met, not when you are tired of it
4. Leave a private note whenever the next person would otherwise have to ask

Tags and notes that stay useful

Two habits decide whether your history is searchable in six months or merely large.

Keep the tag list short. Four to six tags that map to how you actually work (the service, the stage, or the outcome) will get used. Twenty tags will not, and half-used tags are worse than none because they make search results look complete when they are not.

Write notes as facts. “Customer confirmed the rear entrance is the delivery point” is findable and useful to whoever picks this up next year. “Sorted” is neither. Notes are append-only, so treat each one as a small permanent record rather than a scratch pad.

Both habits cost nothing at the time and pay back the first time someone has to reconstruct a job they were not part of.

Common workflow problems and their fixes

Conversations sitting unassigned. Usually means nobody agreed who covers the queue in the morning. Assignment is a convention before it is a feature.

Everything assigned to one person. The first-responder breakdown in reporting will show this clearly. It is a coverage risk rather than a compliment.

Resolved too early. If conversations are being reopened frequently, “resolved” is being used to mean “I replied” rather than “this is finished”. Agree the definition once.

Search returning nothing useful. Almost always inconsistent tagging or notes that carry no facts. Fixable going forward, though not retroactively, which is the argument for agreeing the convention early rather than after a busy quarter.

Read next: saved replies and private notes, or shared team inbox vs a shared email address.