How do I ask a customer enough questions to understand the problem?

Treat intake as a short conversation, not a form you must complete word for word. Begin by inviting the customer to describe the issue in their own terms. Then ask focused follow-ups about context, what they observed, what they have tried, and what they want to happen next.

A useful opening is: “Could you tell me what you were trying to do and what happened instead?” That gives the customer room to explain before you narrow things down. Ask one question at a time, acknowledge the answer, and skip anything they have already covered.

Ask for observable details rather than asking the customer to guess at a cause. For example: “What do you see when you try?” or “What did you expect to happen?” Depending on the situation, useful context may include which item or part of a process is involved, when the issue began, and whether it happens every time or only in a particular circumstance.

Keep the questions connected to their answer. If they say it began today, you might ask whether anything changed just before they noticed it. If they describe an unexpected message, ask them to share its wording if they can do so appropriately. Avoid requesting sensitive information or details that are not needed to understand the issue. You do not need to ask every possible question: ask the next one that would make the situation clearer.

Frame it as a way to avoid repeating steps, not as a test. Try: “What have you tried so far? I’d like to understand what you’ve already checked so I don’t send you through the same steps again.” If they mention an attempt, ask what happened afterward. Keep your tone neutral; do not imply they should have known what to do.

For instance, suppose a customer says a meeting invitation is not showing for one colleague. A useful follow-up could be: “Have you checked whether it appears for anyone else, or is it missing for that colleague only?” That is an illustrative example, not a diagnosis. The answer helps define the scope, but it does not establish the cause.

Acknowledge the urgency, then ask a direct question about the impact or desired next step. For example: “I understand this is holding things up. What do you need to be able to do next?” The customer may want the issue addressed, an alternative for now, an explanation, or an update by a particular time. Do not promise a fix or timing you cannot confirm.

Then briefly play back your understanding: “Let me check I have this right: you expected [expected result], but [observed result] happened when [context]. You have already tried [attempts], and the immediate need is [desired outcome]. Is that accurate?” Invite a correction. This gives both of you a shared description to use when deciding what happens next.

Use this as a flexible prompt, not a script you must complete in order:

“Could you tell me what you were trying to do and what happened instead?”

If needed, follow with:

1. “What did you expect to happen?”
2. “When did you first notice it, and when does it happen?”
3. “What have you tried so far, and what happened?”
4. “What do you need to be able to do next?”

Close with a short recap: “I heard [context], [observed issue], [attempts], and [desired outcome]. What should I correct or add?” In a live conversation, pause after each question and respond to what the customer actually says. In writing, send a small number of relevant questions together rather than a long questionnaire. If you still do not know the next step, explain what information is missing and ask only for that.