When a customer reports a problem you cannot reproduce, it can be tempting to say, “We can’t find an issue.” That wording goes further than the evidence: your attempt did not show the behavior, but it does not establish that the customer’s experience did not happen. A clear reply should say what you tried, state the limit of what you know, and ask for one specific check that could narrow the gap. This keeps the conversation respectful and gives both sides a manageable next step instead of another round of vague troubleshooting.
The useful bits
- Describe the conditions you checked and what happened during that check.
- Say plainly that you could not reproduce the behavior; do not imply it is absent.
- Request one focused, low-effort check and explain what result to send back.
Report your observation, not a verdict
Lead with the distinction between your attempt and the customer’s report. “I wasn’t able to reproduce this in the steps I checked” is a statement about your observation. “The problem isn’t happening” or “There is no issue” makes a broader claim that your evidence may not support.
Acknowledge the customer’s account without treating it as proven or disproven. For example, say that you understand they saw the behavior and that you have not yet been able to observe it yourself. This makes room for different conditions, timing, account settings, or steps without guessing which one explains the difference.
Make your attempt specific enough to be useful
Briefly describe the conditions you used: the action you took, the relevant screen or workflow, and any important detail the customer already supplied. Keep this factual and concise. If you did not check a particular device, account state, or sequence, do not imply that you did.
Specificity helps the customer spot a mismatch. “I followed the steps you described and the message appeared normally in that attempt” is more informative than “We checked and it worked.” If the conditions are still unclear, say so rather than filling in the gaps with assumptions.
Choose one next check, not a troubleshooting menu
Ask for the single detail most likely to distinguish the customer’s situation from yours. Depending on the report, that might be the exact action immediately before the behavior, whether it happens again after reopening the same item, or the approximate time it occurred. Choose only a check that is relevant and reasonable for this customer.
Avoid asking for a full history, several screenshots, and multiple tests in one reply. A long list raises effort and makes it harder to tell which observation matters. If the first check does not clarify things, you can agree on another step afterward.
Explain what information would help
Tell the customer what to report back and how it will help. For instance, ask whether the same action produces the behavior again and, if it does, for the time and the step just before it. Ask only for information appropriate to the issue; do not request passwords, one-time codes, or unrelated private content.
If a screenshot or message detail would be useful, specify the relevant part and remind the customer to leave out sensitive information. Do not promise that one result will identify the cause or guarantee a fix. The purpose of the check is to narrow the conditions, not to claim certainty.
A reply you can adapt
Use a calm, direct structure: acknowledge the report, state what you observed, clarify what that does and does not establish, then request one next check. Keep the wording in your own support voice and change the bracketed fields to match the case.
Thanks for describing what happened with [feature or action]. I followed [the steps checked] and could not reproduce the behavior in that attempt. That means I haven’t observed it under those conditions; it doesn’t establish that it didn’t happen for you. Could you try [one focused check] and tell me whether [specific behavior] occurs? If it does, please share [one relevant detail, such as the approximate time or preceding step], without including passwords or one-time codes.
Close the loop on the check
Before sending, confirm that the request is answerable: the customer can tell what to do, what outcome to watch for, and what to send back. Remove any sentence that sounds like a diagnosis unless the evidence supports it. Avoid promising a resolution or implying that the customer caused the issue.
The exchange has worked if the customer understands the limit of your reproduction attempt and can provide the requested observation—or explain why the check is not possible. When they respond, compare their conditions with the ones you checked and state what you will do next. If the behavior still cannot be reproduced, say that honestly again and choose the next proportionate step rather than treating the report as settled.
- Did I describe only what I actually checked?
- Did I distinguish “not reproduced” from “not happening”?
- Did I ask for one relevant check and specify what to report?
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction