A shared inbox for WhatsApp, Instagram and Messenger

A shared inbox puts every conversation from WhatsApp, Instagram, Messenger and email in one place, tied to one customer record, so a team can see who replied, who owns it and what was said. Add an agent that answers first and hands over to a person when it cannot, and you get speed without losing control.

Most small teams grow their messaging by accident. A phone with WhatsApp Business, an Instagram login shared in a chat, a Facebook Page that one person checks on Sundays, and an email inbox. Each works alone. Together they leak leads, because a message on one app waits while the team is busy in another. This post explains what a shared inbox is, what it fixes and what to look for, with notes on how Sellinger handles it.

What does a shared inbox fix?

Four things that hurt small sales and support teams.

1. Missed messages. A message on a channel nobody opened today waits. The customer moves on.
2. Double answers. Two colleagues reply to the same person with different information.
3. Lost history. A customer who wrote on Instagram on Monday and WhatsApp on Friday looks like two people.
4. No owner. Nobody knows whose turn it is, so the thread waits for the next meeting.

A shared inbox answers each: one list of conversations, an owner on each, one customer record and a visible status.

What belongs in the record?

For a sales team, a conversation is more than text. The useful record for each person holds:

Sellinger keeps the full conversation history across channels on each lead, in a built in CRM with contacts and deals and a two way sync with HubSpot. Our post on what an AI CRM is goes through why the record, not the chat window, is the point.

Which channels does it cover?

Sellinger's outreach channels are LinkedIn, email, WhatsApp, Instagram and live chat. Facebook Messenger comes in through a connected Page. For WhatsApp, the connection runs through your own WhatsApp account, and WhatsApp itself limits outbound messaging, so the agent mainly serves people who write first. That fits an inbox: it is where inbound messages land and get answered.

Be honest about the limits of any shared inbox on a messaging app. The platform sets what is possible, such as the window in which you may message someone who commented, and it can change its rules. Do not build a process that relies on one rule staying the same.

How should an agent and a person share the inbox?

A pure bot inbox loses the thread when the question gets hard. A pure human inbox is slow at night. The pattern that works is a split.

• The agent answers first, from your knowledge base and persona, in the customer's language.
• A person takes over for anything sensitive: pricing talks, complaints, groups, anyone you already know.
• The agent stops on its own when it cannot answer, and flags the lead with a named reason.

In Sellinger, a person clicks Takeover on the lead and the agent stops replying to that lead; Release or Hand back to agent returns it. When the agent has been paused, it picks up from the full history, including what you wrote. See take over a conversation. A campaign can also run in approval mode, where every message waits for a person, which suits the first weeks. The page on approvals and human review explains both.

Automatic replies from helpdesks and no reply senders never count as a human reply. They are marked as machine mail, the agent does not answer them and the lead is sent to a person with a named reason. That keeps an out of office message from starting a conversation with a robot.

What does it look like in a real business?

Hotel Pirin, a 68 room hotel in Bansko owned by a Sellinger co-founder, ran two agents. One wrote cold email to companies for group business. The other, a reservations agent, answered guests by email and, from 24 September, on Facebook Messenger and WhatsApp, in the guest's language. It quoted from the hotel's live availability system or, when that check failed, from the official rate card.

The result for guests: a median first reply of 41 seconds over 54 guest inquiries, and a quote rate that rose from 50% to 92% after a rule to quote as soon as it had dates and party size. The result for staff: groups, agencies and Booking.com messages went to people by design, and people closed most bookings. The agent created no reservation itself. The inbox was fast at the first answer and handed the rest to a person. Read the full case study. WhatsApp there ran through a connected WhatsApp account and was used only to answer guests who wrote first.

What should you set up first?

1. Connect the channels you already use. WhatsApp, Instagram, a Facebook Page, your mailbox. Do not add new ones yet.
2. Write the knowledge base. Prices you may state, opening hours, policies and what the agent must never promise.
3. Set the persona and tone. Formal or friendly, and which languages to answer in.
4. Start in approval mode. Read the first 20 to 50 replies.
5. Decide what goes to a person. Name the topics: complaints, groups, big orders, refunds.
6. Check it weekly. Read ten threads, and fix the rules where the agent was wrong.

Our post on what a good AI reply looks like gives a standard to read those threads against.

How do you know the inbox is working?

Three plain measures are enough for a small team, and none needs a dashboard.

• Time to first reply. Read ten conversations a week and note how long the first answer took. Hotel Pirin tracked this as a median, 41 seconds for guests, which is a number you can only reach with an agent answering first.
• Conversations waiting on you. At the end of each day, count the threads where the customer wrote last. The number should be near zero.
• Handovers and their reasons. Every time the agent stops, the lead carries a named reason. If the same reason repeats, such as a price it has no answer for, add the answer to the knowledge base. The inbox then needs fewer people over time without losing control.

Our post on WhatsApp AI agent handover covers when the agent should step back on that channel.

What should you avoid?

• A shared login passed around a chat. Use accounts with named members, so you know who answered. See the help page on teams and members.
• No rule for the night. Decide what the agent answers when nobody is awake and what it holds for morning.
• Mixing personal and business messages. Facebook offers choices for personal messages from friends: flag them, hold them back or treat everything as business. Pick one.
• Treating the inbox as a help desk. A shared inbox is a conversation view, not a ticket system. If you need queues, SLAs and macros, say so when you choose a tool.

A selection checklist

• [ ] Every channel I use lands in one list.
• [ ] Each conversation has one customer record and one owner.
• [ ] A person can take over, and the agent stays quiet until released.
• [ ] The agent stops by itself on questions it cannot answer.
• [ ] Machine mail does not start conversations.
• [ ] I can read the full history before I answer.