- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Fully absorbed. Loving the work. Energized focus. That’s a flow state of mind.
Flow by ServiceNow is a conversational AI service desk that automatically resolves employee requests through conversation, directly inside Slack, Microsoft Teams, and email. Remove the burden from employees, because it was never about the ticket. It was always about the service. Portals, queues, and forms were a means to an end. Employees ask, and Flow answers or acts, in the same thread where the question came up.
Why this exists
Every service team has a version of the same story: employees want instant answers, but high volume and constant interruptions hold you back. You can solve most things, and have even documented how to, but you can’t (yet) clone yourself.
Flow gives any team a working service desk in a day, from a lean IT shop to a satellite department at a much larger company. Connect single sign-on, point Flow at your collaboration tool, connect your knowledge, and start resolving requests. When a request repeats, describe the fix in plain language and Flow builds the automation.
How it works
Flow joins the channels employees already use. They can raise a request in a Slack or Teams channel, message Flow directly, or send an email, and Flow resolves it using your connected knowledge or hands it to an agent when it's complex or sensitive. Your other bots and AI assistants can reach Flow the same way, over APIs or MCP.
Four contexts, one AI
Flow is built to be useful to employees and to the service desk team running it. The same AI shows up differently depending on the job in front of it:
|
Context |
What it does |
|
Answers employees directly in chat |
Uses connected knowledge so the answer is accurate from the first request |
|
Takes action, not just points to an article |
Does what a request actually needs instead of only finding a knowledge article |
|
Turns plain language into automations |
Describe a repeat request and Flow builds it, no developer or admin required |
|
Watches how the team runs Flow |
Looks at how a team is using Flow to surface what's worth automating next |
Tell me what you want. What you really, really want… to automate. Your teams know how to resolve many requests and have probably even documented it. The shortfall is usually not knowledge but follow-through, whether service teams are too busy or AI doesn't have all the pieces it needs to act. This is the gap that context closes.
We’re rolling out Flow in stages and here’s what one early trial customer had to say:
"We're a small team building solutions on ServiceNow and moving fast every day. We want to maximize the time we spend solving customer needs and minimize how much effort we spend on internal IT, HR, and other operational tasks. In the past, we often had to search across numerous locations for answers. Flow turns all of our data into one conversational interface so our team asks for help in Slack and gets answers instantly. It's how we scale knowledge with a lean team." - Peter Oneppo, Co-Founder & CEO, Serenity EHS, Inc.
FAQ
Is Flow just a chatbot?
No, Flow is not just a chatbot. Flow is a full-stack ITSM that helps IT resolve incidents and requests by acting inside your connected systems and building automations for repeat requests. Flow also helps your employees by sourcing knowledge and answering requests directly in chat.
Does Flow replace ServiceNow ITSM?
No. Flow is a standalone service desk built for speed and simplicity in Slack, Teams, and email. Customers who need change management, problem management, or a CMDB-driven process stay on ITSM, and existing customers can run both side by side.
Do I need a ServiceNow instance to use Flow?
No. Flow runs as a standalone product on its own multi-tenant cloud architecture. Existing ServiceNow customers can connect Flow to their instance for bidirectional sync, but it isn't required to get started.
Which channels does Flow support?
For employees, Slack, Microsoft Teams, and email all resolve the same way. For the admin, Flow centralizes requests and incidents into a single queue they access online. Admins respond from this single interface and Flow posts their response in the channel they choose.
Can automations run without a chat message starting them?
Yes. A published automation can also start from a schedule, a webhook, an API call, or an event in a connected system, not just a chat message.
How long does it take to get Flow running?
Flow deploys instantly and can be live in less than a day: connect single sign-on, connect your workspace, connect your knowledge, and start resolving requests. The delay often comes with the connections if the person setting up Flow isn’t also the admin of those various systems.
How much does Flow cost?
Flow starts with a free trial for everyone with no upfront credit card required. There are two paths from there. Existing ServiceNow customers run Flow on Assists they already own or purchase from their account team or partner. For new customers, credits are purchased directly with a credit card in the product. There is a $10k annual minimum commit. Each conversation consumes $2 (or 10 Assists) whether it results in an automation. Automations consume $1 (or 5 Assists).
Flow state is the absence of distractions. Here's how you get there:
-
Request trial access. Sign up for a Flow first look
- Hear more from the team. Click here to join the Flow Community
- Stay up to date. For the latest, visit letsflow.ai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.