A shared inbox is useful only when the team can tell who is responsible for the next reply. As volume grows, one undivided list creates two expensive questions: “Is someone handling this?” and “Am I about to send a duplicate answer?”
Three views of the same support queue
Lavenity now separates the inbox into three ownership views. Your inbox shows conversations assigned to you, All gives the team a workspace-wide view, and Unassigned collects conversations that still need an owner. The Open and Closed filter remains separate, so ownership never gets confused with resolution state.
An operator can assign or reassign a conversation from the chat header. When someone answers an unassigned conversation first, Lavenity automatically assigns it to that operator without overwriting a deliberate manual assignment. It is a small rule that removes a lot of coordination work.
Automatic and manual assignment
The navigation badges count open conversations in each ownership view. That makes Your inbox a personal queue, Unassigned a team triage queue, and All the place to check workload or step in when a teammate needs help.
A simple workflow is enough for most teams: watch Unassigned for new requests, reply to claim one, work from Your inbox during the day, and close the conversation when the customer’s question is resolved. Owners can still reassign a thread whenever expertise or availability changes.
Separating ownership from conversation status
The result is clearer accountability without rigid ticket routing. Visitors still get a fast, human conversation; operators get enough structure to avoid collisions and missed replies.
A working rhythm for a small team
Start a shift in Unassigned and triage new requests. Continue from Your inbox as the personal work queue, and open All when helping a colleague, checking workload, or locating a specific conversation. Before the shift ends, hand off threads that cannot be continued by the current owner.
Do not close a conversation merely because it moved to another operator, and do not remove the assignee only because the team is waiting for the customer. Ownership answers who watches the next step; status answers whether the underlying issue is complete. These signals solve different problems.
Frequently asked question
What happens when an operator replies to an unassigned conversation?
The first responding operator becomes the assignee when no one was assigned manually. This removes an extra click without overwriting an intentional assignment to another teammate.