Zendesk for Employee Service
Running Zendesk employee service on the helpdesk you already own is a sensible instinct. It works better than purists admit, provided you rebuild three assumptions first.
Zendesk employee service: what changes when the requester is a colleague
The queue mechanics are identical. Everything around the queue is not.
Customer support versus employee service
| Customer support | Employee service | |
|---|---|---|
| Who the requester is | Self-registered, often unknown | Known from your directory |
| Main intake | Email, web form, chat | Slack or Teams, email, a form |
| Volume shape | Steady, spikes on releases | Spikes on onboarding and payroll |
| Biggest privacy risk | Customer data leaking | Colleagues seeing colleagues |
| Metric that matters | CSAT and first response | Time to fulfil, and fewer direct messages |
| Success looks like | Fewer contacts per customer | People stop asking in corridors |
Separating the teams properly
This is where internal deployments go wrong, and it usually goes wrong in the same way: one shared instance where anybody in the agent interface can read anything.
HR tickets about pay, grievances or health cannot sit in the same searchable pool as "my monitor is broken". You want separate groups with restricted agents, separate forms, and separate views. On multi-brand accounts a distinct brand per internal service gives you a cleaner split, including different help centres.
Watch light agents here. They are excellent value for a subject expert who needs to add a private comment now and then, and their read access is broader than you'd assume. Grant it per group, not globally.
Restrict your internal knowledge base to signed-in staff with user segments, and remember that an internal article about a security incident is exactly the sort of thing that ends up screenshot into a group chat.
Intake where employees already are
Employees don't go to a portal. That's not laziness, it's that Slack or Teams is already open and the request takes eleven seconds to type there.
So put a form behind a slash command or a message action, and let the integration create the ticket with the requester resolved from your directory. The employee stays where they were. You get a structured ticket instead of a direct message that dies in somebody's notifications. The Slack route covers the mechanics.
Two rules make it stick. Reply in the channel as well as by email, because an employee who has to check a separate inbox will chase you in chat anyway. And keep the modal to three fields, since nine boxes gets abandoned and the request arrives as a direct message instead.
The failure mode to watch for is partial adoption. Half the team uses the integration, half still messages the IT person they like, and your reporting then describes half the demand while looking complete.
What to build in the first month
Keep it small. Internal service desks fail from over-configuration far more often than from missing features.
One form per service area, with as few fields as routing needs. A Slack or Teams entry point, because that is where the requests are already being made. An internal knowledge base with the ten answers you repeat weekly: VPN, password reset, expenses, the printer, holiday booking.
Then SLA policies on internal targets. Most in-house teams never set them, then have no evidence when somebody claims IT is slow.
Where it runs out
Zendesk is a queue product of unusual quality and it isn't an ITSM suite. There is no asset database, no discovery, no change record with a risk classification, no formal service catalogue with fulfilment steps.
You can approximate approvals and model assets with custom objects. Whether that survives an audit is a different question, and the honest answer is covered in Zendesk for ITSM and is Zendesk an ITSM tool.
For a few hundred staff where IT mostly fulfils requests, this is a perfectly respectable service desk. Nobody should feel bad about running one.
Frequently asked questions
Can Zendesk run HR ticketing as well as IT?
Yes, with separate brands or groups. Zendesk HR ticketing needs stricter visibility than IT does, and a Zendesk employee service desk shared across Zendesk internal teams works as long as nobody can read another department's queue. Zendesk internal support is otherwise the same product as customer support.
Can one Zendesk account serve customers and employees?
Yes, and it is common. Use separate brands, groups and forms so internal tickets never surface to customer-facing agents, and restrict internal articles with user segments.
Is there a specific Zendesk employee service product?
Zendesk has positioned employee service as a use case with supporting features rather than a wholly separate product, and packaging changes. Check the current Zendesk docs for what your plan includes.
How do employees raise tickets without a portal?
Slack and Teams integrations are the usual route, plus a shared internal email address. Employees will use whatever is already open on their screen.
Do employees need Zendesk accounts?
They need end-user records, which aren't licensed seats. Provisioning from your identity provider keeps them current without anyone maintaining a list by hand.
Should HR use the same instance as IT?
Same instance is fine. Same group, same views and same agents is not. Separate the access before the first sensitive ticket arrives, not after.
Outages create duplicates fastest
When something internal breaks, forty people report it in ten minutes. Ticket Merger collapses those into one automatically.
Start free trial14-day free trial. No credit card required.