On 1 October 2026 ServiceNow launched Flow by ServiceNow, a standalone AI service desk that runs inside Slack and Microsoft Teams and can be live in a day. It is aimed at organisations that have never bought ServiceNow, which is a first for a company whose products usually arrive with an implementation project attached. We have been through the launch material and the early coverage, and this is how we read it.
What Flow is
Flow replaces the portal-and-ticket model with the chat conversation itself. An employee asks for something in Slack or Teams, Flow resolves it if it can, escalates it to a person if it cannot, and records what happened. When a request is resolved the right way, one click turns that resolution into an automation, so the next time the same request arrives Flow handles it on its own.
The claims that matter are about deployment. No infrastructure, no implementation project, no training for employees, running within a day. Flow was built as a separate product, a startup inside ServiceNow, rather than as a module on the platform, which is how it avoids the usual setup. It is connected to the ServiceNow AI Platform for audit and governance, so what Flow does is visible in the same place as the rest of your AI.
Commercially, Flow is sold on its own to organisations with no ServiceNow relationship, and existing customers on the AI-native SKUs can use it at no additional cost on consumption-based terms. It is in controlled availability now through letsflow.ai, with North America first, and general availability is expected in the fourth quarter of 2026 for North America and EMEA.
Who it is for
Three groups, in our view.
- Teams with no service desk tool. Smaller companies, or functions that have been running support out of a shared inbox and a spreadsheet. Flow gives them structure without a project.
- Business functions outside IT. Facilities, finance operations, marketing operations and the like, where a full ITSM rollout was never going to be justified but the requests are real and repetitive.
- Subsidiaries and acquired companies. Entities that will not be folded into the group platform for a year or two, and need something governed in the meantime.
There is a fourth, less obvious one: large ServiceNow customers who want a quick way to give a team a front door in Teams without touching their production ITSM configuration. Flow can be that, provided the escalation into ITSM is designed rather than left to chance.
What it is not
Flow is not a replacement for a governed ITSM estate. If you run change control against a CMDB, measure SLAs, have regulators who read your audit trail, or need incident, problem and change to talk to each other, you need the platform, not the chat layer in front of it. ServiceNow has been clear about that positioning and so are we. The right question is not “Flow or ITSM” but “which requests belong in Flow and how do they reach ITSM when they need to”.
Before you switch it on
A short checklist from our side.
- Decide the boundary. Which request types Flow owns end to end, which it hands to a human, and which it should not touch. Access requests that grant entitlements belong in the third group until you have seen how it behaves.
- Design the escalation. Where does a request go when Flow cannot resolve it: a person in the channel, a ticket in your ITSM instance, or both. Get the record created in ITSM with the conversation attached.
- Check your region. General availability for EMEA is planned for the fourth quarter. If you process personal data in the UK or EU, confirm where Flow runs before a pilot.
- Govern the automations. The one-click automation is the feature people will love and the one that needs a review step. Agree who can promote a resolution to an automation and how it gets undone.
- Register it. If you have AI Control Tower, Flow is another AI system in your estate. Put it in the register on day one.
Our view
Flow is a sensible move and probably a popular one. It takes the part of service management that most people experience, asking for help and getting it, and puts it where people already are. For the organisations it is aimed at, a day to deploy against months for a traditional tool is the whole argument.
For enterprises it is a useful addition rather than a change of direction. Use it to cover the teams your ITSM programme was never going to reach, connect it properly to the platform, and keep the governed processes where they are. We will update this article once we have run Flow for a customer and can say what the first weeks look like in practice.
If you are weighing it up, our ITSM team can help you decide the boundary and set up the escalation path.
