Skip to content

Shared inbox best practices for a front desk team

The failure is not slowness, it is ambiguity: three people read a message and each assumes another will reply. Ten habits that remove the ambiguity, and the one that only software can enforce.

Sohail Safdar · · 5 min read

A shared inbox does not fail because people are slow. It fails because of ambiguity: three people read a message, each reasonably assumes one of the others is dealing with it, and nobody replies.

That is worth stating first because it changes what the fix is. Urging the team to be quicker does nothing about a problem whose cause is that nobody was sure it was theirs.

Ten habits

1. One owner per conversation. Assign it the moment a person needs to act. "The team" is nobody, and an inbox where everything is owned by everybody is an audience rather than a queue.

2. Reply or reassign, never just read. Opening a conversation and leaving it without acting is how a customer waits an afternoon, and it is also how the conversation stops looking new to everybody else who scans the list.

3. Notes in the thread, not in a group chat. The next person should find the context where the conversation is, not in a chat app, not in somebody's head, not in a text to a colleague. Internal notes and handoffs has the four-line note worth copying.

4. A short tag list. Six to ten, each with a written meaning: billing, new patient, complaint, urgent. A tag applied inconsistently is worse than no tag, because it makes a filter look authoritative while being incomplete, and somebody will decide something from that filter.

5. Priority for the few. If everything is high priority, nothing is. Reserve it for complaints, real deadlines, and anybody who has already waited too long.

6. Snooze with a date, not a hope. "Waiting for the insurer" becomes a snooze until Thursday with a note. Snoozing conversations well covers when it is the wrong tool.

7. Promises written down. If you told a customer somebody would call by three, that goes in a note. Promises are the specific thing that gets lost in a handoff, and a broken promise costs more than the original delay.

8. The same answer to the same question. If three people answer a question three ways, the answer belongs in your approved knowledge rather than in three heads. The tell is a question the team finds slightly annoying to answer: that is a question that has been asked a hundred times and never written down.

9. Cover lunch and leave. Before stepping away, reassign what you own or leave a note. A conversation assigned to somebody who is not there is unowned and looks owned, which is the worst of the two states.

10. The five-minute review. End of the day, everything waiting on a reply, oldest first. Answer, reassign, or snooze with a reason. The point is not the answering, which mostly happens anyway; it is finding the two that have been sitting since the morning because their owner went out.

The habit only software can enforce

Habits 1 to 10 are discipline, and discipline degrades on a busy Friday. One version of the ambiguity problem cannot be fixed by discipline at all:

Two people answering the same customer at the same moment. Both saw it was unowned, both were being helpful, and the customer now has two replies that may not agree.

No amount of training prevents that, because at the moment each person started typing they had correct information. The only fix is for the inbox to say, above the reply box, that somebody else has this conversation open and is already typing.

If your tool does that, use it rather than relying on habit 1 alone. If it does not, habit 1 has to be stricter: assign before answering, every time, even for a one-line reply.

What to do with the AI's handovers

Treat each one as a new conversation that needs an owner, immediately.

A handover is different from an ordinary unread message in one way worth building a habit around: the customer has already been told somebody is coming. So the clock on it started before anybody in your team saw it, and a handover sitting in the list for twenty minutes is worse than an unread message sitting there for twenty minutes.

They should be visibly marked rather than blending in. When an AI receptionist should hand off covers what should produce one.

Two numbers worth watching

Conversations with no owner, right now. Should be close to zero during opening hours. A number that is persistently non-zero means habit 1 is not happening, whatever anybody says about it.

Oldest waiting conversation, in open hours. One number, visible, and it tells you more than a median because it is the customer having the worst experience of your business today.

In Frontiva

The unified inbox carries assignment, tags, priority, snooze and internal notes in line with the conversation, which is habits 1, 3, 4, 5 and 6 as actions rather than conventions.

A line above the reply box says who else has the conversation open and whether they are already typing, which is the habit discipline cannot enforce. It is the one thing in this list that prevents a failure rather than reminding somebody about it.

Bulk assign, tag, prioritise, close, reopen and snooze make the end-of-day review a few clicks rather than one thread at a time, which matters because a five-minute habit that takes twenty minutes becomes a weekly habit and then stops.

Filters save under a name the whole practice can use, and a view that means "assigned to me" resolves correctly for each person who opens it, so one saved view works for everybody rather than needing one per person.

One thread per customer across email, SMS, Instagram, Messenger, WhatsApp and website chat, so the same person texting and then DMing is one conversation with one owner rather than two unowned ones. An AI reply shows the source it answered from alongside it, which is what makes habit 8 actionable: you can see which approved fact produced an answer, and fix the fact rather than the reply.

Frequently asked questions

Why do shared inboxes fail even when the team is working hard?

Because the failure is ambiguity rather than slowness. Three people read a message, each reasonably assumes one of the others is handling it, and nobody replies. Effort is not the variable: an inbox without ownership is an audience rather than a queue, and adding people to an audience makes the problem worse rather than better.

How many people should work one shared inbox?

As many as the volume needs, provided each conversation has exactly one owner. Two people with clear ownership consistently outperform five without it, because the second arrangement produces the diffusion described above. The number of people is almost never the problem; the number of owners per conversation is.

How many tags should a shared inbox have?

Six to ten, each with a written meaning. A tag used inconsistently is worse than no tag, because it makes a filter look authoritative while being incomplete, and somebody will make a decision from that filter. If your list has grown past about a dozen, most of the extras are describing the same few things in different words.

What should happen when the AI hands a conversation over?

It becomes a new conversation that needs an owner, immediately, and it should be visibly marked as needing a person rather than blending into the list. A handover into a queue nobody owns has escalated to nothing, and from the customer's side that is indistinguishable from never having been escalated, except that they were told somebody was coming.

What does the end-of-day review actually consist of?

Five minutes, oldest first, through everything waiting on a reply. For each: answer it, reassign it, or snooze it with a reason and a date. The value is not in the answering, which mostly happens anyway, it is in finding the two conversations that have been quietly waiting since the morning because their owner went to lunch.

Get the next one by email

Email me when Frontiva publishes a new guide or post. At most one a week, nothing else, and an unsubscribe link in every one.

To keep spam out, we record your IP address, approximate location and browser with your message. Privacy Policy

Start free. Be live this week.

Built for dental, med spa, home services, and the businesses that live on the phone.