Skip to main content
Closed for Voting

Email headers are more reliable for OOO detection

Related products:Freshdesk
  • November 26, 2019
  • 1 reply
  • 33 views

Word matching in the subject line and body of the email to detect an out of office reply is unreliable.


Use case:

  1. Users creates a ticket
  2. The ticket is worked and closed
  3. An email is sent to the user about the ticket closing
  4. The user sends an OOO reply

Expected result:
The out of office reply is ignored

Actual result:
The out of office reply creates a new ticket skewing our metrics


If the recipient email server is RFC3834 compliant a header field will be added "Auto-Submitted" where that field has any value other than "no".  Allowing us to match on email headers would allow for more reliable filtering.  We could eliminate the edge cases where users out of office reply does not contain the words we expect.


Parsing the email headers could be useful for other scenarios too.  For example - Web forms could inject specific headers and would be filtered reliably.


Example headers from a gmail auto reply

 

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Precedence: bulk
X-Autoreply: yes
Auto-Submitted: auto-replied
X-Gm-Internal: 1

 

1 reply

Hello Brian,


Did you get a chance to try the Thankyou Detector feature?


The Freddy bot can understand the intent of customer responses to 'resolved' or 'closed' tickets to decide if it should be reopened or not and make sure your metrics are not hampered. This includes for the OOO emails as well.


Cheers!