The shared inbox has been doing the job of a service desk for years.

A busy Slack channel. An email address everyone knows. A spreadsheet someone built a long time ago and nobody quite wants to touch.

And for a while, it works.

Then the team grows. The same questions keep coming back. The people who know where everything lives become the bottleneck.

For a lot of organisations, ServiceNow has always looked like the right answer to a problem that felt too small for it. Too much platform, too much project, too much before anything actually changed for the person asking for help.

Flow changes that.

What is Flow by ServiceNow?

Flow by ServiceNow is a conversational AI service desk that works where people already ask for help: Slack, Microsoft Teams and email.

An employee asks a question in chat. Flow answers from the knowledge you already have, runs an automation when one exists, and hands the conversation to a person when it should.

No portal. No form. No need to explain the problem twice.

What strikes me most is what Flow leaves out.

ServiceNow says no CMDB, no ITIL alignment and no knowledge migration are needed to get started. No new infrastructure. No traditional implementation programme before people can begin using it.

ServiceNow says Flow can be live in a day.

Who is Flow by ServiceNow for?

When we put our Flow guide together, five conversations kept coming up:

• “We're a small team with no service desk.” Support runs on goodwill, a shared inbox and the people who happen to know the answer.
• “We've never bought ServiceNow. It looked too heavy.” Flow can run as a standalone product, with no existing ServiceNow instance needed.
• “ServiceNow was too expensive for us.” Flow starts from a much lower commitment, with pricing based around conversations and automation usage rather than traditional seat-based licensing.
• “Our acquired team needs its own help desk, fast.” For existing ServiceNow customers, Flow can sit alongside the platform as a faster way in, rather than replacing what already works.
• “Can it help teams beyond IT?” Flow is built for IT today, with more teams planned.

If any of those sound familiar, Flow is worth a serious look.

How much does Flow by ServiceNow cost?

Flow is priced on what gets used, not on seats.

For organisations new to ServiceNow, the published model starts with a 30-day free trial, with no credit card required.

After that, the annual commitment starts at $10K, with usage charged at $2 per conversation and $1 per standalone automation run. Additional capacity can be added in $1K top-ups.

For existing ServiceNow customers, Flow can use ServiceNow AI credits, or Assists, depending on what you already own.

That means 10 Assists per conversation and 5 Assists per standalone automation run.

Some customers may need additional Assist capacity depending on expected usage.

These are ServiceNow's published prices in US dollars and are worth confirming when you request access.

The important part is the model.

Start with a defined set of requests and let spend follow real usage.

The question has changed

For years, the first question for a smaller organisation was whether ServiceNow was realistic at all.

Flow changes that question.

Now it is: where should you start?

That sounds simpler, and it is. But it is still worth thinking about before you switch anything on.

Which requests should Flow handle first? What should it be allowed to do on its own? Where should a person always stay involved? And what will your usage — and therefore your bill — actually look like?

The teams that answer those questions upfront will get more from the speed Flow promises.

The ones that don't may still get live quickly, then spend the next quarter working out what they should have decided at the beginning.

Flow is built to be easy. We help you start in the right place.

Flow is currently in controlled availability, with general availability for North America and EMEA expected in Q4 2026. Access is being confirmed customer by customer.

As a ServiceNow Elite Partner, Crossfuze can help with the bit that comes before launch.

Where should you start?
Pick the requests worth tackling first.

What will it cost?
Estimate conversations, automation runs and Assist usage before you commit.

What does Flow need access to?
Work out the knowledge, tools and integrations it needs from day one.

How do you get live?
Get the subscription, capacity and setup right before employees start using it.

We've written a short guide, Meet Flow by ServiceNow, covering what Flow does, who it fits, what it costs and where to start.

Read the Flow by ServiceNow guide >

Request early access →

If your service desk is still an inbox, this is the moment to change that.

‍

‍