Zendesk Support and Zendesk Guide work in tandem to help you set up and manage your customer experience and support workflow.
Zendesk Support is the powerful back-end of your support operations: defining your support workflow and helping you manage your users and ticket queue. Zendesk Guide is the help center you provide to your customers and it contains your knowledge base content and gives your customers easy access to request support from your staff.
As you’ll discover in this article, Support and Guide work closely together and some of the key elements of your customer experience, as it’s presented to your customers in Zendesk Guide, are configured and enabled in Zendesk Support.
Perhaps most importantly, the tight alignment of Support and Guide enables agents to easily locate content in your help center so that they can add links to articles in their replies to customers, which increases the likelihood of one-touch ticket resolutions.
Understanding access controls for Support and Guide
Configuring end user access for submitting tickets and viewing your help center
Because your customers are the key element in all that you do with Zendesk, the customer (or end-user), records are shared across all products. When setting up Guide, this means that you need to configure user access and user roles in Support that will affect Guide.
Administrators in Zendesk Support can use the Customers and Security settings pages to define the type of access that you allow your customers. These access settings affect both Support and Guide access.
- Open means that everyone can see your help center and submit support requests.
- Closed means your help center is visible to everyone but only the users that you add to your Zendesk account can sign in and submit support requests.
- Restricted means that your help center is visible to all users but only users with email addresses in domains that you approve are able to successfully submit support requests.
| Zendesk Support | Zendesk Guide |
|---|---|
| Define who can submit tickets, if customers are required to register, help center access, authentication methods. | Require users to sign-in to see and use your help center, (this allows you to create a closed help center). |
Granting agents Guide admin privileges
An agent’s role in Guide is, by default, defined as Guide Viewer. This role allows them to participate in the knowledge base, but they don’t have any management privileges. Their permissions related to content are not role based, but are determined by user segments set in Guide. (There’s another layer of access permission for content that is explained in Restricting view and edit access to specific areas of content in your Help Center.)
Administrators are defined as Guide admins and are granted all privileges in Guide, including all management privileges and access to all content, regardless of user segment. Administrators can also grant full Guide admin privileges to agents.
| Zendesk Support | Zendesk Guide |
|---|---|
| Grant an agent Guide admin privileges. | View a comparison of role permissions by role. |
Restricting view and edit access to specific content in your help center
A user segment is a collection of end-users and/or agents, defined by a specific set of attributes, used to determine access to help center content.
Each user segment contains either signed-in customers or agents. Additionally determine which signed-in users or agents are included, based on attributes in their user profiles in Support. For signed-in users you can add the tags contained in their user profiles or the organization they’ve been added to, (or both). For agents, it’s based on tags and the agent groups they belong to.
User segments are the building blocks for user permissions. You apply user segments to a knowledge base article to define viewing access. And you use user segments to build management permissions that you apply to knowledge base articles to define editing and publishing permissions. You can apply only one user segment per article for visibility and one for management.
When you apply a user segment for visibility or management, only those users have permission to view or edit those knowledge base articles. User segments do not apply to Guide admins, who have access to all sections.
| Zendesk Support | Zendesk Guide |
|---|---|
| For customers, add tags to their user profile or add them to an organization
and use these as criteria for user segments. For agents, use tags and the groups
they belong to. Grant an agent Guide admin privileges. |
Create user segments and apply them to articles in the knowledge base. |
Enabling features that work together in Support and Guide
Customizing and creating support request forms
The support request form that’s available to customers in the help center is defined in Support, not in Guide. This form is displayed to customers in the help center when they click the Submit a request link, in the upper-right corner of your help center. You don’t see this form in the help center when you’re signed-in as an admin or agent.
The default version of the support request form contains the essential ticket data fields, (email address, subject, and description) and enables customers to include an attachment. You can add custom fields and make other changes to this form as needed in Support.
| Zendesk Support | Zendesk Guide |
|---|---|
| Configure and customize the support request form.
Note: On
Enterprise
plans,
you
can
create multiple ticket forms for different types of support
requests.
|
The support request form is displayed to customers in Guide. |
Setting up multiple branded versions of a help center
On most plans, you can set up multiple help center versions, for the different brands that you support (see Creating a Help Center for one of your brands).
Brands are defined as customer facing identities can include their own visual branding elements, domain name, email support addresses, help center, and other customer contact points such as the Web Widget, Zendesk Talk, and Zendesk Chat.
| Zendesk Support | Zendesk Guide |
|---|---|
| Add brands and enable separate help centers, as allowed. | Customize the look of and manage the content and users for each branded help center. |
Supporting multiple languages
When you enable other supported languages, you’re responsible for providing translations of the content you add. For Support that means any content you add to your business rules and support ticket workflow, (macros, automations, and triggers). For Guide that means any customized theme content, your help center name, category and section headings, and articles in your knowledge base. Only standard text in your help center, such as "Submit a request," is automatically translated for users.
| Zendesk Support | Zendesk Guide |
|---|---|
| Configure your account settings to support multiple languages. Manage the translations of content contained in your macros, automations, and triggers using a feature called dynamic content. Set and detect a user’s language. Include language as a condition in your business rules. |
Specify a default language for your help center and enable any languages you
want to support in it. Localize (translate), words used in your help center structure and any other text snippets you want to add to the help center user interface. Create language versions of your knowledge base articles and select a provider and a process for translating and publishing your articles. See:
|
Embedding Zendesk Support features into your help center using the Web Widget
- help center knowledge base search
- Your contact form
- Zendesk Chat (if available)
- Zendesk Talk callback request (if available)
- Contextual help
Although the Web Widget becomes a container for some of the features already provided in the Guide user interface (ticket forms and knowledge base search), the reason you may want to include it in Guide is to provide Chat and also make these components easily accessible from every page in your help center.
| Zendesk Support | Zendesk Guide |
|---|---|
| Enable and configure the Web Widget. Generate the Web Widget code that you can add to any website. |
Enable the Web Widget to be displayed in your help center. |
Enabling agents to incorporate self-service in their tickets
Directing customers to the self-service content in your help center
To help ensure that the self-service content you provide to your customers using Guide is discovered and used by your customers, it’s important to direct customers to it. You can help drive traffic to content in Guide using the agent interface in Zendesk Support.
You can add links to your help center articles in your global macro,s and agents manually add links to articles in their personal macros for replies to customers.
Agents can use the Knowledge Capture app in Support for easy access to help center articles. They can quickly search for and insert links to relevant articles in their replies without leaving the ticket.
Another option is to use Answer Bot, which uses machine learning to automatically respond to support requests with a list of potentially relevant knowledge base articles. Answer Bot is available on all Suite plans or can be purchased as an add-on to Guide.
| Zendesk Support | Zendesk Guide |
|---|---|
| Agents can use the Knowledge Capture app to insert links to help center
articles in their ticket replies. Start an Answer Bot trial to automatically respond to support requests with links to relevant help center articles. |
Provide the knowledge base content that is used by agents, the Knowledge Capture app, and Answer Bot. |
Providing feedback about and contributing new content to the knowledge base
Because your agents are constantly interacting with your knowledge base content and have firsthand experience with how effective it is, they should be active participants in its development and maintenance.
When you’re starting out to develop knowledge base content, you can analyze your support data to identify the areas that give your customers the most trouble or confusion and focus your efforts on documenting them.
Using the Knowledge Capture app, agents can easily search for and add links to knowledge base articles in their replies to customers. Agents can also flag articles that need attention (an update for accuracy, for example), and create new articles from within the app.
| Zendesk Support | Zendesk Guide |
|---|---|
| Use the Reporting tools in Support to discover which customer issues need
documentation. Use a ticket tagging process to flag issues that need documentation. Use an About field on your ticket forms to capture and categorize issues that need attention and documentation. Use the Knowledge Capture app to allow agents to contribute to the knowledge base from within the agent interface. |
Allow agents to directly manage and contribute content to the knowledge base
in Guide. Enable agents to use the Knowledge Capture app to flag and create articles. Allow agents to collaborate on creating and managing articles by setting up collaboration workflows with Team Publishing to review, approve, and publish content (Enterprise plans only). |
Managing end-user content in Support and Guide
Measuring user activity in your help center
For the knowledge base, Support tracks the number of articles created, views, votes, subscriptions, and comments. Search reporting provides insight such as what your customers are searching for, if they find what they’re looking for, and the number of tickets created after a search.
If you are using the Knowledge Capture app or Answer Bot, activity for those are available in prebuilt reporting dashboards, which greatly extends the standard reporting tools that are available in Support.
And finally, on all Guide plans, you can optionally use Google Analytics to track website engagement metrics such as number of sessions and users, page views, average session duration, bounce rate and so on. You set up a Google Analytics account and then connect it to Guide.
For more information about measuring help center activity and the success of your self-service channel, see Measuring self-service and ticket deflection.
| Zendesk Support | Zendesk Guide |
|---|---|
| Use the Reporting dashboard in Support to track knowledge base and search
activity. If you use them, track Knowledge Capture and Answer Bot activity in Zendesk Explore. |
Set up a Google Analytics account, add the tracking ID number to the Guide
Admin settings page, and then track website engagement activity in Google
Analytics. See:
|
Moderating end-user content in your help center
You can set up Guide to prevent all end-user contributed content or only end-user content that contain specific words from being publish until you allow it to be. When you enable content moderation, content is sent to a queue, based on your moderation settings, to be reviewed and approved by a Guide admin before being published in your help center.
| Zendesk Support | Zendesk Guide |
|---|---|
| Grant agents Guide admin privileges to agents so that they can moderate content in Guide. | For administrators and agents with Guide admin privileges, enable content moderation, manage end-user contributed content, and handle spam and spam user accounts. |
Managing spam
Both Support and Guide provide tools for preventing, managing, and removing spam and the user accounts associated with spam.
Support provides filtering for incoming support requests from the email channel, so that you don’t see and have to deal with it in your ticket queue. However, not all spam is caught in that filter and there are also reasons why some types of incoming support requests and emails may be flagged as suspicious. In these cases, Support suspends them and holds them in the Suspended Tickets view so that you can manually moderate them.
In Guide, spam comes in the form of knowledge base comments. To deal with spam in your help center, the spam filter is enabled by default to prevent new and edited end-user posts and comments that appear to be spam from being published to your help center.
You can manually flag and remove individual incidents of spam that might get through the filter. As you manage individual spam in Guide, you have the option of not only deleting the spam content but also of suspending the user who created it. When you suspend a user, that user can no longer submit tickets or post or comment in your help center.
For more information about all the spam prevention tools in place in the help center, see About Help Center spam prevention.
| Zendesk Support | Zendesk Guide |
|---|---|
| Zendesk Support filters and prevents spam from incoming support channels such
as email. Incoming email that is considered suspicious but not clearly spam is suspended and placed in the Suspended Tickets view. Users can be suspended when reviewing a suspended ticket and also in the user’s account profile. |
Manually mark knowledge base comments as spam. Optionally also suspend an end-user and delete all the content they created in your help center. Enable content moderation to control end-user content that appears in your help center. |
Creating and managing tickets from help center comments
Your help center is your self-service channel and its purpose is to enable your customers to help themselves solve their problems without contacting you for support (in other words, prevent tickets from being created). However, you also need to monitor and be an active participant in your help center.
Most importantly, don’t let questions asked in your help center go unanswered. That’s why it’s a best practice to assign one or more agents to monitor your help center and answer their questions when other customers don’t.
| Zendesk Support | Zendesk Guide |
|---|---|
| Manage and resolve tickets created from comments in your help center. | Create tickets from comments to follow up on a user question or take an issue offline. |
0 Comments
Please sign in to leave a comment.