I've found ignoring the zero effort message to be moderately effective. Not ignore the work... like actually go deal with the incident or whatever. I just avoid feeding into the loop of it. Some time later I'll casually let them know how it went.
Sometimes they're persistent. If you don't respond quickly they might send another question mark (no joke), or escalate.
When they do escalate I tend to present it as 'Oh yea, we noticed that on the monitoring system and I dealt with that afterwards'.
This could be a complete fabrication, I just don't like to encourage them. Was it you, or the queue?
The trick of corporate survival, as observed in those who can actually hack it, is extreme compartmentalization. They become two people: one who watches the abuse from a distance as if it were happening to someone else, and then a normal self that is functional enough to do the grocery shopping without bursting into tears. The problem is that very few people can sustain this compartmentalization (also known as: dissociation) for more than a few years. It tends to play out badly (memory issues, alexithymia, autoimmunity) in the long term.
Or somehow magically know what to do and say. If you say to little, you are not engaging with the team, say too much and you are disruptive. Say the wrong thing and thats a big problem.
We really need to move our society on from telling people that companies are a family and they look after people. They dont.
To put it in engineering terms: I don't care about the amazingly rich data structure manipulations you're doing internally, I want the json api endpoint to have the same spec as it did yesterday.