The first question sets the length of the chat
Long chats are usually not caused by hard problems. They are caused by the agent spending the
first several exchanges asking things that did not narrow anything down, or asking for
information they could have looked up. Every question costs a round trip, and in chat a round
trip can be a minute of waiting while the customer types.
Good questioning is therefore an efficiency skill as much as a communication one. The aim is
the smallest number of questions that gets you to a confident diagnosis — and, just as
importantly, questions the customer can actually answer.
Start wide, then narrow
The reliable structure is a funnel. One open question to understand the situation, then
progressively closed questions to pin it down.
- Open: “What were you trying to do when it went wrong?” This gets the customer’s framing, which frequently contains the answer.
- Narrowing: “Does it happen on every order, or just this one?” Cuts the possibility space roughly in half.
- Closed: “Is the error the red banner at the top, or a message inside the form?” Confirms the specific case.
Agents who invert this — starting with narrow technical questions — often spend
five minutes ruling out things the customer would have eliminated in their first sentence if
asked openly.
Ask one question at a time
The most common failure in chat specifically is stacking. “Can I get your order number,
the email on the account, when you placed it, and what payment method you used?” produces
one of three outcomes: a partial answer, a long silence while they gather everything, or an
answer to only the last item.
Ask for one thing, get it, then ask for the next. It feels slower and is consistently faster.
Where you genuinely need several facts, number them and keep them to two or three — a
formatted short list is answerable, a paragraph of questions is not.
Do not ask what you can look up
Asking a customer for information already visible in the account is the quickest way to signal
that nobody is really paying attention. If the order history is on screen, do not ask when they
ordered. If the pre-chat form captured their email, do not open by asking for it.
The exception is identity. Where a request would change an account, issue a refund, or expose
personal data, you must verify through your normal account process — and it is worth being
explicit that a chat widget is not an authentication channel. Confirming details for security is
legitimate; just say why. “Before I change the delivery address, can you confirm the
postcode on the account?” is a question with a visible reason, which nobody objects to.
Questions that make people defensive
Some phrasings are diagnostically fine and socially costly. They imply the customer caused the
problem, which turns a technical conversation into a face-saving one.
- “What did you do?” Try: “What happened just before it stopped working?”
- “Are you sure you clicked save?” Try: “Can you tell me what you saw after you clicked save?”
- “Have you tried restarting?” asked first. It is often the right step and it reads as dismissal. Acknowledge the problem, then ask.
- “Why did you do that?” Almost never necessary. What they did matters; why rarely does.
The pattern is to ask about what was observed rather than what was done. Observations are
neutral; actions invite blame.
Check your understanding before acting
Before making a change, spending ten minutes investigating, or escalating, restate the problem
in one sentence and ask if it is right. It takes one exchange and catches the misunderstandings
that otherwise surface after the work is done.
“So the discount applied on the first order but not the repeat one, and both were
placed on the same account — have I got that right?”
Customers correct these readily, and the correction is often the actual diagnosis.
Know when to stop asking
There is a point where further questions stop adding information — usually because the
customer does not have the answer. Continuing past it is frustrating for them and unproductive
for you.
Signals to stop: repeated “I am not sure”, answers getting shorter, or the same
information coming back rephrased. At that point switch from asking to doing — investigate
from your side, ask them to try one specific thing, or escalate to someone with access to the
data. “I have enough to look into this, let me take it from here” is a relief to
someone who has run out of answers.
What to measure
Track messages-to-resolution alongside handle time; a chat resolved in twelve short exchanges
is a questioning problem even if the total time looks acceptable. In quality reviews, count the
questions asked before the agent had enough to act, and check whether any of them were answerable
from information already on screen. That single check is the fastest route to shorter, better
conversations.