Two new names are showing up in every ServiceNow deck this year: EmployeeWorks and Employee Slate. They get used almost interchangeably, which is exactly why they're confusing. Here's the difference, in pictures, before you put either on a roadmap.
The equation
Now Assist and EmployeeWorks aren't competitors — they're the same intelligence layer facing two different audiences. Now Assist helps the people working inside ServiceNow. EmployeeWorks is the front door for the people asking ServiceNow for help in the first place.
How Otto answers a request
Understand intent
Researches across enterprise data to work out what's actually being asked.
Choose the path
Breaks the request into tasks, picks the right tools and agents.
Do the work
Triggers workflows, updates records, pulls data across 450+ connectors.
One clear answer
Returns a single conversational response, not a link to dig further.
What's different under the hood
Employee Slate isn't a reskin — it runs on AIUX, a different framework entirely.
What migrates on its own
ServiceNow is not deprecating Service Portal or Employee Center. Both remain fully supported. Employee Slate is early-stage — topic taxonomy, manager hubs, and complex custom page building aren't fully built out yet.
So which one fits you
Content-heavy intranet, deep navigation, lots of legacy widgets? Stay on Employee Center — the rebuild cost outweighs the gain today. A reasonably clean catalog and knowledge base, and ready to go conversational-first? Employee Slate is worth piloting — with a close eye on licensing and token costs, which scale differently than a traditional portal. Either way, it's an instance-specific answer, not a platform-wide one.