Customers keep asking us a great question. Flow by ServiceNow and ServiceNow EmployeeWorks (formerly Moveworks) both give employees chat-based help in Slack and Microsoft Teams. So what’s the difference?
The truth is, these are radically different products. Each one solves a different problem. And for ServiceNow customers, there’s a place for both. Let’s start with what each one is built to do.
An AI service desk for every stage: the full ServiceNow platform and Flow
Two products, two different jobs
EmployeeWorks: the front door for your entire enterprise
If you knew it as Moveworks, it’s the same front door, now part of ServiceNow. Employees go to one place, a portal or chat, to get help from any department, find answers, and kick off requests.
EmployeeWorks handles a multi-department request in one conversation
EmployeeWorks works alongside ServiceNow products and service catalog your teams already use, like ServiceNow IT Service Management, and routes each request to the right place with ServiceNow as one of the deeply supported system of records. It reaches well beyond ServiceNow too, with 100+ enterprise application connectors and 40+ search sources, all under the permissions and governance an organization-wide front door demands.
If you use ServiceNow and want one front door for every employee, and to interface with key organizational departments like IT, HR, Finance, Legal, etc. EmployeeWorks is the answer. Full stop.
Flow: a full-stack AI service desk for one team
Flow is an AI service desk built for a single team in the Fortune 500, or a whole organization in the Fortune 500,000. Unlike EmployeeWorks, Flow tracks and resolves requests on its own. It gives a team one place to take requests, answer questions, and close issues in Slack, Teams, and email.
Flow takes and resolves requests right in Slack, Teams, Email, or Web
It’s built for two kinds of customers: teams inside a ServiceNow customer that want their own service desk up and running fast, and organizations new to ServiceNow that want to start with one team, like IT.
Yes, Flow can connect to the ServiceNow platform. When it does, it pulls in knowledge and asset context so the team has what it needs, and it syncs work back to ServiceNow so your system of record stays complete. But Flow isn’t built to be the front door for the rest of the company. Flow is the front door… for Flow.
Built for purpose: what only each one can do
What about building automations in plain language?
You can do it with both. The difference is scope.
In the Flow web interface, an admin describes in plain language what they want automated, from scratch or right after resolving an issue (“/automate”). Flow builds it. Those automations live on Flow, serve that team, and run through the Flow bot in Slack or Teams, or via API and MCP.
Describing an automation in plain language in Flow
Need automations or custom apps that span departments? Build them on ServiceNow using ToolSmith or Build Agent, where you can also describe what you want in plain language and have it generated for you. Those automations surface natively in EmployeeWorks, giving every employee one place to trigger them. For ServiceNow customers, this is the first choice.
Building an enterprise tool with ToolSmith
See the difference: onboarding a new hire
In Flow, an onboarding automation might provision Okta, Google Workspace, and Zoom access for a new hire, then let them know they’re ready to go. It saves the support team time and helps new people settle in fast, especially in smaller organizations without a web of systems and processes.
In EmployeeWorks, onboarding becomes a business process that starts at offer acceptance and runs through the employee’s first year in one intelligent workflow. The new hire enters personal information in Workday and ADP, enrolls in benefits through Workday or SAP SuccessFactors, signs post-hire paperwork in DocuSign, gets software access provisioned, completes a background check, and more. No manual handoffs. Mandatory training stays on track. And the new hire gets a first year that feels welcoming, not chaotic. For larger, more complex organizations, that end-to-end automation is a must.
A quick way to decide
The best-in-class front door for every employee, connected to ServiceNow IT Service Management and the rest of your business? That’s EmployeeWorks.
A simplified, full-stack service desk for one team that tracks and resolves its own work, with automations the team builds itself? Say hello to Flow.
Have both needs? Remember, it’s not either/or. Use both. Each does its own job, and they’re better together, whether you’ve run on ServiceNow for years or you’re just getting started.
