Case study
Why your team stops trusting the list of customers waiting for a reply
Our team app's waiting list filled with red rows for conversations that needed nothing. We added a way to close a chat without writing in it, and made the wait restart from the customer's next message.
Key takeaways
- A waiting list is only as good as its least accurate row.
- A conversation needs a way to be closed without anyone sending a reply.
- When a closed conversation reopens, the wait should start from the new message.
- One shared answer for waiting status keeps every device and reminder in sync.
In our own team app, the list of customers waiting for a reply only worked when every row on it was real. After combining all chats into one place, we saw red rows for conversations that had simply ended—a customer's thank you, a visitor who left satisfied. The list was telling us to answer messages that needed nothing, and that is how any support inbox fills with old chats.
What a red waiting row costs you
A waiting list stops being trusted as soon as a few rows are false. People start to ignore it or just scan for names they know, so the one customer truly waiting gets missed among those who are not. These false rows also keep reminders going to the team, and sometimes trigger an AI assistant to answer a thank you that needed no reply. We saw this first-hand after bringing every chat into one list with waiting ones on top.
Why old chats end up in the waiting list
The list treated the last message as the sign someone was waiting—even if that last message was just a thank you. There was no way in the system to record that a person had closed a conversation without replying. The app on the phone also guessed which chats were waiting instead of checking with the server, so the two could disagree.
The obvious fix, and what it missed
Our first fix was to add a No reply needed action on every waiting row. Before releasing it, we tested the whole process as a team member would, and found two problems this fix alone would have missed. First, a website chat already taken over by one of us never showed as waiting when the visitor wrote again—the phone's own rule left out a held chat. Second, after marking a conversation as needing no reply, the next customer message brought it back with a wait older than it really was, because the server still counted from the old message. Both faults were fixed and included in a new build the same day.
What the team has now
Now, every chat from every place appears in one Chats list, the same on iPhone and Android, with waiting conversations at the top. Any waiting row can be marked No reply needed by swipe, long-press, or from inside the conversation. It leaves the waiting list at once, remains in recent chats, and counters drop accordingly. An Undo option stays for five seconds before any change is sent. The mark is kept on the conversation, stopping reminders and keeping the AI assistant from answering a closed thank you—the website visitor never sees this. If the customer writes again, the conversation returns, and the wait starts from their new message. A chat taken over by a team member now reappears as waiting for that person if the visitor writes again. The server now decides for every chat whether someone is waiting and since when, and both apps show exactly that, so the phone no longer guesses.
Where this stands
The server-side changes are live. The visible change is in version 1.0.2 of our iPhone app, built and on its way to the App Store, and ready for the next Android version. Older versions of the app keep working unchanged.
What you can check yourself
- Count how many red items in your team's waiting list really need an answer today. If several are thank-yous or finished chats, people are already being taught to ignore the list.
- Ask your team how they close a conversation that ended without them writing the last word, and if the app allows it. If they use a workaround or just leave it, that's a sign to improve.
- Mark one test conversation as done, write to it again from a customer's phone, and see if it returns and whether the wait starts from your new message or an older one.
- Check that when one person takes over a chat, it doesn't vanish from their waiting list if the customer writes again.
- Compare the same chat on two phones. If one says waiting and the other does not, the app is guessing rather than reading one shared answer.
What to do next
Start by reviewing your team's waiting list. Ask whoever manages your app if a conversation can be marked as needing no reply without sending a message, and if a reopened chat counts its wait from the customer's new message. If not, set a clear rule: don't write a fake reply just to clear a row. Use any close action the app has, or ask for one.
This is the kind of work Tech Concierge engineers do to keep chat systems clear and reliable for teams who handle support across several channels.
Questions people ask
Why does my team ignore the waiting list in our chat app?
A waiting list is only as useful as its accuracy. When people find rows for conversations that need nothing, they stop trusting the list and may miss customers who are truly waiting for a reply.
How do we close a customer conversation that ended with a thank you?
The app should allow you to mark a conversation as needing no reply, without sending a message. If not, avoid sending a fake reply just to clear the row, and ask whoever manages the app about adding this feature.
Why does a conversation come back with an old waiting time after the customer writes again?
The system may be counting the wait from an old message instead of the new one. A reopened chat should start its waiting time from the customer's latest message to reflect reality.
Should the app or the server decide which chats are waiting?
There should be one shared answer—ideally from the server—so every phone and reminder sees the same state. If each device decides alone, they can show different results.
Will an AI assistant answer a customer after we mark the chat as needing no reply?
If the mark is kept on the conversation and the assistant checks it, it should not reply. In our case, marking as no reply needed stops reminders and prevents the assistant from responding to closed chats.