Worknano

Shared inbox vs ticket system: when to switch

Updated 2026-11-15

A shared inbox vs a ticket system, also called a help desk, comes down to one question: can you tell who is dealing with each customer request? A shared inbox is one email address that several people read, such as info@ or support@. A ticket system turns every request into a "ticket": a numbered note with one responsible person and a clear state. Switch when you can no longer say who is handling a request and whether it is finished.

An everyday comparison

A shared inbox is like one letterbox for the whole office. Everybody can take the post out. Nobody knows for sure who has answered which letter.

A ticket system is like the numbered slips at a repair shop. Each job gets a slip. The slip says who is working on it and whether it is ready. Nothing is lost, and anyone can look up where a job stands.

The difference at a glance

Shared inboxTicket system
A request isAn emailA ticket with a number
Who deals with itWhoever opens it firstOne named person
What you can seeRead or unreadNew, in progress, waiting, done
Where requests come fromEmail onlyEmail, website form and chat in one list

When a shared inbox is the right choice

For one or two people with a small number of requests, a shared email address works well. Both see everything. A quick word settles who answers. There is no reason to add more structure before you miss it.

Six signs it is time to switch

  1. A customer got two different answers from two colleagues.
  2. A request was never answered, because everyone thought someone else had it.
  3. "Has anyone replied to this?" is asked most days.
  4. You cannot say how many requests are open right now.
  5. Requests also come in by phone or through the website, and those are noted somewhere else or not at all.
  6. Someone goes on holiday, and nobody knows where their half-finished conversations stand.

One or two of these now and then is normal. If three or more happen every week, the shared inbox is holding you back.

The biggest gain: knowing what is waiting

The most useful thing about tickets is a small one. You can mark a request as "waiting".

Sometimes you are waiting for the customer, who still owes you an answer. Sometimes you are waiting for a colleague who has to fix something first. In an inbox, both look like an old email. With tickets, they move out of the way. The list of things your team has to do today becomes short and honest.

How to switch in four steps

  1. Agree on a few states. For example: new, in progress, waiting for the customer, waiting for a colleague, done.
  2. Agree on a rule for who takes what. Every new ticket gets a responsible person within a fixed time, for example by the end of the morning.
  3. Send everything to one place. Emails to your support address and messages from your website form should all turn into tickets.
  4. Bring over only what is open. Leave old emails where they are. Move the open conversations by hand and start fresh on a Monday.

How Worknano handles this

In Worknano, everything someone asks of a team becomes a ticket in that team's queue, which is its list of open requests. A ticket moves through New, Open, Waiting on requester, Waiting on task and Resolved. Each move takes one step, and so does turning a ticket into a task. A form can be linked to a queue, and then each sent form arrives as a ticket. People outside the workspace are kept informed by email. Colleagues get a notification inside Worknano. The Requests Assistant sums up a queue, shows where a ticket stands and helps write replies. Tickets, the tasks they turn into and the documents that hold the answers are all in the same workspace. So a request never has to be forwarded out of sight.

Create a free workspace and move this week's open requests into a queue.