Etiquette is latency management
In chat, the customer cannot see you working — they can only see whether text is arriving. Most "rude" chat experiences are actually silent ones: the agent was busy doing the right thing invisibly. Nearly every rule below is a way of making your work visible.
Chunk, don't monologue
A 200-word answer composed over three silent minutes lands as a wall after a worrying gap. Send it as three messages as you go: the direct answer first, the steps second, the caveat third. The customer starts reading while you keep typing — latency hidden, comprehension better, and they can interrupt if you misread the question.
Narrate your silences
- "Checking your account — about two minutes." beats two minutes of nothing.
- Come back BEFORE the estimate expires, even to extend it: "Still digging, need three more."
- If you must step to another conversation, say so honestly: "Bear with me a moment — right back."
Mirror the register
Match the customer's formality, not your template's. A terse "does it support SSO?" deserves a terse, precise answer; a chatty greeting can be met warmly. One asymmetry stands: they may use emoji and slang freely; you use them sparingly and only after they do. And never correct a customer's spelling by conspicuously spelling it right back at them mid-argument.
Multi-chat honestly
Concurrency is chat's superpower, and its trap. Cap yourself at the number where nobody waits more than ~30 seconds for a reply — for most agents that is two or three real conversations, not the six the dashboard permits. When you are saturated, let new chats queue with an honest wait rather than accepting and starving everyone.
Transfers and endings
- Transfer with the context attached. "I'm bringing in Maya, who owns billing — she can see everything we've discussed" — then make it true by passing the transcript, never by asking the customer to re-explain.
- Close with a summary, not an exit. What happened, what happens next, when. "Anything else while I have you?" then leave the door open: the transcript arrives by email either way.
- Let the customer close first when you can — ending a chat while they are typing is the door-slam of text.
Write it down as canned scaffolding
The best teams turn these habits into shared canned responses — not scripts to send verbatim, but scaffolding every agent personalizes. Ten minutes of weekly transcript review keeps the habits honest: read one saturated-hour conversation and ask which silence needed narrating.
Small habits that read as respect
Etiquette in chat is mostly made of very small things, because the medium strips out everything
else. There is no tone of voice and no face, so punctuation, timing and word choice carry the entire
signal, and habits that seem trivial to the agent are the whole experience for the visitor.
Use the visitor's own words for their problem rather than translating it into internal vocabulary.
Someone who says their login is broken should not be answered about authentication failures; being
restated in jargon makes people feel corrected. Acknowledge before you solve, in one short sentence,
so they know they were understood before they read the fix.
Read the whole message before replying to the first line of it. Answering the opening sentence of a
three-sentence message is a common cause of visitors repeating themselves, and it is entirely
avoidable. And when you have asked someone to do something, thank them for doing it before moving on.
It costs three words.
Correcting the visitor without making it a contest
A specific etiquette problem deserves its own treatment: the visitor is confidently wrong. They
have misread the price, misremembered the policy, or are describing a feature that has never
existed. How this is handled decides whether the conversation stays cooperative.
The move that works is to correct the fact without correcting the person. Give the accurate
information plainly and without a preamble about misunderstanding, and let them adjust privately.
“The included allowance is 500” lands very differently from “Actually, you have
misunderstood the plan.”
Where they were misled by something on your side — unclear wording, an outdated page, a
confusing label — say so, because it is usually true and it removes the sting entirely. It also
gives you the fix: a visitor who misread your page is rarely the only one. Where they are simply
mistaken, state it once and move on rather than proving it.
What to measure
Etiquette resists direct measurement, so read for it. A handful of conversations a week, read with
the single question of how this felt to receive, catches more than any score.
Watch for visitors repeating themselves in transcripts. It is a reliable, countable signal that
messages are being skimmed rather than read.
Pay attention to satisfaction on conversations that were resolved correctly but rated poorly. That
gap is almost always about how it felt rather than what was delivered, and it is the clearest
evidence that etiquette is worth explicit attention.