Some conversations don't need to be answered (newsletters, automations etc.). They are archived/resolved very fast and therefore skew analytics' metrics.
Conversation stages offered a "no action needed" status, but are now deprecated. The "archived with/without reply" metrics are in the Conversations report that is under deprecation.
There needs to be a way to avoid these conversations from negatively reflect on the operational metrics.
One solution would be a filter to filter in/out any conversation that does not have at least one inbound and one outbound message.
Your idea is now live and open for voting.
It has been very helpful for us to identify non-interactive traffic especially when discussing changes with our internal product teams when it comes to automated notifications. Identifying the no reply traffic helps us to put engagement numbers into perspective, especially when an inbox is identified as high traffic just by volume, but it turns out that 70% of that traffic are automated alerts from other systems.