Shared Inbox for Small Business: One Place for Every Customer Message

A customer messages your business on Instagram on Monday morning. On Tuesday they email the same question because nobody answered. On Wednesday they text the number on your website. By Thursday, three people on your team have each seen one of those messages, each assumed someone else had it, and the customer has quietly gone to a competitor. Nothing went wrong in any single place. The failure was in the gaps between them.

This is the everyday cost of scattered messages, and it grows with every channel you add. This guide explains what a shared inbox actually fixes, how to set one up so it stays tidy, how to assign and answer messages without sounding robotic, what response times are reasonable on each channel, and which numbers tell you whether it is working.

Key takeaways

What scattered messages really cost

Small businesses rarely decide to be reachable in seven places. It happens gradually. Someone opens a Facebook page, a customer finds the Google listing and taps the message button, the website gets a chat box, a WhatsApp number goes on the van, and the owner’s mobile ends up handling texts. Each decision made sense on its own day. Together they create several inboxes that nobody checks on the same schedule.

The costs show up in a few predictable ways.

• Missed messages. A direct message on a social app sits unread because the person who has the login is on a job site. The customer does not know that. They only know they were ignored.
• Duplicate replies. Two people answer the same enquiry, sometimes with different prices or different availability. That looks disorganised and can create an expectation you then have to walk back.
• Lost context. The customer explained their problem on one channel and you reply on another with no idea what was said. They have to start again, which is the single most irritating thing about contacting a business.
• Personal-phone dependence. When customer messages live on one employee’s phone, that knowledge leaves with them on holiday, sick leave or resignation.

None of this needs a large team to cause trouble. Two people sharing four channels is enough.

What a shared inbox fixes

A shared inbox pulls messages from every channel into one list of conversations that the whole team can see. The idea is simple, but four specific problems go away when you do it.

Ownership

Every conversation can have a named person responsible for it, which removes most “I thought you had it” failures. Unassigned conversations are visible as a group.

History

All messages from a customer sit in one thread, whichever channel they arrived on. When a person reappears two weeks later, you see what was said before and what was promised. This matters most for the questions that span time: quotes, bookings, deliveries and complaints.

No duplicate replies

When a teammate has already replied, the thread shows it, so the customer gets one coherent answer.

Handover

Shifts end, people go on leave, and some questions belong to someone else. A shared inbox makes handover a reassignment rather than a forwarded screenshot with a note attached. The next person sees the full thread and can carry on in the same voice.

Which channels belong in the inbox

The first instinct is to connect everything. Resist it for a moment. Each channel you offer is a promise that you will answer there, and the promise is only worth making if you can keep it.

Start by counting last month’s enquiries by channel. The channels that matter are the ones that already bring real conversations; one with two messages a month and no one watching is a liability.

A reasonable rule: add a channel when you can name who will watch it and what a normal reply time will be. Remove or hide one when you have consistently failed to meet that standard.

A status workflow that stays simple

Statuses exist to answer one question at a glance: does this conversation need anything from us right now? The fewer there are, the more reliably people update them.

• Open. The customer is waiting for something from you, or the conversation is active. This is your working list.
• Snoozed. You have done what you can for now and are waiting for something — a delivery, a customer reply, a date next week. Snoozing hides the thread until it matters again, so it does not clutter the open list and does not get forgotten.
• Resolved. The question is answered and nothing is pending. If the customer writes again, the conversation can reopen with its history intact.

Two further states are housekeeping rather than workflow: archived for conversations you want out of sight but not deleted, and spam for the messages that should never have reached a person. Keep them out of daily decisions.

Assigning conversations: three approaches and when each fits

Assignment answers who replies. There are three common ways to decide, and the right one depends on how your team is organised rather than how big it is.

Round robin is the easiest default for generalists, but it ignores skill and availability, so keep the group to people who are at a screen during working hours. Channel-based assignment suits people who specialise by channel; name a backup for each. Keyword rules route by what the customer says and are unreliable for vague topics, so start with a handful of clear words and tighten them after a week.

Canned responses without the robot voice

Canned responses are saved replies you can insert in a few keystrokes. Used well, they save time on the questions you answer every week — opening hours, how booking works, what a quote includes. Used badly, they produce replies that visibly ignore what the customer asked. The difference is in how they are written and when they are used.

What a useful canned response contains

• A clear title. Name it by what it answers, such as “Opening hours” or “Quote process”, so people can find it quickly.
• A short shortcut. A few easy-to-type characters let you insert the reply without leaving the keyboard.
• Merge tags. Placeholders for details such as the customer’s name fill in automatically, which keeps the reply personal without extra typing.
• A category. Grouping replies — sales, scheduling, billing — stops the list becoming a wall of titles as it grows.

Seven rules for writing ones people will actually use

• Answer first, greet second. If the customer asked whether you work Saturdays, the first sentence should say yes or no.
• Write like a person at your business. Read it aloud. If you would not say it across a counter, rewrite it.
• Leave a gap for the specific. End with a line you complete by hand that refers to the customer’s own detail. That one sentence is what separates a template from a form letter.
• Avoid canned apologies. “We apologise for any inconvenience” reads as a reflex. Say what actually went wrong or do not apologise.

Labels: a light layer of organisation

Statuses tell you what to do; labels tell you what a conversation is about. A small set of labels — for example sales enquiry, booking, complaint, supplier and feedback — makes it possible to filter the inbox, spot patterns and hand a topic to the right person.

Keep the list short, label by topic rather than by person or urgency, and agree the meanings so that one person’s “sales” is not another’s “lead”. If a third of conversations carry the same label, that is a finding: perhaps your website should answer it first.

Response-time targets by channel

Customers do not measure your reply time against a stopwatch. They measure it against the channel they used. A text that goes unanswered for a day feels worse than an email that goes unanswered for the same day, because texting implies immediacy.

The figures below are starting points for a small team, not industry standards. Adjust them to your business, then publish them to your team and keep them honest.

Setting expectations after hours

You do not have to answer at midnight, but you should not leave people guessing. State your reply hours on your site and profiles, clear the overnight queue oldest first each morning, and promise only what you will actually do.

Privacy and consent when you text customers

Messaging channels feel casual, but the rules around them are not. Rules differ by country and, in some places, by state or province, so treat the following as principles to check rather than legal advice.

• Have a basis for contacting people. A customer who texts you first and asks a question has opened a conversation. Sending promotional texts to a list you collected for another reason is a different matter.
• Make opting out easy. If someone says stop, stop, and make sure everyone on the team knows that is a request to honour rather than an invitation to persuade.
• Record consent. Know where and when a person agreed to be messaged, because you may need to show it.
• Check each platform’s own rules. Some messaging platforms restrict when a business may start a conversation or require approved templates outside a recent customer message.

Measuring whether it is working

You do not need a dashboard of twenty metrics. Three numbers are enough to run a small team, and each tells you something different.

First response time

How long a customer waits for the first human reply. It is the number customers feel most. Look at the typical value and at the slow end, because a good average can hide a handful of people who waited two days. Break it down by channel so you can see where the target is slipping.

Unresolved age

How old your open conversations are. A short open list full of old conversations is a sign that things are being acknowledged and abandoned. If the oldest open thread is weeks old, either it should be snoozed or resolved, or something is stuck and needs a person.

Volume by channel

How many conversations each channel produces, and when. It shows where to put your fastest replies and which channels to add or retire.

Common mistakes

Switching on too many channels at once

A new inbox makes it feel cheap to add every channel in an afternoon. The cost shows up later, when the volume arrives and nobody has agreed who answers what. Add one channel at a time, run it for a couple of weeks and only then add the next.

Canned replies that ignore the question

The quickest way to make a customer feel processed is to send a saved reply that answers a different question. Read the message before you reach for a shortcut, every time.

How Scalry handles this

Scalry’s conversations feature brings your messages into one inbox. Channels supported include SMS, email, WhatsApp, Facebook Messenger, Instagram DMs, website live chat, Google Business Messages, voice calls and LinkedIn. Which channels are available depends on your plan and on what you have connected, so check what is included before you plan around a particular one.

Each conversation can be open, snoozed, resolved, archived or marked as spam, and you can send replies directly from the inbox rather than switching to each platform. Labels let you categorise conversations by topic.

Canned responses have a title, a shortcut and merge tags, and are grouped by category, so a frequently used reply is a few keystrokes away and still fills in the customer’s details. Assignment rules come in three types — round robin, channel based and keyword match — and distribute conversations across the team members you choose. For your own website, there is a live chat widget that feeds the same inbox as everything else.

Because conversations sit in the same workspace as your contacts and the rest of your customer records, a reply can be written with the history in view. That is the practical benefit: not a cleverer inbox, but fewer gaps for customers to fall through. The habits in this guide — owners, small status sets, honest response targets — are still yours to set.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Where do customers actually write to us? Count last month’s enquiries by channel before deciding what to connect.
• Who owns each conversation? If the answer is “whoever sees it first”, messages will be missed.
• Who covers when the owner is away? A channel with no backup is a gap waiting to happen.
• What reply time do we promise on each channel, and do we meet it?
• Which routine questions deserve a canned response? Look for anything you have typed more than five times this month.
• What happens to a conversation that matches no rule? Name the person who checks the leftovers.

If you cannot answer the first three, you are not ready to choose between Scalry and your current messaging setup yet — you are still deciding what you need, which is a cheaper problem to solve first.

A two-week plan to get started

Days 1 to 3: list every place customers can message you, count last month’s enquiries by channel and choose what earns a place in the inbox. Days 4 to 6: pick three statuses, six to eight labels, one assignment method and a backup for each person, and write your response targets down. Days 7 to 9: draft your five most common canned replies. Days 10 to 12: go live with the one or two busiest channels and watch every conversation. Days 13 and 14: review first response time, open-list age and volume by channel, then decide whether to add the next channel.

Frequently asked questions

What is a shared inbox for a small business?

A shared inbox collects customer messages from several channels, such as email, SMS, social messaging and website chat, into one list that your whole team can see. Each conversation has an owner and a status, so messages are not missed or answered twice, and anyone can see the history before they reply.

Which channels should I connect first?

Start with the channels that already bring you real conversations. Count last month's enquiries by channel and begin with the top one or two. Add others one at a time, only when you can name who will watch the channel and how quickly they will reply.

How should I assign conversations to my team?

Use round robin when everyone can answer most questions and you want an even load. Use channel-based assignment when people specialise by channel. Use keyword matching when topics have distinct vocabulary, such as billing or bookings. Whichever you pick, name someone to check conversations that match nothing.

Do canned responses make replies sound robotic?

Only when they are used carelessly. Answer the question in the first sentence, keep the reply short, use merge tags for details like the customer's name and leave room for one personal line. Avoid them for complaints or anything emotional, and review them regularly so they stay accurate.

How fast should I reply on each channel?

There is no universal standard, but customers expect speed to match the channel. Aim for minutes on live chat, around an hour on SMS and WhatsApp, a couple of hours on social and Google messages, and within one business day for email. Publish your working hours so people know what to expect after hours.

Do I need permission to text customers?

Often yes, and the rules vary by country and region. A customer who messages you first has started a conversation, but sending promotional texts needs a proper basis for contact and a clear way to opt out. Record when and how consent was given, and check local requirements before automating anything.

What should I measure in a shared inbox?

Three numbers are enough for a small team: first response time, which is how long customers wait for the first human reply; unresolved age, which is how old your open conversations are; and volume by channel, which shows where enquiries come from and when. Review them weekly and look at the slowest cases.