Ticket Merger

Freshdesk Email to Ticket

Email is still most of the queue. Freshdesk email to ticket conversion rests on three settings, and one of them breaks silently.

Start free trialAll guides

The two addresses behind Freshdesk email to ticket

Every Freshdesk account has a system address on the freshdesk.com domain, created when you sign up. Mail sent there becomes a ticket immediately, with no setup at all.

You do not publish that address. You add a support address on your own domain, support@yourcompany.com, and connect the two. Customers see your domain, replies come from your domain, and your helpdesk isn't visible in the address bar of every conversation.

The connection happens one of two ways. Either you forward mail from your real mailbox into the Freshdesk system address, or you configure a direct connection to the mailbox where that is supported for your provider. Forwarding is the common route and it is the one worth understanding properly.

Forwarding, done in the right order

Sequence matters here, because a half-finished setup loses mail rather than erroring.

Add the support address in Freshdesk first, so the destination exists before anything is pointed at it.
Create the forward in Google Workspace, Microsoft 365 or wherever the mailbox lives. Both usually require confirming the forwarding destination.
Decide whether the original mailbox keeps a copy. Keeping one is a safety net during migration and a source of confusion afterwards, because somebody will start answering from the mailbox instead of the ticket. Turn it off once you trust the setup.
Send a real test from an outside address, confirm the ticket appears, reply from the ticket, and confirm the customer gets it from your domain.

Then do the test people skip: reply to that reply from the customer side and check it lands on the same ticket instead of creating a second one. Broken threading is the most common cause of a queue full of the same conversation three times over.

DNS, without the guesswork

You are asking a third party to send mail as your domain. Receiving servers are entitled to be suspicious about that, and if you skip this step a share of your replies quietly land in spam.

Three records matter.

SPF, which lists who may send for your domain. Freshworks publishes an include value to add to your existing record. You get one SPF record per domain, so edit the existing one rather than adding a second.
DKIM, which signs outgoing mail. Freshdesk generates the keys and shows you the records to publish.
DMARC, which tells receivers what to do when the first two fail, and gives you reports. Start at none, read the reports, then tighten.

The exact hostnames and values are specific to your account and they change, so take them from the email settings screen in your own Freshdesk admin area or the current Freshworks docs. Never copy DNS values out of an article, including this one. After publishing, allow for propagation, then verify in Freshdesk rather than assuming.

How threading actually decides

A reply joins an existing ticket by matching identifiers in the message headers, primarily the references and in-reply-to fields, supported by the ticket identifier Freshdesk places in the outbound mail.

If the identifiers survive the round trip, threading works. If something strips or rewrites them, it does not, and nothing tells you.

Things that break it: a customer starting a fresh email instead of replying, a mail gateway that rewrites message identifiers, an aggressive signature or footer appender, a ticketing system on the customer side generating its own thread, or your own outbound template losing the identifier during a redesign.

The other half of threading is what happens to replies on closed tickets. Depending on your settings, a reply either reopens the original or opens a brand new ticket. Both are defensible. What you cannot afford is not knowing which you have, because the second one is exactly how one conversation becomes two records with a shared history nobody can see. If you already have pairs like that, merging is the cure.

Why some emails never become tickets

The complaint is always the same: "I emailed you last week". Here's the checklist, in the order that finds it fastest.

Spam filtering. Both your mail provider and Freshdesk apply filtering. Check the spam or filtered view inside Freshdesk before blaming the forward.
An agent sent it. Mail from an address registered as an agent behaves differently from mail from a customer. This confuses people testing with their own work address more than anything else on this list.
Autoresponders and loops. Out of office replies and system-generated mail are often suppressed deliberately to prevent infinite loops, and that suppression can catch legitimate mail from automated systems.
The forward broke. Provider changes, an expired forwarding confirmation, or a mailbox over quota. It fails quietly, which is why a weekly test from an outside address is worth the thirty seconds.
A rule filed it first. A mailbox rule moving mail to a folder before the forward runs means nothing ever reaches Freshdesk.
An automation closed it on arrival. Somebody wrote a rule that auto-closes a category, and it's doing exactly what it was told. Check your creation rules and your notification setup together, since one often explains the other.
FAQ

Frequently asked questions

Why is Freshdesk email not creating tickets?

Usually forwarding. Freshdesk email forwarding has to point at the exact support address from the Freshdesk support email setup, and a filter or a loop-prevention rule upstream is the other common cause of Freshdesk email not creating tickets.

How do I set up a support email address in Freshdesk?

Add the address in Freshdesk first, then forward mail from your real mailbox to the Freshdesk system address, or connect the mailbox directly where that is supported. Test with a real message from an outside address afterwards.

Which DNS records do I need?

SPF and DKIM at minimum, ideally DMARC as well. Take the exact hostnames and values from your own Freshdesk email settings or the current Freshworks docs, since they are account-specific and change.

Why do replies create new tickets?

Something is stripping or rewriting the message identifiers, the customer started a fresh email rather than replying, or your settings create a new ticket for replies to closed tickets. Check which behaviour you have configured.

Why did Freshdesk email to ticket conversion skip a message?

Common causes are spam filtering, mail sent from an address registered as an agent, autoresponder suppression, a broken forward, a mailbox rule filing it first, or an automation closing it on creation.

Should the original mailbox keep a copy?

During migration, yes, as a safety net. Afterwards turn it off, or somebody will answer from the mailbox and the ticket will show a conversation that ends halfway through.

The same email, twice

Broken threading and impatient customers both create duplicate tickets. Ticket Merger finds and merges them, from $29/month with a 14-day trial.

Start free trial

14-day free trial. No credit card required.

Keep reading

Freshdesk Email Notifications: Stopping the Noise
How Freshdesk email notifications work for agents and requesters, how to cure notification fatigue, and the settings that send customers the same mail twice.
Freshdesk Automations: Rules That Earn Their Keep
How the three Freshdesk automation rule types work, which ones to build first, and the limits you hit when a rule needs to look at two tickets.
How to Merge Tickets in Freshdesk (2026 Guide)
How to merge tickets in Freshdesk step by step: how the primary is chosen, what happens to conversations and secondary tickets, and whether you can undo it.
Freshdesk BCC: What CC and BCC Actually Do to a Ticket
How CC and BCC behave on Freshdesk tickets, what the helpdesk BCC address is for, and the reason replies from a blind-copied address sometimes disappear entirely.