Solutions/Operations

The shared mailbox,
worked.

Triaged, classified and routed as it arrives, with a reply drafted and waiting. Anything that leaves your organisation is gated behind a person until you say otherwise.

Get a Demo→

The situation

One address, everything arriving at it: requests, chases, documents, complaints, things that are not for this team at all. No queue, no owner, whoever opens it first deals with it, or decides it is someone else's and leaves it.

Four people each know part of the answer. The same question gets answered differently depending on who is in. The oldest thing in there is three weeks old and nobody is sure whether it still matters.

What arrives in a week

Routine requests with a known answerMOST OF IT

Chases on something already openA LOT

Documents to be filed somewhereSTEADY

Genuinely new problemsTHE FEW

The last row is what your team is for. The first three are what the queue is made of.

Triage, classify, route

Every item gets a type, an owner and a state within minutes of arriving, and a record saying why it was classified that way.

Read it properly

Including the attachment, the forwarded chain underneath and the thing the sender actually wants, which is often in the last line.

Give it a type

Your categories, not ours. New request, chase on an open item, document to file, not for this team, needs a person now.

Put a name on it

Routed to the person or rota that owns that type, with duplicates and chases attached to the item they belong to rather than sitting as new work.

Draft, approve, then, once earned, send

Replies start as drafts and stay that way until the record earns the step.

LEVEL 3Drafted, waitingThe reply is written, in your tone, with the source it relies on attached. A person reads it and sends, edits, or rejects, and the rejection teaches it.

LEVEL 4Batched for releaseA morning's worth of routine replies, grouped by type, released in one pass. The unusual ones are not in the batch.

LEVEL 5Sends the known onesOnly for reply types you have approved dozens of times, and only inside the organisation unless you have explicitly lifted that.

A floor, not a setting

Anything leaving the organisation is gated

A message to a customer, a supplier, a regulator or anyone else outside your boundary waits for a person by default, at every trust level. Internal replies can be earned. External voice is granted case by case, per reply type, by a named owner.

The reason is simple: inside the organisation a bad reply is embarrassing, and outside it is a commitment. The record shows who lifted the gate, for which type, and when.

The five levels and their floors →

Inside the boundary

Routing, internal answers, filing, updating the item. Earned through the record.

Outside the boundary

Held for a person, unless you have granted that specific reply type to that specific role.

What the ops lead sees at 9am

Not a dashboard of activity. A short list of things that need a person, and a longer list of things that did not.

Needs you

Three drafts to approve, each with its source.

One request it could not classify, and it says why.

One item ageing past your promise, flagged before the sender chased.

Already done

Overnight arrivals read, typed and routed.

Chases attached to the items they were chasing.

Documents filed where your team files them, findable by name.

Every line of both lists opens into the record: what it did, why, what it read, and what it chose not to do.

How records are filed →

Before you go furtherWho this is for, and who it isn't.The sizes, the work and the situations where we would tell you not to buy this, and what to look at instead.Who it's for →

One mailbox is enough to start. Preferably the one nobody wants to own.