Inbox assignment: who owns a conversation, and why 'everyone' means nobody

Every conversation in a shared inbox should be owned by one person or one queue with a named owner. When a conversation belongs to "the team", it belongs to nobody, and it is the one that sits for three hours while everyone assumes someone else has it. Assignment can be automatic (by location, by service, round robin) with reassignment by a person, and the inbox should show, at a glance, what is unowned and what has waited longest.

The unowned conversation

The AI handled the first reply. The customer asked something that needed a person. The conversation was flagged and sat in the inbox, visible to five people, answered by none, because each assumed another would. The customer texted again at 4pm: "Hello?" That is the failure assignment prevents, and it is more common than any AI mistake.

Ways to assign

By location. A multi-branch business routes each conversation to the branch it concerns, and the branch's front desk owns it. This is the most common rule for service businesses.

By service or topic. Billing questions to the office manager; bookings to the front desk; new leads to whoever works leads.

Round robin. Each new conversation to the next person in rotation. Fair, simple, and it ignores who is actually good at what.

To a queue with an owner. Conversations go to "Front desk" and the front desk lead is accountable for the queue. The people in it pick up; the lead makes sure nothing waits.

Manual. A person triages and assigns. Works for tiny teams and fails the moment that person is at lunch.

Most businesses combine: automatic assignment by location into a queue, with a named owner per queue, and reassignment by a person when needed.

Reassignment

People go to lunch, go home, go on leave. A conversation assigned to someone who is not there is as unowned as one assigned to nobody. The inbox should let anyone reassign, should let a person hand their conversations to a colleague when they leave for the day, and should show conversations assigned to people who are marked away.

The branch problem

At a multi-location business, a branch manager should see and own conversations about their branch, and should not be looking at another branch's. The owner sees all of them. Conversations that are not about any branch (a general enquiry to the main number) go to a shared queue. The AI's booking, once a location is chosen, determines the branch, and the assignment follows.

The AI and assignment

While the AI is handling a conversation, it is owned by the AI, visibly. The moment it hands off, the conversation is assigned by the rules and the customer is told who. The handoff should never land in "unassigned"; it should land on a person or a queue with an owner, with the reason for the handoff shown.

The report that matters

Conversations waiting for a reply, by owner, with the longest wait at the top. Unowned conversations, if any, in red. Median time from handoff to first human reply, by person and by queue. A manager who looks at this once an hour finds the stuck ones before the customer texts "Hello?".

Frequently asked questions

Should the owner of the business be assigned conversations?

Only if they are actually working the inbox. Assigning to an owner who is not is the same as assigning to nobody.

What about after hours?

Handoffs after hours go to the morning queue with a timestamp, and the customer is told when to expect a reply. The first person in picks up the queue.

Can a conversation have two owners?

No. One owner, with internal notes for the second person. Two owners is how both assume the other replied.

What Frontiva does here

Frontiva's unified inbox lets you assign each conversation to a person, tag it, set priority and snooze it, and sorts the list by real activity so what needs an answer is at the top. For leads, lead management can auto-assign to the teammate with the fewest open leads. Rule-based routing into queues is not built. See internal notes and handoffs for how a second person helps without taking over.