We have recently refreshed our branding across our offerings and changed the names of our pricing plans. If you have signed up before Aug 9, 2021, please click Previous plans to view your applicable plans.
We assure you that this change will not impact your product experience, and no action is required on your part.
For every incoming email, Freshdesk checks 3 email markers to understand whether the email is a reply to an already-existing ticket. If the email is identified as a reply, Freshdesk performs additional sender email checks to make sure it's not spam.
Email Markers Check
Freshdesk looks for the following three markers in every incoming email. For an email to be threaded to a ticket, it has to pass one of the following checks:
- Ticket ID (if enabled)
- Unique Identifier
By default, when a customer creates a ticket in your portal, a ticket ID is generated. The notifications that the customer and agent receive about the ticket updates will carry the ticket ID in the subject line. When the customer or agent replies to these notifications, Freshdesk will check if the ticket ID matches and will thread the reply accordingly.
Additionally, to ensure that your ticket replies get threaded to the right ticket, you can also configure a unique ticket threading identifier. To set this up:
- Go to Admin > Email > Advanced Settings > Configure prefix for Ticket ID.
- Provide a name that will get appended with your ticket ID, and hit Save.
- This name will now appear on all incoming tickets (eg: #Freshworks-1234).
Freshdesk lets companies that want to send personal replies to their customers remove the ticket ID from the subject line. If the ticket ID is not present, the threading check is done in the following two ways:
Every email has a unique identifier assigned to it by the email provider called Message-ID. (You can read this article to know how you can find the Message-IDs of emails from various email providers).
When you reply to an email, the Message-ID of the original email is available in the 'In-Reply-To' or in the 'References' section of the email, using which a reply gets threaded to the original email. Freshdesk uses the same method to thread replies to tickets.
Apart from a unique identifier set by the email provider, Freshdesk also has a unique identifier for every email notification sent. This is done using a hidden div tag in the email. As long as the tag remains intact, the email will be threaded properly. For example, if the customer uses plaintext mode to reply, the ticket identifier will not work.
Email ticket threading will also work when two different businesses use Freshdesk to work with each other. Specifically, each Freshdesk account will add an identifier as part of the email message in the hidden div tag so that ticket threading will work in Reply and Forward scenarios.
Helpdesk address as recipient check:
- If the customer sends an email to firstname.lastname@example.org and email@example.com, then it will be created two separate tickets. That is, if the customer keeps two addresses configured in the helpdesk as recipients in the same email, then it won’t be merged or threaded under the same ticket.
- Also in the middle of a ticket conversation, if the customer replies adding another support address, then that reply will be created as a separate ticket, and also be displayed as a reply in the current ticket.
After the ticket is identified as a reply, the requester email should be one of the following for it to be threaded to a ticket:
- Requester email address of the ticket
- Agent email address of the ticket
- Email address(es) in the CC of the ticket
- Email address(es) to which the ticket was forwarded
So unless an email satisfies one of the email markers check and one of the sender email checks, it will be created as a new ticket in your helpdesk. If, however, the agent understands that the new ticket is a reply to an existing ticket, they can merge the tickets manually.