Employee Service: Zendesk for HR and IT, not just for customers
Zendesk is known as a customer service tool. But the same platform has long run internal teams too: HR, IT, Finance, Legal. The Employee Service Suite is Zendesk’s answer to that. This text settles two things: what it is, and where it differs from classic customer service.
What Employee Service is, and who it’s for
Technically, the Employee Service Suite isn’t a new product but a variant of the familiar Customer Service Suite. It includes every function of the equivalent customer plans plus a handful built specifically for internal teams. The idea behind it: instead of external customers, your own workforce brings the requests. The ticket that used to come from a customer now comes from a colleague who needs a new laptop, wants her holiday approved, or has locked herself out.
Four building blocks that classic customer service doesn’t have:
- Service Catalog: a maintained list of services that employees request directly in the help center; the request is linked automatically to the ticket. Technically the catalog sits on Custom Objects, and a request takes up to five attachments.
- Approvals: sign-off steps directly in the request. Example: the manager approves the second monitor before IT orders it.
- Task Lists: predefined task lists for recurring scenarios. An onboarding runs through the same steps every time.
- IT Asset Management: an inventory of devices, assignment to employees, requests attached to the relevant asset.
Plus the Workday app, which shows central employee data (department, manager, role) read-only right in the ticket. Access stays read-only. Which fields appear depends on the mapping between your Workday and Zendesk instances and therefore differs from one setup to the next.
Which plan unlocks what
The most important buying decision is in the plan. The entry level doesn’t have the four internal building blocks yet — they only arrive one tier up:
| Building block | Team | Growth | Professional |
|---|---|---|---|
| AI Agents, Knowledge, Action Builder | ✓ | ✓ | ✓ |
| Service Catalog | – | ✓ | ✓ |
| Approvals + Task Lists | – | ✓ | ✓ |
| IT Asset Management (ITAM) | – | ✓ | ✓ |
So if you’re introducing Employee Service for the catalog, approvals, or asset management, you need at least Growth. List prices rise with the plan: $29 for Team, $59 for Growth, $99 for Professional, each per agent per month.
public/werkstatt/bauplaene/employee-service/service-catalog.png
Maturity per building block
Not every building block is equally far along. IT Asset Management is the youngest: it launched in autumn 2025 in Early Access. Task Lists run outside the ticket lifecycle, so there’s no automation and no due dates on the individual tasks. At the same point, Approvals were missing sign-off by an entire group and an API. Before the rollout, then, you check the current state of each building block: already generally available or still in Early Access, before you build a process on it.
Where it differs from customer service
On the surface much looks the same: tickets, Agent Workspace, help center. The difference lies in who sits on the other side and what that person may see.
- Internal users, not the public. There’s no public help center. Access always runs through SSO: internal knowledge sits behind the company login, not open on the web.
- Stricter access control. Private Groups and Department Spaces separate the areas: a payroll question from HR shouldn’t land in the same open queue as a printer problem for IT. With Department Spaces, ticket access shifts from groups to brands; the downside is a per-department fragmented Help Center that you choose deliberately.
- Channels employees already use. Alongside the portal, requests arrive through Slack and Teams. They serve as intake and escalation channels; the catalog and approvals can’t yet be fully operated through them or on mobile.
- AI for internal cases. The employee-service AI agents handle recurring, multi-step requests along your policies; for triage and next steps, Copilot steps in. Behind it sits a dedicated employee AI agent built on Unleash: it pulls knowledge from sources like Google Drive, SharePoint, and Confluence while respecting the access rights (RBAC) that already exist there.
Switzerland: internal HR data and the revDSG
Internal tickets often carry more sensitive data than customer support: pay, illness, termination. That puts Employee Service in Switzerland under the revised Data Protection Act (revDSG). Three points to settle before the rollout:
- Data residency and region. Where do the ticket data sit, and does that match your internal requirements?
- Access log. Who saw which ticket? Approvals work as an audit trail here, because every sign-off stays documented.
- Redaction. Sensitive details in tickets can be redacted before they become visible to a wider circle.
Bottom line
Employee Service is no magic trick, it’s the same Zendesk engine turned inward, with the guardrails internal work needs: private instead of public, SSO instead of the open web, plus approval, catalog, and asset logic that customer service doesn’t have. Run Zendesk for customers already and you know eighty percent of the tool. The remaining twenty decide whether internal teams trust it with their sensitive cases: SSO-only, clean department separation, Service Catalog.