Detecting Changes in Requester’s Email Subject Line in Zendesk Support | Community
Skip to main content
Idea Submitted

Detecting Changes in Requester’s Email Subject Line in Zendesk Support

Related products:Ticketing system (Support)
  • July 23, 2025
  • 6 replies
  • 0 views
박

Hello Zendesk Community,

I’m encountering a challenge with our inbound email workflow and would welcome your advice:

 

Current Workflow

  • All customer emails are forwarded into Zendesk via our mail server alias.
  • Zendesk threads replies based on Message‑ID and References/In‑Reply‑To headers, so even if a requester edits the subject line, their reply attaches to the original ticket.

Problem

  • We need to know when a requester actually changes the email subject (for example, to introduce a new topic), but Zendesk does not update the ticket’s subject field in that case.
  • Without detecting that header change, agents cannot easily see that the customer meant to start a new conversation—this leads to confusion and delayed follow‑up.

Looking For

  1. Best practices or existing apps that can parse the incoming email’s Subject header (before Zendesk threading) and flag or warn agents when it differs from the stored ticket.subject.
  2. Any sample workflows, triggers, or API‑based solutions that reliably surface “subject‑only” edits as a distinct event or internal note.

Thank you in advance for your insights and recommendations!

    6 replies

    Scott12
    • Scott12
    • July 24, 2025

    Yes, admins having more control over how Zendesk links emails to tickets would be very useful. 

    We have exactly the same challenge you have mentioned but we also get examples of where a customer may forward their original query to a non-support email address (directly to their account manager for example) the account manager will then add in a support address and update the subject to match the existing ticket, expecting that because the ticket number is included in the subject that it will link it to the existing ticket. Sometimes, they even add the tracking code from the bottom of the body of ticket emails. Only to create a whole new ticket and cause confusion for the customer. 

    The current build seems to assume that customers never interact with any other members of an organisation other than the support emails and that just simply isn't the way many businesses work. Especially Professional Services providers. 

    MS Dynamics365 has a plethora of options on how the admin can choose to track and link messages, far superior. 

      W
      • Wendelin
      • August 26, 2025

      We are having the same issue. We must at least know that the customer changed the subject otherwise a lot of mistakes are easily happening.

      Splitting tickets afterwards on own action would be fine but we must have the info about it.

      Emily31
      • Emily31
      • August 27, 2025
      Hi all! Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
       
        W
        • Wendelin
        • August 28, 2025

        Only detection of subject line change should be pretty easy to implement I guess.

        W
        • Wendelin
        • September 18, 2025

        We are already using a app to easily split emails. I even understand that this may be required manually as long as the customer is working her in a not optimal way BUT the point is to even have a good chance of finding this out. We must know if the customer is changing the subject line – even in an open conversation. The subject line can have a major important information with high impact to the business.

         

        It would be very easy if I get the chance of a trigger condition “Subject line does not match ticket subject” with a variable of the current email subject. Then I can make a comment whenever the ticket subject does not match.

         

        We try our of best of educating our customers but I cannot expect that each of them changes their behavior for a thing which never was an issue.

         

        Such an advanced system which is missing such an basic feature. I cannot underline this enough that this is a constant issue which can have a high risk of missing on important things, actions and tasks which may lead to high damage costs.

          Benjamin24
          Thank you for taking the time to provide us with this feedback! 
           
          This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 
           
          Thank you again for your feedback and for being a valuable customer with Zendesk.
          Terms & ConditionsCookie settingsAccessibility statement