Imagine a customer asking whether a repair is ready. At 10:05, one colleague says yes. At 10:08, another asks for the repair number. Both are trying to help. The customer now has to work out which answer to trust.
A shared inbox needs a shared working rule: one visible owner per conversation, a clear distinction between internal notes and customer replies, and a check for unassigned work. Giving everyone access is only the first part.
The idea, at a glance
Shared access, clear responsibility.
- 01Receive
Check new and unassigned work.
- 02Claim
Make the conversation owner visible.
- 03Collaborate
Keep internal advice separate from replies.
- 04Hand over
Transfer the next step with acceptance.
Choose access that can be removed
Give people their own sign-in and the access their role needs. Gmail's delegation documentation explains how delegated email access can be granted and removed. Check the controls and limits of whichever provider you use.
Do not solve a staffing problem by passing one password around. Keep a named administrator and a joiner-and-leaver checklist. Test the actual phone and desktop experience before asking the team to rely on it during a shift.
Agree what each person does
The queue owner checks coverage
Choose who watches for new and unassigned requests during each working period. This person need not answer everything. Their job is to notice work with no owner and pass it to someone who can act.
The conversation owner carries the promise
The owner reads the latest history before replying, records the next step and keeps the customer informed. A colleague may add information in a private note. A handover changes the owner explicitly, with acceptance from the next person.
| Situation | Working rule |
|---|---|
| New message has no owner | Queue owner assigns it |
| Two people open the same conversation | Check ownership before composing |
| Specialist advice is needed | Ask internally; keep one customer contact |
| Owner leaves for the day | Hand over due work to a named colleague |
| Same request arrives twice | Link the records and keep one active thread |
Google Groups documents assignment and duplicate states. Those controls demonstrate why access, responsibility and completion should be treated separately. They do not mean every email app handles them the same way.
Separate the note from the reply
Before sending, inspect the recipients and whether the composer is a private note or an external message. A note such as “Please verify this refund before I reply” belongs inside the team, not in the customer's inbox.
Use a harmless practice conversation to rehearse replying, adding an internal note and handing over. If your tool has no private notes, keep internal discussion in an approved place and link it to the request without including the customer.
Decide what happens outside working hours
Publish the hours you actually cover, including the time zone. An acknowledgement should say when someone will review the request, without promising a fix. If you have a separate urgent route, state what it is for and make sure it is staffed.
The reply-template guide helps turn that promise into clear wording. The handover checklist helps a colleague keep it when shifts change.
Run a small collision test
Ask two team members to open the same test request. Can they see who owns it? Can they tell whether a reply has already been sent? Then change the owner and confirm that the next action survives.
Use the enquiry tracker to fill any gap your current tool leaves. Start by fixing one confusing moment in the working routine, then judge whether additional software would remove work you can actually name.
A conversation worth having
Reader comments
What has worked in your business? Share a useful example or ask a question. Comments are reviewed before publication.
Loading comments…