Use cases / Shared inbox

Use case

Everyone saw the email. Nobody answered it.

A mailbox five people watch has no owner. Messages get answered twice, or not at all — and the thread that matters is always in the inbox of whoever's away. None of it is anyone's fault, which is exactly the problem.

The mailbox everyone shares and nobody owns.

A customer emails enquiries@ on Tuesday. On Wednesday two replies go out — one from the office manager, one from the director, with different answers. On Thursday a supplier's question sits untouched, because everyone can see it and everyone assumes someone else has it. And the thread with the awkward history lives in the personal mailbox of someone on holiday — or someone who left in March.

The standing fix is a rota — be clearer about who picks up what. But an inbox five people watch has no owner by design, and no rota survives a busy week. Shared-inbox tools like Front or Missive exist and fit plenty of teams; the case for building it in is when the inbox needs to live inside the system that runs your work, not beside it.

How it actually works.

  1. Every shared address flows into one place — enquiries@, accounts@, the addresses customers actually use — and each message attaches itself to the client, job or candidate it belongs to. Not filed by a person a week later; matched by the system as it arrives.
  2. Every message gets one owner and a state. Needs a reply, waiting on them, done. The moment it lands it is visibly somebody's — so nothing sits in the gap where it's everyone's job and therefore no one's.
  3. The routine reply is drafted for you; a person sends it. The answer you've written forty times is drafted and waiting for approval. Nothing goes out on its own — the judgement stays human, the typing doesn't.
  4. The whole history lives on the record. Open any client's file and every conversation is there, including the ones that happened in a colleague's mailbox. Handovers and holidays stop being archaeology.

Where we've done it

Wired into a working platform.

This runs in production today. In the operating platform we built for a UK firm, the mailboxes are wired into the system of record: conversations are tracked against the client's file, and the communication history sits there next to the work itself — one part of a build where more than twenty separate systems run as a single flow.

Read the full case study →

What module one looks like.

We don't rebuild your comms in one go. Module one is the single address that leaks the most — usually the one on your website.

What the grey area costs.

Nobody can hand you an off-the-shelf number for this one, because the cost never appears on an invoice. It's the enquiry that never got a reply and became someone else's customer. The message answered twice with two different answers, and the hour spent smoothing that over. The client who chased three times and quietly concluded nobody was home.

Which of those your firm is paying depends on what lands in that mailbox. That's a thing worth finding out precisely — a process audit maps one week of your inbox and shows you where messages stall.

Not sure this is the one to fix first? The 20-question self-audit ranks your processes — free, two minutes, no email →

Start here

Bring us your inbox on a Monday morning.

A free process audit is thirty minutes. Show us the mailbox everyone shares, and you'll leave with a written map of where messages stall and how each one would find its owner on its own — whether or not we ever work together.

No pitch deck, no obligation. The map is yours either way.