Loading…
Systems / Inbox Triage
PROVEN IN THE LABtime · calm
Inbox Triage
Lanes, draft replies, you approve — then send.
- What it is
- Mail is classified into lanes. Replies are drafted. You click send.
- Typically gives back
- ~8–12 h/week of morning triage
- Replaces
- One overflowing mailbox and drafts started from zero.
What it costs you without this
Calm arithmetic, not fear. Methodology.
Mornings spent sorting newsletters from leads before any real work starts.
Lab measurement
Test-environment process run: 142 messages classified in one pass.
Lab measurement
Reply drafting started from scratch on every thread.
Lab measurement
No trail of what was sent and why — the next hire cannot take over.
Illustrative example
| Week | Month | At €40/h |
|---|---|---|
| 12 h | 48 h | €1,920/mo |
12 h/week × €40/h × 4 weeks
Lab process pattern — 12 h/week ≈ €1,920/month at €40/h. Your scan gives the real numbers.
A firm like this
Noordzee Supply
6-person webshop, ~60 customer emails/day
Without the system
- Leads, invoices and noise share one inbox.
- A hot enquiry sits under a shipping notification.
- Every reply is typed as if it were the first.
With the system
- Four lanes: lead, client, invoice, noise.
- A draft waits. You edit or discard.
- Nothing leaves without an explicit yes. The send is logged.
| Metric | Before | After |
|---|---|---|
| Morning sort | Unstructured | Lanes first |
| Hours/week on mail | ~12 h | Approve drafts |
| €/month at €40/h | €1,920 | Scan gives your number |
Illustrative composite example — not a real client
What is in the system
Only what we can point to. Missing pieces stay off this page.
Secure mailbox connection
Connects with OAuth to Gmail or Microsoft 365 on a schedule you set.
You see: Mail in. No password stored in a spreadsheet.
Four lanes
Lead, client, invoice, noise — with scoring so paying work surfaces first.
You see: A list ordered by what pays, not by arrival time.
Draft, never silent send
Replies are drafted in your tone. They wait.
You see: A draft. A button. Not a surprise in Sent.
Approval gate
Outbound mail cannot skip the human click. That is the architecture.
You see: Pending: 7. You decide.
Audit of sent mail
Approved sends log. Overrides train the lanes.
You see: Who sent what, and that you approved it.
Noise rules you can override
Low-intent mail is archived with rules you can break.
You see: Newsletters not in the same pile as quotes.
One mailbox first
Lab pattern starts with one box. More lanes after it is reliable.
You see: A boring, working morning — then we add the next box.
How it works
- 1. Create lanes for the work you actually have.
- 2. Draft replies from templates you approve.
- 3. You click send.
- 4. Log what left the building.
In the build
- OAuth connection to Gmail or Microsoft 365
- Lead / client / invoice / noise lanes
- Drafts in your tone — never silent send
- Human approval on every outbound
- Send log and override trail
- Start on one mailbox
- Documentation, scans, handover
- Your repository from day one
Good to know
No. Drafts wait. You approve. That is the product.
If you want a chatbot that answers customers without you, this is not it. We will refuse that scope.
You. OAuth to your tenant. Repo in your account from day one.
Works well with
Start with the scan
90 minutes. Written report is yours. Then a fixed price — or a clear no.