Chatbot With Shared Inbox: Five House Rules So Two People Never Answer the Same Chat, Plus a Who-Owns-It Decision Tree

Chatbot with shared inbox tools let the whole team see every conversation, which is great until two people reply to the same customer or everyone assumes someone else has it. The software cannot fix that alone. What fixes it is five short house rules that your team agrees once. This guide gives you the rules, a decision tree for who owns each chat, and an honest list of what LiveChatBot does and does not do for teams.

5house rules
0per-seat charges
3ticket statuses: open, pending, solved
₹0free plan, 2 websites

⚡ In short

  • A shared inbox shows everything to everyone. That is its strength and its risk.
  • Five rules fix most problems: claim, say so, hand off, use tickets, review weekly.
  • Tickets have owners, so use them for anything that cannot finish in one sitting.
  • Use the decision tree to settle who owns a chat in ten seconds.
Chatbot with shared inbox in LiveChatBot: chat widget appearance settings with colour and welcome message
How it looks in LiveChatBot: chat widget appearance settings with colour and welcome message.

The problem

What goes wrong in a shared inbox

Picture three staff, one inbox, and a new chat. Each sees it. Each assumes someone else is on it. Five minutes pass with no reply. Or the opposite: two people reply within seconds, and the customer gets two answers that disagree.

Neither is a software bug. It is a missing agreement. A chatbot with shared inbox access gives you visibility, not coordination.

The cost of getting it wrong is real but quiet. Customers do not complain about a slow reply; they just leave. And they notice contradictory answers more than slow ones.

The fix is not a bigger tool. It is a few rules written on one page and agreed by everyone who answers, including the owner. Short rules get followed. Long policies get ignored.

The bot adds a twist: it may have already answered. Every agent needs to read the bot’s earlier replies before typing, so the customer is never asked the same thing twice.

Rules one to three

Claim, announce, hand off

Rule 1: first to reply owns the chat

Keep it simple. The person who sends the first human message owns that chat until it ends or is handed over. Nobody else types unless asked.

Rule 2: say who you are

Set a team name and avatar in the widget, but have agents sign off with their first name in the first message. Customers feel looked after, and colleagues can see at a glance who has it.

Rule 3: hand off in words, not silence

If you must pass a chat on, send a short message to the customer: “I am passing you to Priya, who handles refunds.” Then tell Priya in your team’s chat. Never just stop replying.

Our guide to live chat response time explains why a quick first message, even a short one, matters more than a perfect long one.

Try it

Who owns this chat?

Follow the arrows from a new chat to the right action. Print it and stick it where your team can see it.

New chat arrives in the shared inbox
↓
Has a human already replied?
↓
Yes: leave it alone unless asked to help
↓
Colleague is away? Ask in your team chat first
Can the bot answer it?
↓
Yes: read the bot’s reply, then add only what is missing
Needs a person now?
↓
Send a first reply and own it
↓
Cannot finish today? Turn it into a ticket with an owner

Rules four and five

Use tickets for owners, then review weekly

Rule 4: if it cannot finish today, make it a ticket

Live chat is for quick conversations. Anything that needs a refund check, a delivery lookup or a call back belongs in a ticket. LiveChatBot tickets move between open, pending and solved, can have owners, and give customers a page to follow progress without logging in. See how to turn a chat into a support ticket and the ticketing system overview.

Rule 5: review ten chats every week

Sit together for fifteen minutes and read ten real chats. Look for collisions, slow starts and answers the bot got wrong. Add missing answers to your saved replies so everyone answers alike.

Together these five rules turn a chatbot with shared inbox visibility into real teamwork, with no extra software.

Example

An illustrative week with three people and one inbox

This example is made up to show the rules at work.

A small tutoring centre has three people on chat: Asha at the front desk, Ravi who handles fees, and the owner. On Monday morning a parent asks about a batch timing. The bot gives the standard answer. Asha reads it, adds that a seat is free, and owns the chat. Ravi sees it and leaves it alone.

At noon another parent asks for a fee refund. Asha sends a first reply, says she is passing the chat to Ravi, and tells him in the team group. Ravi turns the chat into a ticket with himself as owner because the bank check will take until tomorrow.

On Friday the three of them read ten chats together. They spot two answers the bot got slightly wrong and add them to the saved replies. Nobody was double-booked, nobody waited, and the whole routine took no new software.

Setup

Set up the shared inbox for a team in LiveChatBot

The inbox is shared by default: everyone on the account sees conversations, and there are no per-seat charges, so adding teammates costs nothing extra.

  1. Invite your team and have each person install the Android app. iPhone users answer from a browser, as there is no iOS team app.
  2. Choose an alert tone for each person, per website, so alerts are distinct.
  3. Set opening hours so the away form covers the hours nobody is there.
  4. Load shared saved replies with {name}.
  5. Write your five house rules on one page and pin it where the team works.

Also keep the bot useful. The AI Agent and keyword bot answer first, and your team steps in. Read how the AI Agent hands over.

Honest gaps

What a chatbot with shared inbox here does not do

Be clear on the limits so you plan around them.

  • No staff roles or permissions. Everyone on the account has the same access.
  • No audit logs or single sign-on.
  • No WhatsApp inbox; WhatsApp conversations stay in WhatsApp, with a button card on your site.
  • No native CRM apps. Zapier, webhooks (ticket.created, ticket.solved) and the REST API connect other tools.
  • No pre-chat form.

If you need automatic routing between departments or strict permissions, this is not the right tool. For small teams of two to ten, house rules do the same job for free.

Next step

Agree the rules this week

Gather everyone who answers chats for fifteen minutes, read the five rules aloud, change anything that does not fit, and start. Revisit after a month. Sign up free at livechatbot.in and see pricing when traffic grows.

Frequently asked questions

What is a chatbot with shared inbox?

A bot answers first, and every conversation appears in one inbox that your whole team can see and reply from.

How do I stop two agents answering the same chat?

Agree that the first person to reply owns the chat, and hand off in words when passing it on.

Do I pay for each team member?

No. LiveChatBot has no per-seat charges.

Can chats be assigned to people?

Tickets can have owners. For live chats, use the first-reply-owns-it rule.

Can my team use phones?

Yes, with the Android app. iPhone users answer from a browser.

Keep reading

Related guides

📘

Chatbot With Agent Dashboard: A Screen-by-Screen Tour of What Your Team Sees, and the One Setting to Change on Each (Free Dashboard Glossary)

Read the guide →

🧭

AI Chatbot With Live Agent Transfer: Plan Who Catches the Chat at 3 pm, 9 pm and 3 am, Because the Transfer Only Works if Someone Is There

Read the guide →

🛠️

Lead Qualification Chatbot Software: Three Questions That Separate Buyers From Browsers, Written for Four Business Types (Free Copy-Paste Questions)

Read the guide →

Give your team one inbox

Bot first, people second, no per-seat charges. Start free on two websites at livechatbot.in.