FAQs: Email channel set up | Zoho Desk

FAQs: Email channel set up

Access and prerequisites

Who can configure the email channel in Zoho Desk?
Only users assigned the Support Administrator permission profile can configure the email channel. This includes viewing the support mailbox configuration, creating support aliases, and managing email retrieval for aliases.

If a user cannot access Setup > Channels > Email, their permission profile may not include the required Support Administrator access.
What happens when a customer emails a Zoho Desk support address?
Zoho Desk converts the incoming email into a ticket and assigns it a unique ticket ID. This allows agents to manage customer email requests through the ticketing workspace rather than from a separate mailbox.

For example, when a customer emails support@zylker.com, the message can be forwarded into Zoho Desk and created as a ticket for the appropriate support team.

Default support mailbox

Does Zoho Desk provide a support email address automatically?
Yes. Each Zoho Desk account includes a default support email address in this format: support@<portal_name>.zohodesk.com

The portal name replaces <portal_name>. This address is mapped to the default department and has a friendly name assigned.
Where can the default Zoho Desk support address be found?
  1. Navigate to Setup > Channels > Email.
  2. Open the Support Email Address page.
  3. Review the default address displayed there.
This address can be shared directly with customers if desired. However, organizations commonly continue using an established external support mailbox and forward its messages to the Zoho Desk address.
Must customers use the default Zoho Desk address?
No, Customers can continue emailing the organization’s external support address, such as billing@zylker.com, provided that mailbox forwards incoming messages to the matching Zoho Desk support address.

For example, messages sent to billing@zylker.com can be forwarded to support@<portal_name>.zohodesk.com so they are created as tickets.


Support email aliases

What is a Zoho Desk support email alias?
A support alias is an additional Zoho Desk email address used to receive tickets for a specific purpose. It is separate from the default support address but belongs to the same Zoho Desk account.

For example, sales@<portal_name>.zohodesk.com can be used for sales-related inquiries, while the default address remains available for general support.
When should a separate support alias be created?
Create an alias when different types of requests should be routed independently. This is particularly useful when the organization uses distinct public email addresses for teams such as sales, billing, escalations, or technical support.

For instance, an organization can create a sales alias and associate it with a dedicated Sales department. Messages forwarded from support@zylker.com can then enter Zoho Desk through the sales alias and go directly to the sales team’s workflow.
How is a new support email alias created?
  1. Navigate to Setup > Channels > Email.
  2. Open the Support Email Address page.
  3. Select New Support Email Address.
  4. Enter the alias details:
    1. Enter the address prefix used to receive tickets, for example, enter sales to create sales@<portal_name>.zohodesk.com.
    2. Enter a friendly name, for example, Sales Team.
  5. Select Save.
  6. Configure the equivalent external mailbox to forward messages to the new alias.
The external mailbox must forward to the equivalent Zoho Desk alias; creating the alias alone does not route messages from the organization’s external mailbox.
What is a friendly name for a support alias?
A friendly name is the display name associated with the support address. It appears before the email address.

For example, a friendly name of Zylker Sales for the alias sales@<portal_name>.zohodesk.com appears as: Zylker Sales <sales@<portal_name>.zohodesk.com>
Does creating an alias automatically connect the organization’s external mailbox?
No, Creating a Zoho Desk alias only creates the corresponding destination address in Zoho Desk. The matching external mailbox must still be configured to forward messages to that alias.

For example, after creating billing@<portal_name>.zohodesk.com, configure support@mycompany.com to forward to that address. Until forwarding is configured, messages sent to the external billing mailbox will not be delivered into Zoho Desk through the alias.
Can an alias be used to separate tickets by department?
Yes. An alias can be mapped to a separate department, helping route ticket types directly to the relevant team.

For example, sales inquiries sent to support@zylker.com can be forwarded to sales@<portal_name>.zohodesk.com, while technical requests sent to billing@zylker.com can be forwarded to the default support address. This keeps incoming ticket streams aligned with the teams responsible for them.
Can a support email alias be edited or deleted?
Yes. Aliases created in Zoho Desk can be edited or deleted from the Support Email Address page.

To delete an alias:
  1. Go to Setup > Channels > Email.
  2. Open Support Email Address.
  3. Select Delete beside the applicable alias.
  4. Confirm the deletion by selecting OK.
Before deleting an alias, update or remove any forwarding rule that sends external email to it. Otherwise, messages may continue being forwarded to an address that is no longer configured.
Can every support address be deleted from Zoho Desk?
No, Zoho Desk requires at least one support email address to remain connected. An account cannot be left with no support email address.

Managing email retrieval

Can email retrieval be temporarily stopped for a support alias?
Yes. Zoho Desk allows email fetching to be stopped or started for support aliases at any time.

This can be useful when an alias is temporarily unavailable, being reorganized, or no longer intended to receive new tickets. Before stopping retrieval, verify the operational impact: messages forwarded to that alias may no longer be fetched into Zoho Desk while retrieval is stopped.
Does stopping email retrieval delete the support alias?
The available information distinguishes between deleting an alias and stopping or starting email fetching for an alias. Stopping retrieval controls whether Zoho Desk fetches email for the alias; deletion removes the alias configuration.

Use the retrieval control when the alias should be retained for future use, and use deletion only when the alias is no longer needed.
 Forwarding Incoming Support Emails
Why should a support mailbox forward email?
Forwarding routes messages received at the organization’s existing support mailbox into Zoho Desk so they can be handled as tickets. This is useful when customers already send requests to a well-known address and the organization wants to retain that address rather than ask customers to use a new one.

For example, mail sent to support@mycompany.com can be routed to the organization’s Zoho Desk address, such as support@mycompany.zohodesk.com.
How is forwarding confirmed when using Gmail?
Gmail sends a forwarding confirmation email after forwarding is configured. In Zoho Desk, that email appears as a ticket in the Open Tickets view. The confirmation code in that ticket must be copied into Gmail to complete verification.
  1. Open Open Tickets.
  2. Open the ticket with Gmail Forwarding Confirmation in the subject.
  3. Copy the confirmation code.
  4. Return to Gmail and paste the code into the forwarding-verification field.
  5. Select Verify.
  6. Choose Forward a copy of incoming mail.
  7. Save the Gmail changes.
Forwarding will not be fully active until this Gmail verification is completed.
What is required when routing Google Workspace email to Zoho Desk?
Google Workspace routing can be configured in the Google Admin Console. The route should direct the organization’s support recipient to the Zoho Desk email address and add an X-Orig-To custom header that identifies the original recipient.

To configure it:
  1. Sign in to the Google Admin Console.
  2. Go to Apps > Google Workspace > Gmail > Default Routing.
  3. Select Configure or Add Another Rule.
  4. Add a setting and specify:
    1. Single Recipient: the support address, such as support@mycompany.com.
  5. In the envelope-recipient matching section:
    1. Select Modify Message.
    2. Enable Add custom headers.
    3. Add X-Orig-To with the original support address as its value.
    4. Enable Change envelope recipient.
    5. Set the replacement recipient to the Zoho Desk email address, such as support@mycompany.zohodesk.com.
  6. In options, select Perform this action on non-recognized and recognized addresses.
  7. Save the rule.
The custom X-Orig-To header helps agents identify that the email was routed.
Can multiple Google Workspace support addresses be routed to Zoho Desk?
Yes. The routing process can be repeated for additional support addresses. Each address can have its own routing configuration, allowing several support mailboxes to be directed to Zoho Desk.

For example, separate rules can be created for sales@mycompany.com, billing@mycompany.com, and support@mycompany.com.
Is a paid Yahoo Mail subscription required to forward messages to Zoho Desk?
Yes. Yahoo Mail forwarding requires a Yahoo Mail Plus subscription.

After forwarding is configured, Yahoo sends a verification email to the support address. That verification email can be located as a ticket in Zoho Desk’s Open Tickets view, where the verification process can be completed.

SPF and DKIM authentication

What do SPF and DKIM do for a Zoho Desk support domain?
SPF and DKIM authenticate the domain used for outgoing support replies.

DKIM adds a digital signature to outbound email headers. Receiving mail servers use the public key published in DNS to validate the signature. When the validation values match, the message is confirmed as having been sent by the domain and as unaltered in transit.
What are the overall steps for authenticating a support email domain?
Domain authentication follows four stages:
  1. Add and verify a From Address in Zoho Desk.
  2. Copy the SPF and DKIM record values for that address.
  3. Publish the copied values as DNS records with the domain host.
  4. Return to Zoho Desk and verify the domain after the DNS records are available.
This requires access to both Zoho Desk and the DNS settings for the organization’s email domain.
Where can SPF and DKIM values be found in Zoho Desk?
After the From Address is verified:
  1. Go to Setup > Channels > Email > DKIM Authentication.
  2. Locate the domain associated with the From Address.
  3. Select Verify beside that domain.
  4. In the authentication window, copy the provided text-record values.
These values are used to create the required TXT record in the domain’s DNS manager.
Where should SPF and DKIM records be published?
The records must be published in the DNS settings managed by the organization’s domain host. This may be the provider where the domain was purchased or another service that manages its DNS records, such as GoDaddy, Cloudflare, or BlueHost.

Paste the selector values and TXT-record values copied from Zoho Desk into the DNS configuration, then publish the changes.
How is a domain verified after the DNS records are published?
After the SPF and DKIM records are available in DNS:
  1. Navigate to Setup > Channels > Email > DKIM Authentication.
  2. Select Verify next to the relevant domain.
  3. Select Verify again in the authentication window.
When validation succeeds, the domain status changes to Verified.
What should be checked if the domain does not become verified?
Confirm each of the following:
  1. The From Address was added and verified in Zoho Desk.
  2. The SPF and DKIM values were copied for the correct domain.
  3. The selector and TXT-record values were published in the domain’s DNS settings.
  4. DNS propagation has had sufficient time, typically 24–48 hours.
  5. The address is not sending through the organization’s own SMTP server, since Zoho Desk SPF and DKIM authentication is unavailable in that configuration.
Does DKIM verification prove that an email was not changed during delivery?
Yes. A receiving server validates the DKIM signature against the public key in DNS and compares the signature-related values. A successful match indicates that the email originated from the authenticated sender and was not altered in transit.

For instance, if support@zylker.com sends a reply through Zoho Desk and its DKIM record validates successfully, the receiving server can confirm the message’s authenticated origin and integrity.
Read more: