How it runs today
- 01One shared mailbox takes orders, enquiries, invoices and advertising all at once.
- 02Someone sorts by hand and forwards.
- 03Whatever falls between two areas of responsibility stays put.
Use case · Wholesale
In wholesale the ordering runs through the mailbox: call-offs, date enquiries, complaints and delivery notifications arrive in the same inbox as supplier advertising. Anything sitting here for an hour is not administration but a delayed dispatch.
The most visible effect day to day
What is different here
Not every customer has EDI. A large share orders by email, using their own product names and no numbers - entering it is manual work and the most common place for transposed digits.
“When is it coming?” can only be answered if stock, open orders and supplier commitments are pulled together. Which is exactly why the answer takes so long day to day.
Both name a delivery and a quantity. Which of the two is meant decides between a credit note and an order - and the difference is in the tone, not in a field.
If yours is not listed, that is not an exclusion. Where no interface exists, we build one - that is the most demanding part and it is our trade.
In trade the shared mailbox is an order intake. What sits there is not unprocessed post, it is unrecorded revenue.
The difference
A person does itThe system does it
How it runs today
How it would run with us
What it gets you
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.
In trade the shared mailbox is an order intake. What sits there is not unprocessed post, it is unrecorded revenue. Whether it pays for you depends on your volume - the audit establishes that.
Yes. The ones listed are those we most often meet in wholesale - a list, not a precondition. Where no interface exists, we build one.
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.
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.
2 to 4 weeks.
Sorting and assigning run independently, because they are reversible. Replies never go out without a release.
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.
This page shows the fit in wholesale. The process itself is sector-independent - what matters is whether it repeats.
Shared inbox in generalYou tell us where your time goes. We put it in writing: what is worth automating, and roughly what that costs.