A shared inbox tends to fail quietly. Two people answer the same enquiry with different prices, or nobody answers because everyone assumed a colleague had it. Software can show who holds what, but the team still needs a few rules that survive a busy Friday. What follows is a working agreement you can adapt in an afternoon.

One conversation, one named owner

A team name is not an owner. Each open conversation belongs to one person, even when several people contribute. The owner is the person responsible for making sure the customer gets the next reply, which is different from being the person who knows the answer.

Write down three decisions:

  • Who assigns. Name one triage person per shift. The role can rotate, but at any moment someone should be accountable for the unassigned queue.
  • When a conversation is claimed. Assign before you start typing, so a colleague does not draft the same reply.
  • When ownership ends. Agree what resolved means. Waiting on the customer is still owned; waiting on the warehouse is still owned.

Keep ownership when you only need input. Ask the colleague in a private note and reply yourself. Reassign when someone else will send the next reply, and leave a line saying why, so the new owner never has to reconstruct the story.

Keep notes and replies apart

A private note is written for colleagues and a reply is written for the customer. Sending the first as the second is the mistake people remember, which is why help desks mark the difference clearly. Zendesk, for example, labels the two composer modes Public reply and Internal note, and shows private comments on a yellow background. Whatever tool you use, teach new starters to check the mode before they press send.

Rules for notes:

  • Record facts and the next step. Leave out opinions about the customer. Kenya's Data Protection Act gives people a right to access personal data held about them, and the 2021 General Regulations set seven days to comply with an access request. A note about a named customer may fall within that, so write each one as though the customer could read it.
  • Keep sensitive identifiers out. WhatsApp's Business Messaging Policy tells businesses not to ask people for full card numbers, financial account numbers or personal ID card numbers. If one arrives anyway, do not copy it into a note.
  • Date any promise. "Refund approved by finance on Tuesday" helps the next person. "Should be fine" does not.

Rules for replies are shorter. Say what happens next and when. If you cannot give a date, say when you will update the customer, then do that.

Handovers between shifts

Hospitals have worked on this problem for years. One structured handover used there, I-PASS, covers illness severity, patient information, an action list, situational awareness with contingency plans, and synthesis by the receiver. The last step matters most for a support team: the person taking over says the plan back. Adapted for an inbox, each live conversation gets a short private note:

  1. Urgency. Is anything due today, and is the customer upset?
  2. Summary. One or two lines on what has happened so far.
  3. Actions. What is outstanding, who is doing it, and by when.
  4. If this, then that. For example: if the supplier confirms, send the delivery date; if not, call the customer before noon.
  5. Read-back. The incoming owner confirms they have read the note and reassigns the conversation to themselves.

Limit handover notes to conversations with an open promise or a deadline. If everything gets a note, nobody reads them. Give the handover ten protected minutes on the rota, and treat any unassigned conversation at shift end as the outgoing triage person's problem.

Teach the shift the platform clocks

Some channels limit how long you can reply freely, and an overnight gap can cross that limit. As of 6 November 2026, Meta's documentation says:

  • WhatsApp: a 24-hour customer service window opens and resets with each customer message. Once it closes, you can only send approved templates.
  • Messenger and Instagram: the standard messaging window lasts 24 hours for most user actions. The Human Agent tag allows manual replies within a separate 7-day period.

These rules change, so confirm them from time to time. The practical point holds anyway: if a customer's last WhatsApp message arrives on Friday afternoon, the window will close before Monday. Outgoing shifts should flag those conversations, and the team should keep a suitable approved template ready. The WhatsApp and SMS campaign guide explains how templates are reviewed.

When a customer changes channel

Customers do not organise themselves around your channels. Nielsen Norman Group's omnichannel research puts it plainly: "To customers, you are one company." One of its examples is a subscriber whose credit and schedule change, agreed by phone, did not appear in her online account, which cost her another call and some trust in the company.

Four rules cover most cases:

  • Check history before replying. When a new message arrives, look for a recent conversation with the same contact on any channel.
  • Keep the first owner. If the issue is already in hand, link it to that owner instead of opening a second thread.
  • Confirm identity before sharing account details. A matching name on Instagram proves very little.
  • Carry opt-outs everywhere. WhatsApp's policy requires businesses to respect opt-out requests made on or off WhatsApp, so "stop messaging me" said on a call counts. Record it on the contact the same day. The consent guide for Kenya covers what to keep.

Check the agreement weekly

Pick ten closed conversations each week. Did each have one owner at every point? Was there a handover note where one was needed? Did the customer repeat themselves? Tag why each customer got in touch as well. In a Nielsen Norman Group diary study, missing or confusing information was the most frequent reason people contacted an organisation, so the best fix may be a clearer web page or message.

Where Jadility fits

Jadility's shared team inbox lets you assign conversations, leave private notes and reply together across WhatsApp, Facebook Messenger, Instagram, email, a website chat widget and SMS. Contacts and segments support follow-ups. The working agreement stays yours. See the omnichannel inbox page, or talk to us about how your team works today.

Sources

Share