I just completed the ServiceNow Employee Slate Bootcamp Accreditation.
If your current projects include Virtual Agent or Now Assist, STOP.
Never heard of Employee Slate? That's exactly why I'm posting. It's becoming the new front door for employees; conversation first, powered by Moveworks. It looks like it's going to replace the Employee Center experience and the employee-facing side of Virtual Agent and Now Assist. Slate went GA in May.
Full disclosure: until recently I hadn't heard of it either. An account manager mentioned it in passing, once; that's the only reason the name ever reached me. It's what sent me digging, and the digging is what led to the bootcamp.
Out of curiosity, I googled the accreditation afterwards. Nothing. Not one result. A live product, training, an accreditation; and most of the people building on the current front door haven't heard its name.
Turn Moveworks on in Employee Center and the chat bubble in the corner stops being your Virtual Agent. Same button, different assistant. That's straight from the implementation guide. ServiceNow's own wording: Slate runs on "Moveworks (recommended), or Now Assist where Moveworks isn't available yet".
Which means every hour currently going deep into topics and sub-topics is an hour spent building for the assistant being replaced. And because Slate isn't sold on its own, it arrives inside packages; there's a decent chance it turns up in your estate at renewal whether you asked for it or not.
My honest read after three days inside it: expect the conversational layer you've authored to be rebuilt, not migrated. What survives is what sits underneath; your AI agents, your actions, your knowledge. Build accordingly.
If your VA/Now Assist project were mine, here's Monday morning.
Sort the backlog into two piles: things that help agents do the work, and things that talk to employees. The agent pile is safe. Summarisation, resolution notes, workspace skills; carry on.
The employee pile is the one Slate changes. Keep serving people; stop digging deeper. Keep topics thin, put the logic in flows and actions you can reuse, and spend the freed-up time on knowledge and catalog quality. Whatever the front door becomes, it still needs good content and clean actions underneath.
Pause the big Employee Center redesign. Finish what's in flight.
Read your entitlement schedule before renewal, so Slate arriving is a plan and not a surprise.
If you've already rolled out Employee Center or Now Assist, breathe: none of it is going away. Coexistence is explicitly supported, and nothing here says rip anything out. That's also why I'd pause the redesign rather than bin it; what you've built keeps working, it just gets less love from here.
To be fair to ServiceNow, every product fact above is on their public pages. Nobody has done anything sneaky. The gap is how fast it's all arrived, and how quietly.
Honest answer in the comments: had you heard of Employee Slate before today? Tell me on LinkedIn.
The build story behind Conassi starts here: The shift.
First published on LinkedIn, 27 July 2026. The conversation lives there; the guide lives here.