Turning off ticket management in your help center to allow email-only support

What's my plan?

Suite

Team, Growth, Professional, Enterprise, or Enterprise Plus

Support

Team, Professional, or Enterprise

Verified AI summary ◀▼

Switching to email-only support allows you to manage customer inquiries without requiring users to sign in. Users can still request support via email, chat, or social media, but they can't track requests or engage with help center content. Admins need to adjust settings to remove ticket links from notifications and sign-in options from the help center.

Many Zendesk accounts prefer not requiring their end users to sign in. Removing the sign-in requirement means end users can't view or track their requests on your help center, and they can't follow or vote on help center articles. These tasks require users to sign in. Instead, all communication between agents and end users occurs using other channels.

To provide email-only support, you need to understand the impact of this change on your customers, and then work through the items described in this article.

This article includes the following topics:

• Understanding how email-only support impacts customers
• Allowing anyone to submit tickets
• Removing links to ticket pages in your email notifications
• Removing sign-in links from your help center

Understanding how email-only support impacts your users

When you enable email-only support, end users can still request support without signing in by using any the following channels:

• Sending email directly to your support email address (for example, [e-mail])
• Submitting a support request using the Web Widget (Classic)
• Chatting with an agent
• Leaving a voicemail
• Sending a request through social media

Regardless of the channel by which new requests are submitted, requests become tickets that agents manage using views, creating and applying macros, generating reports, and so on. All communication between agents and end users is captured on those tickets and emails are sent back and forth between both parties.

End users can still access your help center to search for answers. You can promote this self-service support option by providing your end users with the link to your knowledge base (for example, http://mycompany.zendesk.com/hc).

Allowing anyone to submit tickets

To allow requests without requiring end users to sign in, you need to modify your end user settings. Only administrators can make these changes to end user settings. For information on making these modifications, see Enabling anyone to submit tickets in Zendesk Support.

When an unregistered end user submits a request for the first time, they are added as a new end user. They receive the request confirmation email but not the verification request email. They remain unverified in Zendesk Support.

Note: You might be wondering about the Allow users to view and edit their profile data and Allow users to change their password options. You can leave these enabled since your email-only end users will never be able to sign in to do either of these things. Both are still relevant to your administrators and agents.

Removing links to ticket pages from your email notifications

Users must sign in to view ticket pages in your help center. Because you don't want to require end users to sign in, you need to remove any links to ticket pages from any email notifications sent to end users. Some of your default triggers create notifications with ticket links.

Removing ticket links from your notifications

Remove any links to ticket pages from the default triggers that send email notifications to requesters. Here are the triggers you need to modify:

• Notify requester and CCs of received request
• Notify requester and CCs of comment update

You'll also need to modify any similar notification triggers (if any) that you created. Only administrators can edit the triggers.

You might also need to modify triggers that send email notifications to requesters and CCs, as well as the follower email template. See Customizing default email notifications for CCs and followers

To remove ticket links from email notification triggers

1. In Admin Center, click Objects and rules in the sidebar, then select Business rules > Triggers.
2. Open the trigger for editing.
3. Click the Notify requester and CCs of received request trigger to open it for editing.
4. Remove the {{ticket.id}} and {{ticket.url}} placeholders from the text in the email body. For example, here are before and after versions of the email text in the Notify requester and CCs of received request trigger.

   Before:

   Your request (#{{ticket.id}}) has been received, and is being reviewed by our support staff. 
   
   To review the status of the request and add additional comments, follow the link below:
   http://{{ticket.url}}

   After:

   Your request has been received, and is being reviewed by our support staff. 
   
   We'll contact you as soon as we have an answer for you.

5. Click Save.
6. Repeat for the Notify requester and CCs of comment update trigger.

Removing sign-in links from your help center

In your help center, removing elements that link to the sign-in page involves deleting or hiding template components. You must be a Guide admin to edit template components.

Note: Customizing your help center theme is not available on the Suite Team plan.

Your agents, like your end users, will no longer see a sign-in link for your help center. To access the sign-in page, your agents need to use the following URL: mycompany.zendesk.com/access. This is the sign-in page.

Removing the ability to sign-in means that every visitor to your help center is treated as an anonymous user with limited privileges. Anonymous users can view the public areas of your help center and share links to content. They can't comment on articles or participate in the community. Because anonymous users can't participate in the community, consider disabling your help center community, if you have one.

To remove the links to the sign-in page

1. In Knowledge admin, click Customize design () in the sidebar.
2. Hover your mouse over the theme you want to edit, then click View theme.
3. Click Edit code to open the code editor.

   

4. From the list of templates, click header.hbs.
5. From the code, comment out the sign_in fragment, like this:

   {{!--
     {{#link "sign_in" class="sign-in"}}
       {{t 'sign_in'}}
     {{/link}}
   --}}

   If you are using an old theme, you might see a user_info in place of a sign_in fragment. Comment this out instead:

   <!-- {{user_info}} -->

   This component displays a sign-in button on the right side of the header.

6. Select the article_page.hbs template and delete or comment out the following classes:

   <div class="article-comments">
   <div class="article-votes">

   The vote component and the article-comments section prompt users to sign in.

7. Click Publish.