Some support chats are over in two messages. Others turn into a long back-and-forth where both sides are polite, both sides are trying, and neither is getting anywhere. The second kind usually has the same cause: you're each describing a different screen.
So here's a rule we use and recommend: when a chat passes five messages without a fix, stop typing and start watching.
Why five
By the fifth message you've asked the obvious questions — which page, which button, what did it say. If the answers haven't led you to the problem, more questions won't either. What's missing isn't effort; it's a shared view of the screen.
Five isn't magic. Pick a number your team agrees on and stick to it. The point is to stop guessing at a fixed moment, not when everyone is already frustrated.
What “start watching” means
- Open their session. The conversation shows the customer's current page and their recent session. Watch the last minute or two: you'll often see the problem before you finish reading their last message.
- Check the timeline. Rage clicks, console errors and failed requests are marked next to the clicks. A failed request explains “it just spins” better than any description.
- Ask to help on their screen. For a “where is it?” problem, ask to show them: point, highlight or number the steps on their own page. They click the button themselves, and they'll know where it is next time.
- Call if it's faster. Some things are easier said than typed. A call from the chat runs in their browser — nothing to install.
What to say
Changing gear works best when you say why. A line that works:
“I think it'll be quicker if I can see what you're seeing. I'm going to ask to point something out on your screen — you'll get a prompt, and you can stop it any time with Esc.”
Customers rarely say no to that. They've been typing too.
What it changes
Long chats are expensive in the obvious way — your team's time — and in a less obvious one: every extra message is another moment the customer wonders whether to give up. Watching early turns a long chat into a short one, and leaves you a recording of the problem for whoever has to fix it.
The rule also makes life easier for newer agents. They don't have to judge when a chat is going nowhere; the count does it for them.
coview puts the chat, the session, co-browsing and calls in one conversation. Try it free or book a demo.
We build coview: session replay, co-browsing, chat and calls for support teams. Questions about a post? Ask us from the contact page.