A support reply answers the question when it addresses the specific problem, the requested outcome and—if a fix is expected—the proposed method and timing. If the original question asked when a fix would happen, a reply that gives no timing leaves that part unanswered. A response that covers only some of the requested points is partial rather than complete.
What the original request established
A clear written complaint should explain both the problem and the outcome wanted. It should also identify any action already taken to resolve the issue.
Those details provide a practical baseline for reviewing the reply:
| Point raised | What to check in the reply | Sign that part remains unanswered |
|---|---|---|
| The problem | The reply addresses the same issue described in the complaint | It changes the subject or discusses a different problem |
| The desired outcome | The proposed response relates to the outcome requested | It offers activity without explaining how that addresses the requested outcome |
| The proposed method | If asked how the problem can be fixed, the reply explains the approach | The method is missing or too unclear to understand |
| The timing | If asked when the fix will happen, the reply provides a stated time | No timing is given, or the wording leaves the timing ambiguous |
A support contact may explain both how a problem can be fixed and when the work will happen. However, mentioning a possible fix does not necessarily answer a separate question about the requested outcome.
Why previous actions matter
The actions already taken are important context. The reader can compare them with the proposed response to see whether it builds on those attempts or suggests repeating a step that has already been tried.
A reply does not need to repeat every detail from the original complaint to be responsive. The central test is whether it resolves the ambiguity that caused the question to be asked.
What the reader must still confirm
The reader must confirm that the reply matches the problem and outcome actually described, rather than merely sounding relevant. Any promised action, proposed method or timing should also be clear enough to understand.
If an element is missing, a focused follow-up should identify that exact gap and ask for the missing explanation. This checklist assesses the completeness of a reply; it does not guarantee a particular correction, resolution or other outcome.