The repetition is the signal
One message is a person with a problem. Twenty of the same message is something broken with a queue in front of it.
The trouble is you experience them one at a time, spread over weeks, each one small enough to absorb. Nothing adds them up, so the total never gets big enough in your head to act on.
Onsay adds them up. Everything that arrives is read and sorted, and the ones describing the same thing are grouped. Twenty people saying they get signed out on their phone is one group, one decision, one fix.
Point your inbox at it
You do not change how you do support. Forward them in, or send them from whatever tool you already use. Paste in the ones that arrived as a message on a call.
What comes back is not a summary. It says this is something broken rather than something missing, this is where it probably lives, this is what would fix it, and here is how confident that is.
The fix lands, the message stops
Approve it and the work gets done, grouped with every other message describing the same thing. It arrives carrying the reasoning and the original wording of what each person said, so you are looking at a change with its evidence attached rather than taking it on faith.
You read it. You ship it. It stops arriving. That is two hours a month back, permanently, from one afternoon.
What about the ones that are not broken
Plenty of messages are confusion rather than defects. It says so, and separates something failing from somebody being lost. A misunderstanding usually points at wording or a label, which is still a change and still stops the message arriving.