Skip to main content
Closed for Voting

Threading by subject ( to avoid multiple new tickets )

Related products:Freshdesk
  • July 1, 2016
  • 2 replies
  • 51 views

Proper email threading is well described in https://www.jwz.org/doc/threading.html and relies heavily on the In-Reply-To and the References headers of an email and, if all else fails ( and this is extremely IMPORTANT ), on the Subject of the email - a technique called threading by subject.


"Threading" means that when Freshdesk receives a new email it has to decide if it belongs to an existing ticket ( in which case it add the email to the thread of that ticket ) or not ( in which case it generates a new ticket ).


We have a good number of customers that use exotic mail systems. These systems send replies that don't provide proper In-Reply-To and References headers ( if they provide them at all ). We also have customers that compose new emails and just use the Subject of our reply as the Subject of their response email in the belief that this is enough.


Judging from the fact, that other Freshdesk users also mention such cases, I believe that my problems are not unheard of but just more prevalent.


We have past experience with systems that used threading by subject and could handle these emails. My understanding from testing competitive products, is that a number of other helpdesk platforms, also implement decent threading by subject.


In most cases, the threading by subject implementation in helpdesk platforms relies on searching the Subject of the incoming email for a string that can be matched to a ticket number.  For example, it can be configured to look for the first occurrence of  SometextSomenumber and use Somenumber as the ticket number. Example Subject of a customer reply, with COMPX used as Sometext:


   Subject: Re: [ Case: COMPX674591 ] My gizmo is not working.


A threading by subject system that works as described above, will conclude that 674591 is the ticket number and, if a more reliable match cannot be made on the basis of In-Reply-To and References headers, will add the email to the thread of that ticket.


My understanding is that Freshdesk does not implement threading by subject ( but I would be very happy to be proven wrong ). I REALLY want Freshdesk to implement threading by subject ( and give the admin the option to enable or disable this feature and select the Sometext value they want ).


If you are a fellow Freshdesk user that has faced problems with multiple tickets been created when customers with problematic email systems reply, please support this feature request.



2 replies

BTW, threading by subject would also help with autoreply wars: If Freshdesk does not manage to append an incoming email from a broken autoresponder(*) to the thread of an existing ticket, it will  create a new ticket and thus will send another automatic email ( i.e. 'new ticket created' ) back to the broken autoresponder which, in turn. will reply again and so on. If Freshdesk manages to append the first automatic reply to the thread of an existing ticket, the cycle is broken.

 


*) Broken autoresponder: Freshdesk generated notification emails ( like 'new ticket created' ) contain the necessary headers that signify that no automatic replies should be generated in response to them. However, many autoresponders are "broken", which means that they do not respect those headers and send back automatic emails while they should not.


Searching the support forum of Freshdesk I discovered a number of threads that mention that adding [#{{ticket.id}}] in the subject of relevant Email Notifications, enables threading by subject:

https://support.freshdesk.com/support/discussions/topics/296293
https://support.freshdesk.com/support/discussions/topics/307569
https://support.freshdesk.com/support/discussions/topics/23630
https://support.freshdesk.com/support/discussions/topics/26592

I am testing this, and first results suggest that this is indeed the case.