
Rizwan Z. | Nov 18, 2026 | 8 min
For twenty years, getting help at work has meant learning how the help desk thinks: open a portal, pick a category, fill in the fields, wait. Flow by ServiceNow, launched on October 1, 2026, drops that model. The employee asks in a Teams or Slack conversation, and that conversation becomes the service desk.
Flow can be running within a day, with no implementation project and no infrastructure. It answers and closes the requests it can, and passes the rest to a person.
Flow by ServiceNow is a standalone, conversational AI service desk for employee requests. It isn't limited to IT: HR, legal or any team that fields requests can use it.
Flow is built and backed by ServiceNow but runs on its own standalone architecture. It moves at its own pace and is designed for teams that want a dedicated service desk without committing to the full platform. Flow operates as a startup within ServiceNow, run as a separate business unit.
Employees make a request or raise an issue in chat. There's no portal, no form and no new interface to learn. Flow answers from your knowledge base in the same thread, and when an automation exists for the request, it runs it.
Employees can ask for help in Slack, Microsoft Teams, email or a Flow web app. Agents reply from Flow to whichever channel the request came from. Flow answers everyone in a shared thread, so a support channel with several people asking at once still gets one consistent service.
Other bots and AI assistants can send requests to Flow over MCP and APIs. A company already running its own internal assistant can hand service requests to Flow rather than rebuilding them.
Building an automation doesn't need a developer or a sprint. Admins set the safeguards up front, and anyone working within them can build. To create an automation:
Create. Describe how the automation should work in plain language, and Flow builds it.
Adjust. Review each step and change what you need, so you keep full control of what goes live.
Test. Run the automation in simulation or a sub-production environment before publishing it.
Automations usually come from requests that have already been solved. Once someone resolves a request correctly, they can automate it with one click, and Flow handles the next identical request without anyone writing a knowledge article.
Flow's AI serves both employees and service desk agents, and admins can adjust how it behaves for each team:
Helper: answers employee questions in chat.
Resolver: helps agents close requests.
Builder: creates automations.
Service desk coach: shows the team how to get more from Flow.
Flow connects to more than 100 tools out of the box. You can link the systems that hold identity, knowledge, assets or tickets without a knowledge migration or a CMDB. Each connection stays limited to the team that needs it.
For ServiceNow customers, a two-way sync covers tickets, assets, knowledge and Assists, so records stay accurate and traceable on the instance.
Flow tracks request volume, the share of requests employees resolved themselves, and resolution time. It flags repeat requests as candidates for an automation or a new knowledge article. It also reports on its own work the way it reports on any team member's, so you can compare its output side by side with your agents.
One admin sets Flow up in four steps:
Invite teammates individually, or connect company sign-on to add everyone at once.
Add Flow to Slack or Microsoft Teams. It joins the support channels employees already use, and employees can also message Flow directly.
Connect knowledge, asset and ticketing sources for context, plus any apps Flow should automate.
Start resolving requests. Flow takes the first pass within limits set by the admin and passes complex or sensitive issues to human agents.
No. New customers can buy and start using Flow directly, with no existing ServiceNow relationship and no platform prerequisite.
Organisations that already run ServiceNow connect Flow to their instance through an OAuth connection set up on the ServiceNow side. Only the team using Flow changes how it works; the rest of the organisation carries on as normal.
Flow is free to try for 30 days, with no credit card required. After that, you pay for usage.
New customers:
$2 per conversation.
$1 per automation run.
A $10K annual commitment that renews each year, with $1K top-ups available.
You can buy inside the product with a credit card or through a sales rep.
Existing ServiceNow customers pay with Assists, the AI credits they already own:
10 Assists per conversation.
5 Assists per automation run.
There's no extra product to buy and no procurement cycle.
What counts as usage:
A conversation is a single issue, handled by AI or by a person, and charged once. Any automation that runs inside the conversation is free.
An automation run is charged only when an automation is triggered outside an employee conversation, for example by MCP, an API or another agent.
What this means for budgeting:
Flow charges per conversation, not per resolution. An issue a person handles costs the same as one Flow resolves alone.
Work out the minimum before you commit. At $2 per conversation, the $10K minimum covers 5,000 conversations a year, or roughly 420 a month. A small team below that level pays for capacity it doesn't use. A large team well above it should model expected volume first, since a successful rollout costs more as usage grows.
Existing customers should run the same calculation against their Assist balance, because Flow draws from the same pool as their other AI features.
Flow launched in controlled availability. Anyone can sign up at letsflow.ai for updates and early access to the free trial.
Now: existing ServiceNow customers in North America can use Flow, and North American customers got priority access in the first weeks.
Q4 2026: general availability is expected in North America and EMEA.
Q1 2027: wider availability in other regions is expected to follow.
Regional hosting and data residency details for Flow aren't public yet. If your policies set where employee data can be stored or processed, raise that question during early access, before any personal data goes through the trial.
A 200-person company handling support through Slack messages and spreadsheets is a typical Flow customer. So is a satellite team inside a 10,000-person enterprise that can't wait three months for the platform team.
For organisations that already run full ITSM, Flow suits specific departments, remote teams or recently acquired business units. These are teams that need to be up and running quickly, or that prefer a different way of working. For groups that operate in several countries and keep acquiring companies, that last case is the most practical one.
Early Flow customers include:
CFO Advisors, which runs dedicated Slack channels with its clients and uses Flow to answer them in those shared channels, so its finance support can scale without switching tools.
Serenity EHS and VividCharts, two small teams that use Flow to answer internal questions in Slack from what they've already documented.
The US Navy's Fleet Numerical Meteorology and Oceanography Center, which sees potential for users to build workflows directly in Microsoft Teams.
Where the service desk is part of how the enterprise is governed, with change control, service mapping and dependency data behind every request, Flow is the wrong tool. It handles conversations and automations for one team. It isn't an enterprise system of record.
Three ServiceNow products now offer chat-based employee support, and they differ in scope:
ServiceNow EmployeeWorks is the front door for the whole workforce. It routes requests across IT, HR, finance and other departments into the ServiceNow platform.
Flow is a complete service desk for one team. It tracks and resolves its own requests.
ServiceNow ITSM is the enterprise system of record, built on the CMDB, ITIL processes and one data model across the organisation.
A large ServiceNow customer can run all three: EmployeeWorks as the enterprise-wide front door, ITSM as the system of record, and Flow for the team that needs its own desk this week.
Flow's closest competitors are chat-first service desks such as Atomicwork, Console and Serval. Salesforce's Agentforce IT Service also answers employee requests inside Slack and Teams.
Three things set Flow apart:
No platform needed. It runs without a ServiceNow instance, but connects to one through a two-way sync when an organisation already has it.
Usage pricing. It's billed per conversation and per automation run, not per seat.
Open to other AI tools. Other bots and AI assistants can hand work to it over MCP and APIs.
The chat experience alone won't separate these products. The deciding question is whether a service desk can reliably carry a request through permissions, approvals and handoffs across systems. That is also where ServiceNow's long history with workflows should give Flow an advantage over newer competitors.
Where data is processed. Ask where conversations, connected knowledge and automation logs are stored and processed, and whether that matches your data protection obligations.
Knowledge quality. Flow answers from what you connect. Outdated policy pages will produce outdated answers, quickly and confidently, in the same thread where the employee asked. Review your top twenty request topics before connecting their sources.
Escalation rules. Decide which requests Flow must always hand to a person, such as anything involving payroll, legal matters or personal data, and set those limits on day one.
Ownership of the sync. For ServiceNow customers, decide who owns the connection, which records sync, and how Flow automations relate to the workflows already running on the platform.
Your usage forecast. Count last quarter's requests for the team you plan to start with. That one number tells you whether the $10K minimum or your Assist balance fits.
What is Flow by ServiceNow?
A standalone, conversational AI service desk launched on October 1, 2026. It answers and automates employee requests in Microsoft Teams, Slack, email and a web app.
Is Flow by ServiceNow free?
Only for the 30-day trial. Ongoing use is billed per conversation and per automation run.
Does Flow work in Microsoft Teams?
Yes. Flow joins the Teams channels employees already use, and employees can also message it directly.
Do I need a ServiceNow instance to use Flow?
No. Flow works on its own, and existing ServiceNow customers can connect it to their instance.
When will Flow be available in EMEA?
General availability for North America and EMEA is expected in Q4 2026.
Is Flow the same as Flow Designer?
No. Flow Designer is the low-code workflow builder inside the ServiceNow platform. Flow by ServiceNow is a separate product with its own architecture and pricing.
Does Flow replace ServiceNow ITSM?
No. Flow serves one team's requests. ITSM remains the enterprise system of record for organisations that need the CMDB, ITIL processes and change control.
EnableNow works with ServiceNow customers across Europe and the Middle East. Flow raises practical questions for that work: which teams should run on it, how it should connect to an existing instance, and how its automations fit with the workflows already in place. If you're weighing that up, we're happy to talk it through.

Rizwan Z. • Nov 12, 2026 • 8 min
Read full article→

Rizwan Z. • Nov 05, 2026 • 10 min
Read full article→

Rizwan Z. • Oct 21, 2026 • 10 min
Read full article→
Let EnableNow help you modernize workflows, strengthen performance, and unlock measurable value across your ServiceNow platform.