Friends don’t make friends fill out a form: how Flow resolves requests where work happens

[LinnieNow]

Something breaks. You don’t go hunting for a form. You DM the person responsible for IT, “Hey, my VPN isn’t working.” Or you ask ChatGPT, “How do I reset my VPN?” That’s how people actually ask for help. Most IT service desks answer with a service catalog. Pick a category. Fill in the fields. Wait.

That gap is changing how IT teams buy, too. They want an AI service desk that resolves requests inside the tools employees already use, without a long procurement cycle or implementation project. Enter Flow by ServiceNow: a conversational AI service desk that resolves employee requests in Slack, Microsoft Teams, and email. No catalog. No forms. No dropdowns. Up and running in a day.

The real friction isn’t the ticket. It’s the form.

Ticket deflection dashboards track volume. They miss the time employees waste hunting for the right catalog item. They miss the fields left blank or incorrect data because nobody knew what the form wanted.

That’s the hidden cost. Employees do the translation work, turning a simple ask into a form’s structure, before IT even sees the request. What if employees just said what they needed, in plain language?

A quick primer: most companies run IT help through an IT service management (ITSM) platform. IT configures a service catalog inside it, a menu of request types, each with its own form and workflow. Employees find the right item, fill it out, and the request routes to the right team. For large organizations with complex workflows and many teams, that structure, and the underlying common service data model (CSDM), keeps work organized and governed.

Here’s how the two compare

	Enterprise ITSM platform	Flow by ServiceNow
Built for	Large organizations with complex workflows, many teams, and strict data governance	Organizations and teams that want a simple deployment and fast answers to everyday requests, in chat or email
How IT sets it up	Deploys on-prem, in cloud, or hybrid. Centralizes knowledge on a single platform. Configures a service catalog of request types, forms, and approval workflows	Headless, cloud-based, and platform-agnostic. Connects instantly to any knowledge source and business app, then installs from Slack or Microsoft Teams stores
How employees ask for help	Find the right catalog item in a portal and fill out its form	Send Flow a direct message in chat, or just ask in the support channel where Flow is deployed
What happens next	Workflows route the request to the right team’s queue to be resolved and closed.	Flow resolves it in the thread, or hands off with context and helps IT find the solution, and automate it for next time
What’s left behind	A ticket with a full record of the request	A conversation record: reference number, status, full history

Some work calls for enterprise ITSM. Some just needs a conversation. The right partner offers both to meet current and future requirements.

Ticketless sounds good, but doesn’t IT still need a record of the work?

Yes. Skipping the form doesn’t mean skipping the record. Every Flow conversation gets a reference number, a status, and a full history. IT sees it all in the Flow analytics dashboard for auditing and reporting. Already have an enterprise ITSM solution? Records sync both ways, so your audit trail and SLA tracking stay intact.

The real difference is who does the data entry. With a form, the employee does it. With Flow, the conversation becomes the record. Employees just talk. Flow takes the notes.

What this looks like in practice

Request, in plain language	What Flow does
“Reset my VPN access”	Runs the VPN reset automation IT set up, within the guardrails IT defined. Confirms in the same thread.
“I need access to Figma”	Checks the request against IT’s access rules. Grants access or routes it for approval. No catalog item required.
“What’s the status of my ticket?”	Pulls the current status from Flow or a connected ticketing system. Replies in the same thread.

No catalog. No category. No fields. Just a conversation, and a record in the queue IT already works from.

FAQ

Does skipping the form mean IT loses the paper trail?

No. Every request still becomes a record, with a reference number, status, and full history, in the queue IT already uses for auditing and reporting. Connect Flow to an existing ServiceNow instance and that record syncs both ways, keeping your audit trail and SLA tracking intact.

Isn’t a catalog just how IT keeps requests organized?

It’s one way, and it works by asking employees to do the categorizing instead of IT. Flow by ServiceNow asks what someone needs once, in plain language, and either resolves it or hands it off to a person with the details already collected, so nobody has to start over.

How is this different from an AI-native tool that also skips the ticket?

Conversational resolution looks similar on the surface. The difference is what sits underneath: Flow is built and backed by ServiceNow’s own service management depth, rather than a chat layer built on top of a customer’s existing ServiceNow data from outside it.

 

Do I have to replace my existing ticketing system to try this?

No. Flow is headless, meaning it layers on top of the systems you already use rather than asking you to migrate off them. For existing ServiceNow customers, it connects bidirectionally. Try it free for 30 days, no credit card required.

What happens if Flow can’t resolve a request on its own?

It hands off to the right person with a conversation record of everything collected so far, so they start with context instead of asking the employee to repeat themselves.

That’s the real shift. Not fewer tickets. Fewer forms. The request still gets a record. The employee just never fills one out. Want the full tour? Explore the Flow experience on Community.