Best practices for handling customers who reply to old archived threads with new requests Hi everyone,We're reviewing our support workflow and have run into a common challenge: customers often reply to an old resolved email thread when they actually have a completely new request.Currently, when this happens, the conversation reopens in Front, but it can sometimes remain associated with the original owner or context, which makes triage more difficult and increases the risk of missing new work.We're considering a workflow that would:• Automatically detect replies to conversations that have been archived for a certain period of time.• Apply a tag such as "Reopened - Review Required."• Route the conversation back to an unassigned queue for triage.• Use analytics to track how often customers start new requests through old threads.For teams handling a high volume of customer support, logistics, or account management messages, how are you managing this scenario?Have you built rules or tagging structures that help distinguish a genuinely reopened issue from a completely new request
