'Oldest chat first' assumes every visitor in the queue is still there

Chatixy's inbox puts a pulsing green dot on conversations the visitor still has open, and the ticket banner says when they left. A reply to someone present and a reply to someone gone are different pieces of writing, and arrival order tells you neither.

'Oldest chat first' assumes every visitor in the queue is still there

In Chatixy's inbox a pulsing green dot sits beside every conversation the visitor has open right now, and it is missing from all the others. That one mark splits a queue that looks uniform into two different jobs. The standard rule for working a queue cannot see the split.

Oldest first is the right rule when every waiting chat is the same kind of thing

The rule is: work the queue oldest first. It deserves its place. It is fair, it takes one sentence to teach, nobody has to exercise judgment under pressure, and no conversation sinks to the bottom and gets forgotten. If every waiting chat is a person at a screen watching for your reply, arrival order is the right order and there is nothing to add.

The assumption hides in that "if". Arrival time tells you when someone asked. It does not tell you whether they are still there to be answered. A website chat is not a phone line where hanging up ends the call. The visitor closes the tab, and the conversation stays in your queue looking exactly as it did before.

This matters most for conversations that were handed over while nobody on the team was looking. That is the normal state of affairs if the assistant is covering the hours you don't staff.

The list carries a dot, the open ticket carries a banner with a clock

Presence shows up in two places.

In the inbox list, the dot sits next to the assistant name on each conversation the visitor currently has open. It pulses, so you can scan down the list and see which rows are live without opening any of them.

Open a ticket and the same fact becomes a banner above the conversation. It reads either "Visitor online" or "Visitor left the chat · Nm ago", where N is the minutes since they went. The banner answers the two questions queue order can't: is anyone there, and if not, how long has it been?

"Visitor left the chat · 5m ago" above the reply box is a different instruction from "Visitor online", even when the question underneath is word for word the same.

A present visitor can answer a question; an absent one needs the whole answer

A reply to someone who is there and a reply to someone who is gone are two different pieces of writing.

To someone online you can ask a question back and expect an answer. That is the efficient move: one short clarifying question saves you from writing three paragraphs about cases that don't apply. The conversation does the narrowing for you.

To someone who left, a reply that depends on a back-and-forth has nobody to go back and forth with. The clarifying question sits unanswered in the thread. If the person does come back to it, they find they waited and got a question in return. That reply has to stand alone, which means covering the branches yourself.

Here is an illustration. A shop visitor asked whether they can change the delivery address on an order, and the assistant handed it over because someone needs to look at the order.

Written under "Visitor online":

Yes, usually. Has the order shipped yet, or does it still show as processing?

Written under "Visitor left the chat":

It depends on whether the order has shipped. If it still shows as processing, reply here with the new address and we will change it. If it has already shipped, we can't change it from our side; reply with your order number and we will tell you what the carrier allows.

The first is the better reply to a present person and a poor one to an absent person. The second is the reverse: too long for someone who could have answered your question in four words.

The standalone version is easier to write than it sounds. A handoff arrives in the shared inbox with the full transcript and the sources the AI used, so much of what you would have asked is often already in the thread. The handoff practices we have written about before apply doubly here. Read the transcript first, and don't ask for anything the visitor already gave.

The banner is live, so a reply can change shape before you send it

The banner is not a stamp applied when you opened the ticket. When the visitor returns, it flips back to "Visitor online".

Say you start the long, branch-covering reply for someone who left, and halfway through the banner changes. You are now writing to a present person. Delete the second half, ask the one question, and let them tell you which branch they are on. A reply started for an absent person can be finished for a present one.

The opposite case is the awkward one. You asked a clarifying question, and the next time you look the banner says "Visitor left the chat". The question is now stranded. Follow it with the complete version, so that whatever the person finds when they come back is an answer and not a prompt.

Either way, the habit is to glance at the banner before you hit send, not only when you open the ticket.

Every leave and return lands in the History tab

The banner shows the current state. The record is in the ticket's History tab, where each departure and each return is written as its own entry: visitorleft and visitorreturned.

That makes the comings and goings readable afterwards, which is where a team lead gets the most out of it. For a conversation that went badly you can read how long the person actually stayed, and whether they came back while they were waiting. Those lead to different conclusions. A visitor who left right after the handoff was never going to be caught by a faster reply. A visitor who left, returned and left again was checking for you.

More than one viewer adds a count to the banner

When more than one viewer has the same conversation open, the banner appends "· N watching". With a single viewer you get the plain banner and no count.

It is a small addition, but it is the same kind of fact as the dot: something true about the conversation right now that arrival time cannot carry.

Oldest first among the people who are there, then complete answers for the rest

None of this throws out the old advice. It narrows where the advice applies. This is the working rule we would hand a new teammate:

  1. Among conversations with the green dot, go oldest first. These are the people for whom arrival order is still the fair order, because they are all waiting in the same sense.
  2. Then take the conversations without the dot, also oldest first, and give each a complete, self-contained answer that needs no reply to be useful.
  3. Before sending anything, check the banner once more. If it has flipped, rewrite for the person you now have.

Nobody gets forgotten under this rule, which was the whole virtue of oldest first. What changes is that the person staring at the widget is not kept waiting behind a careful reply to someone who has already gone.

The dot does not decide anything. There will be cases where you break the rule on purpose, and you are the one who knows them. The dot is there so that when you choose, you choose with the fact in front of you.

If you already run Chatixy, look for the dot before you pick your next conversation. If you don't, get started: add your website address, customize the support agent and watch it answer in minutes, with a 7-day free trial. See pricing for plans, limits and yearly discounts, or email info@chatixy.com for demos, Business plans and volume pricing.