A customer texts your business line: “Can someone come Thursday instead of Wednesday?” Two people see it. Dana replies “Sure, Thursday at 10 works.” Two minutes later, Marcus replies “Thursday is full, but we can do Friday.” The customer is now confused, and both of your employees feel like they did the right thing.
The opposite failure is quieter. Everyone sees the message, everyone assumes someone else will handle it, and nobody does. The customer waits a day, then books with someone else.
Both problems come from the same place: a shared inbox without rules. Shared access is the easy part. Shared responsibility needs a few explicit agreements. This article lays them out and ends with a one-page policy you can adapt.
Rule 1: Every conversation has exactly one owner
This is the rule that prevents most problems. At any moment, each conversation belongs to one named person. Not “sales,” not “the front desk,” one person.
The owner:
- Sends the replies.
- Sets and keeps the next step.
- Updates the contact and deal.
- Hands the conversation off, with a note, if someone else should take it.
Everyone else can read the conversation and add internal notes. They don’t reply to the customer unless the owner asks them to or the conversation is reassigned.
How ownership gets set
Decide this in advance so nobody has to think about it in the moment:
| Situation | Who owns it |
|---|---|
| New lead, normal volume | Whoever is “on new leads” today |
| New lead, high volume | Next person in rotation |
| Returning customer | The person who last worked with them |
| Specialized request | The person with that skill or language |
| Owner is out | Their designated backup, set before they leave |
If you use software, this is usually called conversation assignment. If you don’t, a whiteboard and a daily “who’s on new leads” message in your team chat can work surprisingly well for a while.
Unassigned is a status, not a resting place
New conversations will sometimes arrive unassigned. That’s fine for a few minutes. Make it someone’s explicit job to check unassigned conversations several times a day, and treat anything sitting there for an hour as a problem.
Rule 2: Use a small set of statuses, and use them consistently
Statuses tell the team what each conversation needs, at a glance. Too many and nobody uses them correctly. Four or five is plenty:
- Open — we owe a reply. The customer is waiting on us.
- Waiting on customer. We replied; the ball is in their court. Has a follow-up date.
- Snoozed until [date]. Nothing to do until a specific date (“call back after their HOA meeting”).
- Closed. The conversation’s purpose is done. A new customer message reopens it.
The most important distinction is the first two. “We owe a reply” and “they owe a reply” look the same in a busy inbox unless someone marks the difference. When they’re separate, your morning check is easy: work through everything in “Open,” oldest first.
Avoid statuses that describe feelings or vague intentions, like “Hot” or “Working on it.” Those belong on the deal, not the conversation.
Rule 3: Handoffs happen with a note
Conversations change hands for good reasons: a lead needs the estimator, a customer prefers Spanish, the owner is going on vacation. Bad handoffs are where context gets lost and customers have to repeat themselves.
A good handoff has three parts:
- Reassign the conversation, so ownership is clear.
- Leave an internal note with what the next person needs.
- Tell the customer if the person they’re talking to is changing.
A useful handoff note:
@Marcus passing this to you for the site visit. Bathroom-only remodel, tub-to-shower conversion. She’s flexible on dates but prefers mornings. Budget conversation went fine; she’s comparing two other contractors. Photos are in the thread from Tuesday.
And the customer-facing message:
Hi Ana, I’m handing you over to Marcus, who leads our site visits. He’ll be in touch today to set up a time. You’re in good hands!
The test: could the new owner reply well without asking the old owner anything? If not, the note isn’t done.
Rule 4: Internal notes are for the team, never for the customer
Internal notes let the team talk about a conversation inside the conversation, without the customer seeing it. They replace side chats in a separate app, where context gets lost.
Use them for:
- Handoff context.
- Questions for a colleague, with an @mention: “@Dan, can we do a custom vanity size?”
- Things you learned that aren’t in the messages: “Spoke by phone, she’s decided on the walk-in shower.”
- Warnings: “Do not offer a discount; already discussed.”
Two rules keep notes safe:
- Double-check before sending. Internal notes and customer replies should look clearly different in whatever tool you use. If they don’t, slow down.
- Write notes as if the customer might see them one day. Keep them professional and factual.
Rule 5: Decide what happens after hours
After-hours is where shared inboxes most often fail, because “someone will see it” becomes “nobody saw it.”
Decide, in writing:
- What hours are covered, and by whom.
- What the customer hears outside those hours. An honest auto-acknowledgment with a time (“We’ll reply by 9 AM tomorrow”) beats silence.
- Who checks first thing in the morning, and how they work through the overnight queue.
- What counts as urgent, and whether anyone is on call for it.
Avoid the pattern where the owner answers from bed at 11 PM on some nights and not others. It trains customers to expect late-night replies and burns out the person doing it. Our post on lead response time goes into setting realistic business-hours and after-hours targets.
Rule 6: No side channels for business conversations
If a rep moves a customer to their personal WhatsApp “because it’s easier,” the shared inbox stops being shared. Make the rule explicit: business conversations happen on business lines. If a customer messages a personal number, the rep redirects them politely:
Thanks for reaching out! So the whole team can help you, could you message us at our main number, (312) 555-0100? I’ll pick it up from there.
Sample one-page inbox policy
Adapt this to your team. Keep it to one page so people actually read it.
Team inbox policy
Ownership. Every conversation has one owner. The owner replies, sets the next step, and updates the contact and deal. Others read and add internal notes but don’t reply unless the conversation is reassigned to them.
New conversations. The person on new leads today (posted in team chat each morning) owns new conversations. Unassigned conversations are checked at 9 AM, 12 PM, 3 PM, and 5 PM.
Response targets. During business hours (Mon–Fri 8 AM–6 PM), conversations marked Open get a useful reply within 30 minutes. Overnight messages get a reply by 9:30 AM.
Statuses. Open (we owe a reply), Waiting on customer (with a follow-up date), Snoozed (with a date), Closed. Nothing sits in Open without a reason.
Handoffs. Reassign, add an internal note with context, and tell the customer who will take over. The new owner should never have to ask what’s going on.
Internal notes. Use notes and @mentions for team discussion. Write them professionally. Check before sending that you’re in note mode.
Time off. Before leaving for a day or more, reassign your open conversations and pending follow-ups to your backup.
After hours. An automatic message tells customers when we’ll reply. The morning person works the overnight queue oldest-first.
Business lines only. No business conversations on personal numbers or personal accounts.
Weekly review. Every Friday, the manager checks for conversations without an owner, Open conversations older than a day, and Waiting conversations without a follow-up date.
Rolling it out
Introduce the rules in one short meeting, not an email. Walk through two real examples from the past month: a double reply and a dropped conversation. Then agree on the policy and start the next morning. Review it after two weeks and adjust what isn’t working.
If you’re deciding whether a shared inbox is enough on its own, our explainer on what a messaging CRM is covers where a shared inbox stops and a CRM starts. The customer support team page shows how the same rules apply to service conversations.
Where inChat fits
inChat is a messaging CRM in development for small teams. Its planned launch scope includes a shared team inbox with conversation statuses, one owner per conversation, internal notes and @mentions. It’s in early access; you can see how conversation assignment is designed to work.