Skip to content

Support queue

Adrià Castany 2 min

What is a support queue?

A support queue is the set of conversations waiting to be handled by one specific group of people. Splitting the inbox into several queues (by channel, language, product or customer type) is the usual way of dividing the work once a single list stops working.

Also called

queue, work queue

Topic
Support concepts
On this page
  1. A queue is not a tag
  2. Why it matters
  3. Criteria for splitting queues
  4. When you need the first one
  5. Few, and on a clear criterion
  6. The ownerless queue
  7. How Intake handles it
  8. Frequently asked questions

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 you end up with fifteen tags that are supposed to distribute work and only describe it.

Why it matters

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.

Criteria for splitting queues

The ones that work are objective, meaning they do not depend on the opinion of whoever classifies.

  • By language.
  • By product or business line.
  • By channel, when the response deadline differs.
  • By customer type, such as accounts with their own service level agreement.
  • By specialty, such as billing or technical support.

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

Frequently asked questions

How many queues should a team have?

One, for as long as possible. The second appears when there is an objective criterion that 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.

What is the difference between a queue and an inbox?

The inbox is where the team sees and handles conversations. A queue is each of the lists that inbox is split into to divide the work.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment