Using the sample data for employee services

The Customer Support Suite and Employee Service Suite plans both provide full-service, cross-channel experiences for your users with the ticketing system, help center, messaging and live chat, and voice all working together. They also provide the basic components and configurations required to get you up and running quickly.

However, while the Customer Support Suite is designed for generic customer service, the Employee Service Suite is designed with common HR and IT use cases in mind. Therefore, Zendesk is able to provide more sample data and configurations that work out of the box for employee services.

This article describes what sample data and configurations are provided for new Zendesk accounts with Employee Service Suite plans and how to use it.

This article includes the following topics:

Understanding the additional sample data and configurations for employee services

Using the employee service sample data and configurations

Understanding the additional sample data and configurations for employee services

In addition to all of the standard content and configurations for the Customer Support Suite plans, Employee Service Suite plans come with the following additional sample data designed specifically for HR and IT use cases:

Ticket forms

Ticket fields

Macros

Views

Brands

Groups

Help center articles

Sample tickets

Using the employee service sample data and configurations

You have the following options when working with the sample data and configurations provided for Employee Service Suite plans:

Use it as-is.

Make adjustments, customizing it to better meet your needs.

Deactivate or delete any of the sample data and configurations you don't intend to use.

To make it easy for admins to identify the sample data and configurations, all of their names begin with [SAMPLE]. This preface isn't displayed to requesters in tickets cases where the name is visible to both agents and requesters. However, it's a good idea to remove this preface from the names of any sample data and configurations you decide to use in your workflows.

It's also important to understand that all of the sample data and configurations for employee services are active by default. That means, unlike Customer Service Suite and Support plans, Employee Service Suite plans have multiple groups, brands, and ticket forms from the start. This changes some expected behaviors, so it's important to identify which of these are applicable to your use case, and deactivate everything else.

For example, new Employee Service Suite plans have multiple brands and omnichannel routing on by default. However, omnichannel routing doesn't recognize which brands agents belong to and tickets are associated with, which can lead to issues. See Using brands (department spaces) with omnichannel routing.

To get started with a new Employee Service Suite account

Review the employee service sample data and configurations.

Deactivate the sample content you don't intend to use.

Configure the sample content you do intend to use. For example, you may want to:

Restrict views or ticket forms by brand to control agent access to tickets.

Configure groups that will handle sensitive information in tickets to be private ticket groups.

Decide whether you'll use omnichannel routing or other routing options. If you decide not to use omnichannel routing, you must turn it off.

Create ticket triggers, custom omnichannel routing queues, or other business rules to assign incomming tickets to groups. This is necessary as soon as you start adding agents.

Add agents and admins individually or in bulk.