What this domain covers
Email tests the inbound and outbound path: support address setup, forwarding, authentication, threading, email commands, notifications, templates, and spam handling. Email remains the highest-volume channel, so small misconfigurations create large ticket noise.
Core rules and concepts
- The support address usually forwards into Freshdesk, or is fetched through IMAP/POP. SPF, DKIM, and DMARC records must authorize the sending path or replies land in spam.
- Threading depends on the ticket ID in the subject line, commonly formatted like [#12345]. If a mail client strips it, the reply can create a new ticket instead of updating the existing one.
- Email commands let agents or permitted senders update tickets from the message body, for example status, priority, assignment, or agent mentions. Commands should be documented and restricted to trusted senders.
- Notifications and templates control what agents and requesters see. Observer rules and account notification settings decide who is copied; template errors are visible to customers.
- Multiple support mailboxes can route into different groups. Each mailbox needs its own forwarding and authentication checks.
- Spam handling, blocked domains, and auto-reply detection reduce loops; out-of-office replies should not reopen or spam tickets.
Worked example
A customer replies to a notification. The subject still contains [#12345], so Freshdesk threads the message into ticket 12345 and reopens it if it was Resolved. A second customer forwards the same thread after deleting the bracketed ID; Freshdesk treats it as a new ticket and creates a new requester record. The reasoning: the ticket ID is the threading key. The fix is to preserve the subject or use the reply-to address, not to merge after the fact unless duplicates already exist.
Traps that cost marks
- Missing SPF or DKIM records, causing outbound mail to be filtered.
- Allowing email commands from untrusted senders.
- Forwarding loops between the support mailbox and Freshdesk.
- Agents replying from personal email instead of the ticket interface, breaking threading and reporting.
- Assuming a forwarded email without the ticket ID will update the original ticket.