Most missed messages are not a tooling problem. Nobody was sure the message was theirs, so everyone left it for someone else. A shared inbox only fixes that if the team agrees on a few rules first.
This is the routine we would set up for a team of two to ten people. The screens are covered in the Inbox itself, so this post is about the habits around them. It assumes you have the Inbox on your plan and your channels connected. If you are still deciding whether it covers your networks, each tab in the Inbox lists the networks it reads from.
Decide what each action means
The Inbox gives you five ways to handle a conversation: assign it, write an internal note, snooze it, label it, archive it. Teams get into trouble when two of those mean the same thing to different people. Agree on this once:
| Situation | Do this | Why not something else |
|---|---|---|
| A message is for a specific person, such as the one who ran the promotion | Assign it to them | A label says what a thing is. It does not make anyone responsible. |
| You answered, but the next step belongs to someone else | Internal note, then assign | The note carries the context so the next person does not re-ask the customer. |
| You cannot answer until something happens, like a refund check or a Monday restock | Snooze to the time you will know | It leaves your Open list clear and comes back by itself. |
| It is finished | Archive | Delete only removes our copy. The thread stays on the network. |
| You want to find this kind of message later | Label it | Labels are for filtering, not for ownership. |
One rule keeps the table honest: every Open conversation has an owner. If the Open list holds unassigned rows at the end of the day, the day is not finished.
A worked week
A three person shop: Maya runs the brand, Dev does fulfilment, Sam works part time on Tuesdays and Thursdays. They get Instagram DMs, Facebook Messenger and Google reviews.
Monday, 9:00. Maya opens the Inbox and filters to Open. Six new conversations. Two are order questions, so she assigns them to Dev. One is a press enquiry: she labels it “press” and keeps it. Three are simple, so she answers them from saved replies and archives them.
Monday, 9:20. An Instagram customer asks if a sold out item is coming back. Maya does not know. She snoozes the conversation until Monday 9:00 next week, after the supplier call, and leaves an internal note: “Ask supplier about restock date, tell her the answer.” Nothing about this is visible to the customer.
Tuesday. Dev opens Assigned to me and has the two order questions in front of him, with nothing else to wade through. One needs a tracking link. He replies, archives it, and puts the other on a three hour snooze while he waits for the courier to reply.
Wednesday. A one star Google review arrives. Maya assigns it to herself, writes the reply, and the Inbox posts it as the public reply to that review. She adds an internal note with what happened, because Sam will see the same customer on Thursday.
Thursday. Sam, who was off Wednesday, searches the customer’s name and finds the whole history including the note. No one had to forward a screenshot.
The following Monday. The snoozed restock conversation returns to Open at 9:00. Maya has the answer and replies.
The shape matters more than the details: one pass in the morning to assign and clear, each person works their own queue, and snooze handles the waiting.
Mistakes that leave people waiting
Using snooze as a to-do list. Snooze is for waiting on an event or a time. If you snooze everything you cannot answer today, the Open list looks clean and the Snoozed list becomes the real backlog. Check Snoozed once a day.
Replying to Messenger or Instagram after the window closes. Meta lets you answer a direct message for 24 hours after the person’s last message. After that the composer closes and says so. That is Meta’s rule, not a setting, so triage DMs on those two networks first. Reviews and comments are not subject to it.
Expecting every network to arrive. Direct messages come in from Facebook, Instagram, X, Bluesky, Mastodon and Telegram, and reviews from Google Business Profile and Facebook. If a customer writes to you on LinkedIn, YouTube, TikTok or Pinterest, that message stays on the network and you answer it there.
Forgetting X is opt in. X charges for every read, so messages from an X account stay off until you switch on “Sync messages” for that account. If an X inbox looks empty, check that first.
Not reconnecting an old channel. Messenger and Instagram messages need a messaging permission that is separate from the publishing one. A channel connected before that permission was requested has to be reconnected before its messages show up.
Trusting a saved reply without reading it. Variables such as {{first_name}} fill in when you insert the reply, and one that is not recognised stays exactly as typed. The text lands in the composer for you to edit, so read it before you send. Keep replies to what is true for every customer, and let the person write the sentence that is about them.
Treating Delete as Archive. Delete removes the conversation from BulkPublish only. The next message from that person starts a fresh one. Archive is the way to put something away.
Writing the private part in the reply box. Switch the composer from Reply to Internal note before you type anything sensitive. Notes are never sent to the person.
Saved replies worth writing first
Start with the questions you already answer weekly. Four that most small teams need:
- Shipping times and how to track an order.
- Opening hours and where to find you.
- Returns and refunds, with the one honest sentence about the limits.
- A thank you for a good review that does not read like a template.
Name them for how you will search for them, not for what they say. “Returns: unopened” beats “Reply 3”. Each reply can be up to 4,000 characters and your workspace can keep 200, which is far more than you will use.
A five minute weekly check
Once a week, whoever leads the team does this:
- Filter to Open and confirm nothing is unassigned.
- Open Snoozed and check that nothing is parked there that should have been answered by now.
- Scan the labels you use. If one is never filtered by, retire it.
- Look at saved replies you did not use this month and edit or remove them.
- Check that every channel still shows messages. A quiet channel can mean a quiet week, or an expired connection.
When a shared inbox is the wrong answer
If one person handles all messages and they live in a single network’s own app, the native app is fine. If you want automatic replies, nothing here sends on your behalf: every reply is something a person typed. And if most of your inbound is on a network we cannot read, the Inbox will cover only part of the picture.
Plans
The Inbox is on the Pro and Business plans, and Free and Lifetime workspaces do not have it. Pro has room for 3 people in a workspace and Business for 10, so a solo Pro account will use the notes, snooze and labels but not much of the assigning. See pricing for the plans side by side.
Related reading: reply to comments on your published posts, invite team members and set their roles, leave internal notes on posts, organize posts with labels, and the post approval workflow.
BulkPublish supports 15 platforms: Facebook, Instagram, TikTok, YouTube, X, Threads, Bluesky, Pinterest, Google Business Profile, LinkedIn, Mastodon, Discord, Telegram, Tumblr and Snapchat.
- Inbox: Free: not included. Pro: included. Business: included.
- Team members per workspace: Pro: 3. Business: 10.
- Channels: Free: 3 (1 per platform). Pro: 30 (2 per platform). Business: 75 (5 per platform).
- Pro $13.99/mo ($11.89/mo yearly). Business $39.99/mo ($33.99/mo yearly). Extra channel slots $2.99/mo each.
The short version
Give every open conversation an owner, use snooze for waiting and archive for done, keep private context in notes, and do a short weekly check. The software handles the list. The rules are what stop messages being dropped.
Start free and connect your channels, then upgrade when you want the Inbox.