How to Configure Email in Freshdesk

The email-to-ticket flow, in one paragraph

Before the menus, the mental model. A customer emails your support address. That mail is delivered into a mailbox Freshdesk can read — either a Freshworks-hosted mailbox ([email protected]) that your real address forwards to, or your own mailbox connected over Gmail, Office 365, or a custom server. Freshdesk picks the message up, creates a ticket, sets the sender as the requester, and routes it to the group you mapped. When an agent replies, Freshdesk sends the outbound mail from your reply-to alias and stamps a hidden ticket-ID marker so the customer's next reply threads back onto the same ticket instead of opening a new one. Every step below is just configuring one link in that chain.

Step 1: Add a support email (mailbox)

This is where the pipeline starts. Per Freshworks' Set up your support email documentation, you add a mailbox under Admin Settings → Channels → Email.

1. Go to Admin Settings → Channels → Email and click New support email.
2. Choose your email setup combination — Incoming only, Outgoing only, or Both (most teams want Both, so Freshdesk receives and sends).
3. Pick a mail server: the Freshworks mail server (the default, giving you [email protected]), Gmail, Microsoft Office 365, or a Custom mail server.
4. Enter the support email name and an email alias — the alias becomes your default reply-to address (e.g. [email protected]), so customers see your brand, not the Freshworks subdomain.
5. Assign incoming tickets to a group (the department or team that owns this address) and, if you run multiple products, link the email to a product.
6. Save.

Two plan notes worth knowing up front. You can add multiple support emails from the Growth plan onward; on the Freshdesk Free program you get one email address only. And assigning different mailboxes to different products is a Pro-plus capability. If you only need one shared inbox, none of that matters — the default Freshworks mailbox works out of the box.

Step 2: Set up email forwarding (Freshworks-server route)

If you chose the Freshworks mail server, your real address — [email protected], hosted with Google, Microsoft, or anyone else — has to hand its mail to Freshdesk. That's done with a forwarding rule.

When you add the mailbox, Freshdesk generates a distinct forwarding address for it (each support email gets its own, so mail from different inboxes never mixes). You then create a forwarding rule in your own mail provider that sends a copy of everything arriving at [email protected] to that Freshdesk address.

1. In Freshdesk's email setup, copy the auto-generated forward-to address for this mailbox.
2. In your email provider (Google Workspace, Microsoft 365, etc.), create a forwarding rule on [email protected] pointing at that address.
3. Return to Freshdesk and complete verification — only a verified support email can be used for outgoing replies.

Freshdesk documents the multi-mailbox and forwarding mechanics in Adding multiple email addresses to Freshdesk. Forwarding rules are only needed on the Freshworks-server route — if you connect your own mailbox directly, skip to the next section.

Step 3: Connect a custom mail server (Gmail, Office 365, or SMTP/IMAP)

Instead of forwarding, you can let Freshdesk read and send directly from your own mailbox. This is the cleaner path if you want mail to originate from your infrastructure. Freshdesk supports OAuth connections to Gmail and Microsoft Office 365, or a fully custom mail server over IMAP (incoming) and SMTP (outgoing).

• Gmail / Office 365: pick the server type, click Sign in, and authorise Freshdesk over OAuth — no app passwords, no forwarding rule.
• Custom server: enter your IMAP host/port/credentials for incoming mail and your SMTP host/port/credentials for outgoing.

The upside of connecting your own outgoing server is deliverability: mail is sent from your domain's own infrastructure, so authentication is more straightforward. For a step-by-step on the OAuth flow specifically, see how to connect Office 365 or Gmail to Freshdesk.

Step 4: Authenticate your mail with DKIM (and SPF)

An address that receives mail is only half the job; the mail you send has to be trusted, or it lands in spam. That's what DKIM does — it digitally signs outbound mail with your domain so receiving servers can verify it genuinely came from you.

You configure it under Admin → Channels → Email → Advanced Settings → DKIM, where Freshdesk gives you DNS records to add at your domain host and a Verify button to confirm they've propagated. The honest caveats, straight from the advanced email settings docs:

• DKIM requires a verified custom domain. If you're still on a [email protected] address (or a trial account), the DKIM page shows an empty state — there's no domain to sign for yet. You have to add a support email on a custom domain first.
• DKIM is recommended but not strictly required for a custom-mailbox configuration — "not required for custom mailbox configuration, however, we still recommend you configure this option." If you connect your own SMTP server, that server's own authentication does much of the work.
• SPF isn't configured inside Freshdesk itself; it's a DNS record on your domain authorising Freshdesk (or your mail provider) to send on your behalf. Pair SPF with DKIM for the best deliverability.

If your replies are landing in spam, DKIM/SPF is almost always the first thing to check. There's a fuller walkthrough in Freshdesk SPF, DKIM, and custom mailbox setup.

Step 5: Get threading and requester handling right

The last mile is making sure conversations stay conversations. In Advanced Settings, Freshdesk exposes the controls that decide how replies thread and who gets recorded as the requester:

• Ticket ID prefix — Freshdesk stamps a hidden marker like [#prefix-{{ticket.id}}] so a customer's reply lands back on the original ticket. If threading misbehaves, confirm this prefix is present in your outgoing email templates.
• Create requester from Reply-To and use original sender for forwarded emails — decide whether the forwarder or the original customer becomes the ticket's requester (important if a colleague forwards a customer complaint in).
• Automatic Bcc (up to 50 addresses) — silently copies an archive or monitoring inbox on all ticket mail.

Native Freshdesk email: what it does well, and where it stops

Credit where it's due: Freshdesk's native email is solid. The email-to-ticket conversion is reliable, the forwarding and OAuth options cover almost every mail setup, DKIM/SPF support is built in, and threading — once configured — mostly just works. For a huge number of teams, this is all the email infrastructure they need, and none of what follows is a knock on it.

But notice what "configure email" gives you and what it doesn't. Every step above builds a pipe — it gets the customer's message into a ticket and your agent's reply out to their inbox. It does nothing about the actual work in between: reading the email, understanding what the customer wants, and writing the answer. A perfectly configured mailbox still lands every message on a human who has to do the reading and the typing.

There are honest edges, too. DKIM is domain-gated — you can't authenticate mail on a freshdesk.com subdomain, so any team that hasn't moved to a custom domain ships weaker deliverability. Threading is rule-based, so unusual clients, stripped subject lines, or aggressive forwarding can still fork a conversation into two tickets. And forwarding rules add a hop that's one more thing to break silently.

This is the seam where an AI layer fits — and it's worth being clear-eyed about the build-versus-buy tradeoff before adding one. The category of AI agents for customer service exists to do the reasoning-heavy part the pipe can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, your mailboxes, or your DKIM setup. You connect Macha to Freshdesk with your subdomain and API key, and it reads the same email-to-ticket conversations your forwarding rules already create: drafting or posting a grounded first reply, triaging by intent, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. Credits are consumed per AI action, not per resolution — see the pricing breakdown.) If you want to see how that automation is wired, how to automate Freshdesk with AI walks through it.

The clean division of labour: keep Freshdesk as the system of record for how mail moves — the mailbox, the forwarding, the authentication — and layer an agent on top for the part the pipe can't do, which is actually answering what comes through it.

FAQ

Where do I set up a support email in Freshdesk? Go to Admin Settings → Channels → Email → New support email. Choose an email setup combination (Incoming, Outgoing, or Both), pick a mail server (Freshworks, Gmail, Office 365, or Custom), set your reply-to alias, assign the mailbox to a group, and save.

Do I need a forwarding rule? Only if you use the Freshworks mail server. In that case, your real address forwards mail to a Freshdesk-generated forward-to address. If you connect your own Gmail, Office 365, or custom server directly, no forwarding rule is needed.

How many support emails can I add? You can add multiple support emails from the Growth plan onward. On the Freshdesk Free program you're limited to a single support email address.

Why do I need DKIM, and can everyone use it? DKIM signs your outbound mail so it isn't flagged as spam. Freshdesk recommends it, but it requires a verified custom domain — you can't configure DKIM on a yourcompany.freshdesk.com subdomain, so you'll need a custom support-email domain first. Pair it with an SPF record on your DNS for best deliverability.

Can I add AI to Freshdesk email without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and works on the same email-to-ticket conversations your mailboxes create — drafting grounded replies and triaging by intent — while Freshdesk stays the system of record for how mail is received, sent, and authenticated.

Ready to turn your Freshdesk inbox into something that answers itself? Start a free trial of Macha and connect it to your Freshdesk in minutes.