Use case
Shared inbox
In a mid-sized company a central mailbox is often the working memory of the whole business. And the place where things disappear.
The most visible effect day to day
The process
Where a person is needed - and where they no longer are.
- ClaudeLab from here
Step 01Person
Inbox
Intake
Step 02ClaudeLab
Sorting
Deciding
Step 03ClaudeLab
Handover
Output
The difference
The same process, once as it is today and once with us.
Step 01 · today
Step 01 · with us
Step 02 · today
Step 02 · with us
Step 03 · today
Step 03 · with us
What we build
- Component 01
- Incoming messages are sorted into your categories and assigned.
- Component 02
- Attachments are recognised and assigned to the right job.
- Component 03
- Standard cases get a prepared draft reply - unsent.
Degree of autonomy
Sorting and assigning run independently, because they are reversible. Replies never go out without a release.
Where it does not fit
If it is not settled internally who is responsible for what, the system sorts by rules that do not exist. Then that question comes before the project - it can be answered quickly, but someone has to answer it.
More specific
What this looks like in your sector
The process is sector-independent, the fit is not. These pages show the systems, the formats and the rules that actually apply there.
Logistics
In transport, a mailbox left sitting is standing time. Sorting is not a convenience topic here - it is part of dispatch.
ViewWholesale
In trade the shared mailbox is an order intake. What sits there is not unprocessed post, it is unrecorded revenue.
ViewProfessional services
In professional services the matching decides what can be billed. An email that lands in the wrong project is work nobody charges for.
ViewFrequently asked
What does it cost to automate shared inbox?
From €6,900 for the first process, from €4,900 for each further one in the same project. The firm price follows the audit (€2,500, credited against the project) - before that, any number would be a guess.
How long does implementation take?
2 to 4 weeks. Building it is usually the shorter half - the time goes into access, coordination and test cases.
What do we have to provide?
Access to the shared mailbox and the rules on who is responsible for what. A list of the cases that must never be answered automatically. Two weeks of real inbox to read along with, before anything goes live. Nothing more is needed to start.
How will we know it works?
From verifiable criteria agreed before the build: Across 300 real messages, at least 92 % reach the right area of responsibility. Nothing falls between two responsibilities - unclear cases go to a defined place. For everything that leaves the building, a person stays the sender.
Does the AI decide on its own?
Sorting and assigning run independently, because they are reversible. Replies never go out without a release.
When is this not worth it?
If it is not settled internally who is responsible for what, the system sorts by rules that do not exist. Then that question comes before the project - it can be answered quickly, but someone has to answer it.
Which sectors does this suit?
In our experience particularly Wholesale, Logistics, Professional services. The process itself is sector-independent, though - what matters is whether it repeats.
Tell us where your time goes.
In the audit we record the process, work out what is worth automating, and you get a plan with fixed prices - credited against the build if you go ahead.