Two hundred emails before lunch
The sales@ inbox is where everything arrives. An enquiry for 1,000 flyers. A customer's artwork for a job booked last week, attached to a reply to a completely different email. A proof approval. A complaint about a delivery. A merchant's price increase notice. Someone's out of office. Three people read the inbox, each assuming someone else has dealt with the enquiry that arrived at 7.40, and nobody flags it.
By Friday, the flyer enquiry has gone to a printer who replied on Tuesday, and the artwork that arrived by reply to the wrong email has not been matched to its job.
Everyone reads it, nobody owns it
Shared inboxes are good at receiving mail and bad at making sure it is dealt with. In print, they carry a mix of messages that each need a different person and a different action.
- Messages are not sorted by type, so enquiries sit next to invoices and complaints.
- Nobody is assigned, so everyone assumes someone else has it.
- Artwork and approvals are not linked to jobs, so they are found by searching.
- Flags and folders mean different things to different people.
- There is no record of how long enquiries wait for a first reply.
What the inbox costs
Enquiries that wait lose to printers who reply first. Artwork that is not linked to its job holds up production while someone searches. Complaints that sit unread get worse. And the people reading the inbox spend a large part of their day triaging instead of doing the work each message asks for.
An intake that sorts and assigns
- The shared inbox is connected, through Microsoft 365 or Google Workspace, to an intake service that reads each new message.
- Each message is classified, using a language model such as OpenAI or Anthropic Claude where rules are not enough: new enquiry, order, artwork, proof response, delivery query, complaint, supplier, or other.
- The sender is matched to a customer, and job numbers or references in the message are matched to jobs in your MIS.
- Artwork attachments are filed to the matching job and, if you use automated preflight, checked. Proof responses are recorded against the proof.
- New enquiries are turned into a draft spec with the missing details listed, and assigned to the right estimator or rep by your rules.
- Each message becomes a task with an owner. Messages the service is unsure about go to a human sorting queue rather than being guessed.
- A simple view shows unassigned and overdue items, and how long enquiries wait for a first reply.
| Message type | Goes to | Linked to |
|---|---|---|
| New enquiry | Estimator or rep | Customer, draft spec |
| Artwork | Prepress | Job folder |
| Proof approval | Account handler | Proof version |
| Delivery query | Dispatch | Job and tracking |
| Unsure | Human sorting queue | Nothing until checked |
An inbox that runs itself
Each message has an owner and a next step. Artwork is on the job before anyone goes looking. Enquiries reach an estimator with the spec half-built. The inbox stops being a place people scroll and becomes a place work arrives from. And you can see how quickly enquiries get a first reply, which is often the quickest way to win more work.
Is your shared inbox a black hole?
- Several people read the same inbox with no clear ownership.
- Enquiries have gone unanswered for days.
- Artwork arrives by reply to unrelated emails and gets lost.
- Complaints have sat unread.
- You cannot say how long enquiries wait for a reply.