As of
Do employees still need an IT service portal?
Employees still need an IT service catalog, but not the portal of forms it was built as: in Slack and Teams, the catalog works best as policy over what your HR system already knows.
Ask an IT team where its requests come from and the portal is rarely the answer. People message the service desk in Slack, reply to an old email thread, or DM the one colleague in IT they know by name. The portal gets used for the things that refuse to work any other way.
Every chat-first vendor has noticed. Meeting employees in Slack or Teams is where everyone starts now, and this guide won't spend long on it. The Slack DM guide covers how to make chat a tracked front door.
The harder question is what happens to everything behind the portal. A service catalog isn't a web page. It's a set of decisions about what IT offers, who qualifies, who approves and what happens next. Those decisions still have to live somewhere, and they have to stay true when the organization changes underneath them.
Do employees still need an IT service portal when an AI agent answers in chat?
Not as the front door. Most employees will ask in Slack or Teams whatever you build, and an AI agent that answers there can handle requests without a portal visit. What they still need is the catalog behind it, kept accurate, and a web surface for the people who don't work in chat.
The ITIL guide covers why an employee should ask the agent rather than search for a form. This guide is about the catalog itself, because that's the part most chat-first approaches leave exactly where it was.
What the service catalog actually does
It's worth being fair to the catalog, because it does real work. Each item records something your organization decided:
- what IT offers, named in one place, so "can I get this?" has an answer
- who is entitled to it, usually by role, team, location or employment type
- which questions the request has to answer before anyone acts on it
- who approves it, in what order, and under what conditions
- what fulfillment does once it's approved, and who owns that step
That last list is the real catalog. The portal is just where employees were sent to read it.
An admin maintains all of this by hand. A typical service management platform keeps each item as its own record with its own form, its own picklists, its own approval chain and its own mapping of roles to entitlements. A hundred items means a hundred places where "Sales" is spelled out as a department, and a hundred places to change when Sales splits in two.
Why catalog forms go stale after a reorg
The catalog's facts are copies. The department picklist is a copy of the org chart as it stood when someone built the form. The approval chain is a copy of who managed whom. The entitlement rule that says account executives get a Sales Cloud seat is a copy of a title that may since have been renamed.
HR keeps the originals current because payroll depends on them. Nobody keeps the copies current, because nothing breaks loudly when they drift. Requests still get filed. Approvals still go somewhere. It just becomes the wrong somewhere, a little more each quarter, until a reorg makes it obvious all at once.
Picture a new customer success manager starting three weeks after a reorg moved her team out of Sales. HR had the new department and her manager in Workday on day one, but the Salesforce form's department picklist still ends at Support, so she picks Sales. The approval goes to the Sales VP, who has never heard of her, and she gets the seat days later from someone in IT she messaged directly, with no ticket behind it.
The forms have a second cost that gets less attention. Every field that asks an employee who their manager is, which office they sit in or whether they're a contractor is a question the organization has already answered. Asking again isn't neutral: the employee can get it wrong, and the approval then routes on their guess.
How an AI agent turns the catalog into policy
The useful move is to keep every decision the catalog made and stop storing it as forms.
An item becomes a policy written against attributes: everyone in Customer Success gets a Salesforce seat; contractors need a sponsor for anything that holds customer data; finance tools require the requester's manager to approve.
The form disappears because the agent already has its answers. When an employee asks for something, the agent reads who they are from the systems that own those facts: team and manager from HR, accounts from the identity provider, laptop from device management. It only asks what genuinely isn't known anywhere, such as which project the access is for or how long it's needed.
Approvals resolve the same way. The policy names a role, "the requester's manager" or "the data owner for this app", and the agent looks up who holds that role today. After a reorg, nobody edits an approval chain, because the chain was never written down as names.
What your admin maintains shrinks to the part that needs judgment: which policies exist, what they allow, and who handles the exceptions they can't decide.
When a portal still makes sense
Some people don't live in chat. Contractors may not have a Slack or Teams account. Warehouse and retail staff may share a device or work from a browser. Some employees simply like to see what's on offer before they ask.
For them, a web portal is still worth having. The point is that it reads from the same policies as the chat channels. An employee should get the same answer, the same approver and the same record whether they asked in Teams or in a browser. Two front doors with two rulebooks is how the catalog drifted in the first place.
How STLabs runs the catalog as policy
STLabs is built for the catalog to live as policy, which is what AI-native service management means in practice for this part of the work.
Axiom™, the live model of your organization, connects to your HR system, identity provider and device management and keeps each person's team, reporting line, devices and access current as those systems change. Every fact records which system it came from and when it was observed. That's what lets the agent skip the form: it already knows what the form would ask.
Your team writes rules once in Policies & Approvals. A policy can allow a request, block it or require approval, and the workflow waits for the decision before it acts. The same rulebook applies in Slack, Teams and the web portal. Fulfillment runs as Workflows, described in plain language and versioned, and every decision is logged with the rule applied, the approver and the time.
Employees ask through Employee Self-Service in their own words. In Slack, "My Requests" shows everything they've asked for and where it stands. On the Growth plan and up, Access Lifecycle also adjusts access when someone changes roles, so many requests never need to be made.
In practice, a person who moved teams last week types "I need Salesforce" in Teams. Axiom™ already has them on the new team under the new manager, the policy for that team decides, and the request either completes or goes to the right approver, with the rule that decided it on the record.
How to test your catalog on your own systems
Pick the team that moved most recently in a reorg. Then try three things.
Request a common item as someone on that team, through your portal, and note every field you're asked to fill in. For each one, check whether your HR system or identity provider already holds the answer.
Follow the approval. Does it reach the person who manages the requester today, or the one the item was configured for?
Finally, open the item's configuration and count how many places name a department, a title or a person. Each is a copy that someone has to update at the next reorg. If that number is large, the work to do is in the catalog, whatever sits in front of it.
Keep what the catalog decides, drop what it asks
None of this needs a big switch. STLabs runs alongside the service desk you already run, and teams go from integration to results in five days, so you can move one catalog item at a time and see it hold through the next org change. The plan is in Moving to STLabs from your current service desk.
Keep every decision your catalog encodes. Stop asking employees to repeat what HR already told you. A catalog should know who's asking before they say a word.
Frequently asked questions
Do employees still need an ITSM self-service portal?
Most employees prefer to ask in Slack or Teams. A web portal is still useful for people without chat access, as long as it applies the same policies as the chat channels.
What happens to the IT service catalog without a portal?
The catalog's decisions stay: what IT offers, who qualifies and who approves. They work best written as policies over HR attributes, so they stay accurate after a reorg without anyone editing forms.
How do we track IT requests made in Slack or Teams?
Every request should become a record with an owner, whichever channel it came from. STLabs logs every decision with the rule applied, the approver and the time, and employees can see their requests under "My Requests" in Slack.
What about employees who don't use Slack or Teams?
Give them a web portal that reads from the same policies. STLabs applies one rulebook in Slack, Teams and the web portal, so the answer and approver are the same everywhere.