A broad complaint contains several symptoms and support needs one bounded test to narrow the cause.
The useful bits
- One diagnostic question
- Non-destructive test steps
- A useful reply reports the observed result and any stopping condition, without guessing at the cause.
Before you write
Use this example when a broad complaint contains several symptoms and support needs one bounded test to narrow the cause. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- One diagnostic question
- Non-destructive test steps
- Expected result and safe stopping point
An email you can adapt
The subject “One check for case [reference]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: One check for case [reference] Hi [name], To narrow down [issue], could you try [specific non-destructive check] once and tell us what happens? We expect [normal result]; please note the exact message if it differs. Stop if the action would change or remove information you need, and tell us instead. You do not need to repeat the full process or send unrelated data. [Owner] will review the result before suggesting another step. Best, [sender]
Check the boundary
Do not ask customers to disable security controls or delete stored information as a routine diagnostic shortcut.
What a useful reply should settle
A useful reply reports the observed result and any stopping condition, without guessing at the cause.
Compare the result with the diagnostic question and explain why the next step follows from it.
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