Skip to main content
Question

Best practices for handling customers who reply to old archived threads with new requests

  • June 5, 2026
  • 1 reply
  • 11 views
pgagent01

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? Any lessons learned would be appreciated.

    1 reply

    pgagent02
    • pgagent02
    • Conversationalist
    • June 5, 2026

    We've dealt with a similar issue, and one approach that has worked well for us is treating older reopened conversations as "new work" unless there's clear evidence that the customer is continuing the original issue.

    Our workflow uses a rule that checks whether a conversation was previously archived and inactive for a defined period. When a reply arrives after that threshold, we automatically apply a tag indicating that the conversation needs review and route it to a shared triage inbox rather than returning it directly to the previous assignee.

    This has helped for a few reasons:

    • The original owner may no longer be the best person to handle the request.
    • Customers often change topics within old email threads, making historical context less relevant.
    • A triage step ensures that genuinely new requests are categorized and assigned correctly.

    We've also found it useful to track these conversations separately in reporting. Over time, the data showed that a significant percentage of "reopened" conversations were actually brand-new requests submitted through old email chains. That insight helped justify additional automation and process changes.

    One lesson learned is to avoid fully automating reassignment based solely on a reopened status. In our experience, some replies are legitimate follow-ups to unresolved issues, so having a quick triage review before assignment improved accuracy.

    I'd be interested to hear whether other teams are using message content, AI classification, or custom fields to help distinguish between a true follow-up and a completely new request.

    Terms & ConditionsAccessibility statement