My perspective is a bit different. I feel that setting expectations is important. There is 10x more demand on me and my teams than they can handle so I find that acknowledging that I am aware of a request but won’t look at it for some time is helpful. I think it decreases stress because it differentiates between “I didn’t see it”/“I saw it and I don’t care” and “I saw it and will get back to it because I’m busy with other things”.
The former encourages people to chase you to get an answer, since they have no signal back. The latter gives them the opportunity to either accept the timeline or escalate if they need something sooner.
As I mentioned, that can be done today by posting a message in the topic. I feel this is a very “instant-messaging” approach though. It doesn’t make the conversation progress much and I don’t particularly want to bump a topic for this. It’s should be more like a reaction in my mind. The topic owner might be interested, but does everyone else want to have a new unread counter pushing them to open the topic and discover that A will reply next week, B will reply on Thursday, etc? I don’t think so, that’s very noisy.
The next best thing is to ask on slack when people will follow up but that now leads to a lack of transparency and added interruptions.
We are actually not using the platform I mentioned. However when we looked into our various options (discourse vs others in the context of asynchronous work) this was a really big pro for them and our team could instantly see how useful that would be.