How to turn support email into tickets
To turn support email into tickets, route your support address into a tool that opens one tracked record per conversation, threads later replies onto that same record using the message headers, and gives every record a status and an owner.
The worry that stops most teams before they start is DNS: people assume email to ticket means handing your mail domain to a vendor. For the large majority it does not. A forwarding rule on the mailbox you already have is enough, it takes a minute, and you can undo it just as fast. Step 2 lays out all three routing options so you can pick the least invasive one that works.
A ticket is not a magic object. It is one record per customer conversation, carrying a status, an owner, and the full back and forth. Everything below is about getting mail into that record reliably and keeping it there when the customer replies.
Steps
- 1
Decide what one ticket means
The unit is the conversation, not the message. A customer writes in, you answer, they answer back: that is one record with three messages on it, one status, and one owner. Teams that instead open a record per message end up closing the same issue four times and reporting numbers that mean nothing. Whatever tool you pick, check this behavior first, because it is the difference between a queue you can trust and a list you have to read.
- 2
Pick one of the three ways to get mail in
Forwarding is the simplest: add a rule on [email protected] that copies everything to the inbound address your tool gives you. No DNS change, reversible in a minute, and the original mailbox keeps its copy as a safety net. MX delegation is the cleanest delivery: point the MX records of a subdomain such as support.yourcompany.com at the tool so mail arrives directly with no second hop. It costs a DNS change, and you should never point your main domain at a help desk unless that tool is your only mail host. OAuth connection is the third: authorize the tool against your Google Workspace or Microsoft 365 mailbox so it reads and sends through the mailbox itself, which usually also lets it import mail that is already there. It needs no DNS and no rule, at the cost of the broadest permission grant of the three and a token somebody has to re-authorize when it expires.
- 3
Make replies land on the record they belong to
Threading is done with headers, not with subject lines. Every message carries a Message-ID, and a reply carries In-Reply-To and References pointing back at it, which is how a tool knows this is the same conversation. Some tools also stamp a token in the subject as a fallback for clients that strip those headers. Threading breaks in predictable ways: a customer writes from a different address, or starts a brand new message instead of replying, or forwards the thread in from a colleague. Check that your tool can merge two records into one by hand, because you will need it.
- 4
Break the auto-reply loop before it starts
The classic failure is a loop. Your mailbox forwards to the tool, the tool sends an acknowledgment, and something on the other end answers the acknowledgment, which forwards back in and starts again. Three rules avoid it. Forward in one direction only, and never set the tool to send back into the mailbox that feeds it. Confirm the tool suppresses auto-replies to mail marked as automatic (the headers to look for are Auto-Submitted and Precedence). And remove any vacation autoresponder from the mailbox you are forwarding from. Then send one test from an outside address and count the acknowledgments: exactly one should arrive.
- 5
Decide whether the customer ever sees a ticket number
Since threading runs on headers, the bracketed number in the subject line is optional in most modern tools, and it is the single thing that makes a small team read as a call center. Turn it off in the subject template, and check the auto-reply body too, since that is where a reference number usually hides. Keep the number if customers phone in and need something to quote, or if you resell support and have to cite a case in a report. Otherwise let the conversation look like an email.
- 6
Handle the mail that is already in the mailbox
Forwarding and MX delegation are both forward-only: they act on new mail and know nothing about the two years sitting in the folder. An OAuth connection can often import history, which is worth checking if that history matters to you. If it cannot, the low-risk pattern is to leave the old mailbox in place and read-only, let the open threads there finish out over a week or two, and let everything new arrive in the tool from the cutover date.
Frequently asked questions
Do I need to change my MX records?
Usually not. A forwarding rule on your existing support address, or an OAuth connection to the mailbox, gets mail into a ticketing tool without touching DNS at all. MX changes only come up when you want the tool to receive mail directly for an address, which is generally done on a dedicated subdomain such as support.yourcompany.com rather than your main domain. Pointing your primary domain MX at a help desk means all company mail routes through it, which is rarely what a small team wants.
Will customers see a ticket number?
Only if you leave one switched on. Modern tools thread replies using the Message-ID, In-Reply-To, and References headers, so a reference number in the subject line is a fallback rather than a requirement. Check two places if you want it gone: the subject template and the body of the automatic acknowledgment. Keep the number when customers phone in quoting it or when you owe someone a case reference in a report, and drop it when you would rather the exchange read as a normal email.
What happens to email already in the mailbox?
Nothing, unless you deliberately import it. Forwarding rules and MX changes only affect mail that arrives after you make them. Some tools can import history through an OAuth connection to Google Workspace or Microsoft 365, so check that if your archive matters. Otherwise the safe pattern is to keep the old mailbox accessible but read-only for search, let its open threads close out over the following couple of weeks, and treat the cutover date as the line.