Email-to-Ticket Done Right

At 02:14 on a Sunday the desk's mailbox received an out-of-office reply from a supplier. The help desk acknowledged it, creating a ticket. The supplier's system replied to the acknowledgment with the out-of-office reply. The help desk acknowledged that. By 07:30 there were four thousand one hundred tickets, all from the same supplier, all about nothing. The morning technician spent an hour working out why the dashboard said the desk was having its busiest day in history. E-mail is the oldest channel, the most used, and the one most desks set up in an afternoon and never think about again. It does not stop thinking about itself.

This series is about setting it up properly, once. It covers how a mailbox becomes a queue, in plain words. It covers threading replies to the right ticket, and what happens when the subject line loses the number. It covers loops and auto-reply storms, with the kill switch. Then come spam, junk and the review queue, where held mail waits for a person. It covers attachments, images and large messages, and testing the mail pipeline before you trust it. That includes the alert that fires when the desk's own mailbox goes quiet. E-mail will carry most of your tickets. Treat the pipeline like a server, because it is one.

Articles in This Series

• How a Mailbox Becomes a Queue: E-mail to Ticket in Plain Words
  The desk's mailbox is read, each new message becomes a numbered ticket, and replies go out from the desk's address. Also covers one mailbox per department, and the mailbox setup checklist.
• Threading Replies to the Right Ticket: Numbers, Headers and Merges
  Ticket numbers in subjects, message headers, and the forwarded mail that loses both. Also covers the reply that starts a second ticket and how to merge it, and the threading test sheet.
• Loops and Auto-Reply Storms: Detection and the Kill Switch
  Out-of-office ping-pong, two systems acknowledging each other forever, loop detection, the kill switch, the morning after, and the loop prevention checklist.
• Spam, Junk and the Review Queue: Hold It, Don't Delete It
  Filters on sender, subject and domain; hold for review rather than delete. Phishing reports are tickets, not junk. Also covers who reviews the held mail, and the screening rules table.
• Attachments, Images and the Message That Is Too Big to Arrive
  Size limits, inline images, where attachments live, the screenshot that is the whole ticket, the message too big to arrive, and the attachment policy.
• Testing the Mail Pipeline Before You Trust It
  The ten test messages, watching the mailbox itself, the mail that silently stops on a Friday, the alert on the desk's own inbox, and the test script.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.