This question stems from the problem that Reopen Review status isn't communicated. It's just one of many ways that people are impacted by that. It was the impetus for developing a new userscript.

SERopenReviewWarning, provides this information.

When a question has been through the review queue, the userscript produces a message under the Close message that looks like this example:

You can use this installation link with your userscript manager: https://github.com/BobVul/SEReopenReviewWarning/raw/master/SEReopenReviewWarning.user.js

If you've never used userscripts, you load a userscript manager, like Tampermonkey, Greasemonkey, or Violentmonkey, as an add-on in your browser. Then you use it to install userscripts.

That said, the problem described here could benefit from a different solution. If people saw this information automatically, it would avoid the issue described in the question. Most of the people in this situation will not have already loaded userscripts related to the Stack Exchange, and they aren't likely to run out and install this to answer their own question.

If the core users who respond to these complaints have this userscript (probably the same users who might load it anyway), they would have instant access to the information to respond to the complaints. They would still need to respond, but it would save researching the question timeline.

For the situation in this question, the ideal solution would be for the Stack Exchange to incorporate the feature into the site UI, so everyone automatically has access to the information. That would have added benefits, including a reduction in good questions fading into obscurity because nobody realizes that reopening them requires external intervention.

That's a problem that's easy to happen on sites, like Super User, that get technical questions from non-technical askers. The multiple rounds of clarifications and edits, that are commonly needed to fix a question, result in questions failing the reopen review before they are ready to be reopened.

But in the meantime, at least we now have this userscript as a tool.

This question stems from the problem that Reopen Review status isn't communicated. It's just one of many ways that people are impacted by that. It was the impetus for developing a new userscript.

SERopenReviewWarning, provides this information.

When a question has been through the review queue, the userscript produces a message under the Close message that looks like this example:

You can use this installation link with your userscript manager: https://github.com/BobVul/SEReopenReviewWarning/raw/master/SEReopenReviewWarning.user.js

If you've never used userscripts, you load a userscript manager, like Tampermonkey, Greasemonkey, or Violentmonkey, as an add-on in your browser. Then you use it to install userscripts.

That said, the problem described here could benefit from a different solution. If people saw this information automatically, it would avoid the issue described in the question. Most of the people in this situation will not have already loaded userscripts related to the Stack Exchange, and they aren't likely to run out and install this to answer their own question.

If the core users who respond to these queries have this userscript (probably the same users who might load it anyway), they would have instant access to the information. They would still need to respond, but it would save researching the question timeline.

For the situation in this question, the ideal solution would be for the Stack Exchange to incorporate the feature into the site UI, so everyone automatically has access to the information. That would have added benefits, including a reduction in good questions fading into obscurity because nobody realizes that reopening them requires external intervention.

That's a problem that's easy to happen on sites, like Super User, that get technical questions from non-technical askers. The multiple rounds of clarifications and edits, that are commonly needed to fix a question, result in questions failing the reopen review before they are ready to be reopened.

But in the meantime, at least we now have this userscript as a tool.