Support queue
A queue is a set of conversations waiting to be handled by one specific group of people. Splitting the inbox into several queues — by channel, by language, by product or by customer type — is the usual way of dividing the work once a single list stops working.
What is support queue?
A queue is a set of conversations waiting to be handled by one specific group of people. Splitting the inbox into several queues — by channel, by language, by product or by customer type — is the usual way of dividing the work once a single list stops working.
Also: queue · work queue
A queue is not a tag
A tag classifies a conversation afterwards; a queue decides who sees it and with what priority. They get confused because many tools build both on the same field, and the result is fifteen tags created in the belief they distribute work when all they do is describe.
Why it matters
What changes in a SaaS
Because the alternative to queues is everybody looking at the same list, and that works with two people and breaks with five: two pick up the same conversation, nobody picks up the hard one, and the urgent thing sits under whatever arrived first.
Support queue in detail
When you need the first one
When two people work the same list at the same time and have already collided. Before that, a queue is process that gets configured and used by nobody.
Few, and on a clear criterion
By language or by product works because the criterion is objective. By "urgency" works badly: everybody believes their own thing is urgent, and it ends up as one queue with everything in it.
The ownerless queue
The most common failure is leaving a "miscellaneous" queue nobody watches. Every queue needs somebody responsible for emptying it, or it becomes the place conversations go to die.
How Intake handles it
Questions about support queue
How many queues should a small team have?
One, for as long as possible. The second appears when there is an objective criterion that genuinely separates the work — another language, another product — not when somebody wants to see "their stuff" apart.
Can you have queues per customer?
For large accounts with their own commitments, yes, and it usually works. The risk is ending up with a queue for every customer who complains, which is an expensive way to reward whoever shouts loudest.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Routing
Routing is the set of rules deciding which queue or which person each incoming conversation goes to: by detected language, by customer plan, by words in the message or by team workload. It replaces somebody distributing by hand.
Shared inbox
A shared inbox is a mailbox the whole team can access, where every conversation has an assigned owner, a status and a history visible to everyone. It replaces forwarding emails between colleagues and the generic address one person quietly runs.
Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
Front line
The front line is whoever receives conversations before anybody else: they resolve what is documented, gather the missing information and pass on what they cannot close. It is the filter that decides what reaches the rest of the team and in what state.
Ticket backlog
The backlog is the set of questions open and still unresolved at a given moment. More than its size, what gets watched is its trend: if more questions come in than get closed, the backlog grows, and it grows cumulatively even when the daily difference is small.
Overflow
Overflow is what happens when more conversations come in than the team can handle within its usual window. It is not a one-off failure: it is a state, and it usually lasts days, because what goes unanswered today piles on top of tomorrow.
