When replying to a support ticket, how many questions should I ask to get the necessary information without overwhelming the user? Is there a limit to how many questions are too many? It seems that only one will probably get answered anyway, but I want to make sure I can fully address the issue at hand.
4 Answers
I usually stick to a couple of emails to ask for info, and if I'm still missing what I need, I just call the user directly. Sometimes a phone call can clear things up much faster than waiting for emails.
My personal guideline is to keep responses short—no more than three sentences and one question. If it’s too long, people won’t bother to read it, and then you're just stuck waiting for a reply.
I think it really depends on the information needed. If the customer only says, "It's broken, fix it!" then you need to ask whatever questions required to get the details. It's all about clarity at the start.
Honestly, ask whatever you need to complete the request, but try to get the important details early. If you wait too long, it can feel like you weren't paying attention to their issue. That way, they understand you need more info, rather than seeing you as unresponsive for weeks.
Absolutely! Keeping it concise makes it easier for both sides.