Direct answer
A shared inbox lets everyone see a message and so lets everyone assume someone else has it. The fix is to turn each message that needs action into a record with one owner, one status and a place for the reply. The inbox then becomes an intake point, and the records are where the work is tracked. We build this as a scoped workflow in your existing mail and task tools, not as a helpdesk product. It also covers the case where enquiries reach you at several addresses: they are pulled into one list, and sales enquiries are passed on to the CRM.
What arrives
List what really lands in the inbox before designing anything. Typically it is a mix: customer questions, supplier messages, sales enquiries, invoices, automated notices and internal chatter. Each kind needs a different route, and some need none. The first job is a short sort rule that separates "needs action" from "for information", agreed with the people who read the inbox.
Turning a message into a record
A message that needs action becomes a record holding the sender, the subject, a link to the original, a type and a status. Creation can be automatic for clear cases and one click for the rest. Keep the record small: it points to the email rather than copying it, so nothing is duplicated and nobody works from a stale copy.
Assignment
Every record needs one named owner, not a team name. Choose how owners are set: by message type, by sender, by rotation, or by a person who triages. Add a fallback so an unmatched message still lands on someone. If the owner is away, the record should move to their backup instead of waiting quietly.
Replies from the record
The owner works from the record and replies from there or from the mail client, with the reply linked back. The aim is that anyone opening the record sees what was said and what is still open. Status changes are simple: new, in progress, waiting on the sender, done. "Waiting" is worth having, since it separates work you are blocked on from work you have not started.
Duplicates and threads
People forward, copy and reply-all, so the same request can appear twice. Group messages from one thread under one record, and give staff a way to merge two records that are clearly the same issue. Do not merge on a loose match alone; a wrong merge hides a real request. Where the tool is unsure, it should flag a possible duplicate and let a person decide.
Enquiries arriving in several inboxes
Sales enquiries often arrive at info@, a contact form address and a personal mailbox. The workflow reads each agreed source, creates one record per enquiry, and passes genuine sales enquiries to the CRM with the source noted. Setting up the CRM side is described in email to CRM automation. The routing rule is yours: who gets a new enquiry, and what happens if nobody responds. We only connect the inboxes and systems you name and can grant access to.
The aged view and what stays in the inbox
One list shows open records by age and owner, so a stalled item is visible before a customer complains. Anything that needs no action stays in the inbox or is archived; do not create records for noise. When a message needs a person rather than a rule, see AI to human handoff, and for staff-raised requests see the internal request portal.
Scope
A single inbox-to-tracker workflow across a small number of tools can fit the fixed-scope Automation Sprint (€1,690); larger designs are quoted once the process is mapped. It is not a helpdesk product with ticket numbering, service levels or a customer portal. It is part of workflow automation and systems integration.
Questions
Is this a helpdesk?+
No. It is a lightweight workflow that gives inbox messages an owner and a status inside the tools you already use. There is no ticketing product, service-level engine or customer-facing portal.
Which mail systems does it work with?+
We confirm what your mail system and task tool allow before proposing a design. We do not assume a connection exists for any particular product.
Can it collect enquiries from several addresses?+
Yes, for the addresses you name and give us access to. They feed one list, and sales enquiries are passed to your CRM with the source recorded.
What if two people reply to the same message?+
One owner per record prevents it in most cases. The record also shows a reply has gone out, so a second person can see it before answering.