Part of
Enterprise AI chatbot
Implementation

Internal Chatbots for IT and HR Service Desks: What to Automate and What to Route

Employees ask in Slack or Microsoft Teams; one agent workflow handles password resets, access requests and HR policy questions for the IT and HR desks.

An internal chatbot on your IT and HR service desks can resolve the requests that follow a written rule. That covers password resets through your identity provider's own reset flow, access requests routed to the right approver, and ticket and incident status. It also covers how-to answers from your runbooks, and HR policy questions answered from the current handbook with the section cited. Some requests should reach a person, with the conversation attached: anything that changes how someone signs in, concerns one employee's case, or needs a manager's judgment.

Both desks carry risks a customer chatbot does not. The IT help desk is a known attack route. In their Scattered Spider advisory, first published in November 2023 and updated in July 2025, CISA and the FBI describe how it works. Attackers use social engineering to trick IT help desk staff into resetting passwords and multi-factor authentication (MFA) tokens. They then take over accounts in single sign-on environments. On the HR side, employees act on what they are told about leave, pay and benefits, and some of what they bring is confidential. HR leaders still want a chatbot. Gartner surveyed 179 HR leaders in January 2024, and the generative AI use case they prioritized most, at 43%, was an employee-facing chatbot for HR service delivery.

What can an IT help desk chatbot resolve on its own?

An IT help desk chatbot can resolve a request on its own when the fix runs through a system that already enforces your rules. It reads the ticket, the incident list or the runbook. It hands identity work, such as a password reset, to the identity provider instead of doing it itself.

RequestWhat the chatbot doesResolves alone?
Password resetHands over to your identity provider's self-service resetYes, through that flow only
New phone or MFA resetOpens a ticket for a person to verify identityNo
Software or system accessCreates the request and routes it to the approverAfter approval
Ticket or incident statusReads your ticket queue and open incidentsYes
How-to and known issuesAnswers from runbooks, with the page linkedYes, when it is documented
Device or network faultCollects the details, runs set checks, files the ticketPrepares the ticket

Password resets show how this works. Once users have registered their authentication methods, Microsoft Entra ID's self-service password reset lets them reset their own password without an administrator or the help desk. Okta offers the same as self-service account recovery. The chatbot sends the employee into that flow and confirms the result, so the identity checks stay in the system built to run them. If the agent itself runs on Azure, we build it as one of the Foundry agents that act under Entra ID. Azure role-based access then decides who can build, run and read it.

HR chatbot use cases: what it can answer and what must reach a person

An HR chatbot works from three sources: the handbook, the employee's own record and the processes HR already runs. It can answer a policy question and cite the section and its effective date. It can read the asker's leave balance from the HR system. It can also start a process, such as an address change or an onboarding checklist. Our guide to building a knowledge base chatbot your employees will use covers the handbook side in detail.

It should not answer questions about one person's situation that need judgment. That means a complaint, a medical matter, a disciplinary step, a pay dispute or anything about another employee. For those, the chatbot stops answering and tells the employee who will contact them and how. It sends the message to a case queue only HR can read. That queue must be separate from the IT ticket system. Otherwise every service desk agent can read a complaint about a manager. Our AI for HR page covers the onboarding and policy agents in-house HR teams start with.

Why identity checks come before automation

A message from a signed-in Slack or Teams account proves which account sent it. It does not prove who is typing, because an attacker who controls the account can send the same message. So an internal chatbot can use that sign-in to read the asker's own records and file requests. It never changes a sign-in method, a recovery phone or an email address because a chat asked it to. Those changes go to your identity provider's flow, or to a person following your recovery procedure. The identity check then runs in a procedure built for it, outside the chat window.

Pick a request to see where it goes, what identity check applies and where it is logged.

Pick a request
Where does this service desk request go?
What the chatbot does

Identity check

Where it is logged

Chatbot
  • Forgot password (IT): resolves in the chat. Hands over to your identity provider's own reset flow.
  • New phone, reset MFA (IT): goes to a person. Opens a ticket for the service desk.
  • Salesforce access (IT): resolves after approval. Creates the request and routes it to the approver.
  • Is the VPN down? (IT): resolves in the chat. Reads open incidents and adds you to the right one.
  • Days off left (HR): resolves in the chat. Reads the asker's own record in the HR system.
  • Parental leave policy (HR): resolves in the chat. Answers from the current handbook for that country, with the section cited.
  • Report a manager (HR): goes to a person. Stops answering and passes the message to the HR case queue.
Illustrative requests and replies. The chatbot never changes a sign-in method or recovery detail on the strength of a chat message, and HR cases never enter the IT ticket queue.

Approval is the other control. The chatbot can create an access request on its own, but access is granted only after the approver named in your policy says yes. Each step is logged with the request, the records read and the approver. An auditor can then trace any access back to a decision. Our enterprise AI governance page lists the controls we build into these systems.

How an internal chatbot connects to Slack, Teams and your service desk

Employees reach the chatbot where they already work: a direct message in Slack or a chat in Microsoft Teams. Behind that chat, one agent workflow decides whether a request belongs to IT or HR. It then reads only what that request type needs.

We build these on self-hosted n8n in your cloud, behind your own sign-in, so documents, logs and run history stay in your environment. When a task calls a hosted AI model, the provider receives only the fields that task needs, under your own agreement with that provider. Where your data rules allow no outside call at all, a model you host does the work instead. IES Limited already receives its daily MI alerts as cards in Microsoft Teams, sent to six audiences by brand and sensitivity. An internal chatbot uses the same delivery path. The IES daily MI alerting case shows that build.

Does an internal chatbot work in every language your staff use?

It can, but answer quality can differ by language, so test each one. NIST's Generative AI Profile (NIST AI 600-1, July 2024) notes that a large language model may perform less well in languages other than English, or in certain dialects. It adds that groups who get the weaker results can end up worse off than if no AI system were used. For an HR chatbot, that means an employee in one country can get a weaker answer about the same leave policy than a colleague in another.

Two steps reduce that gap. First, keep a handbook source per country and tag each document with its country and effective date. The chatbot then answers a Dutch employee from the Dutch policy. Second, before launch, test every language you support with the same set of real questions, and score each language separately. Pinkcube's chat agent answers customers in Dutch or English, and it was scored on 76 test scenarios before any customer saw it. The Pinkcube case shows how the imperfect scores became rules.

What to measure after an IT or HR chatbot goes live

NIST AI 800-4, published in March 2026, documents how hard it is to monitor AI systems after they go live. It sorts the work into six areas, including functionality, security, compliance and human factors. Our guide to enterprise AI agents in production lists all six. For a service desk chatbot, a short set of numbers covers most of it.

  • Resolved without a ticket, by request type and by language.
  • Reopened or repeated requests, where the employee came back about the same issue within a week.
  • Handoffs and why, so you can see which request types need a rule, a document or a person.
  • Questions with no source, which tell HR and IT which pages to write next.
  • Answers marked wrong by employees or by your reviewers, each traced to the document it came from.

Log enough to answer those questions and no more, and keep HR case content out of the general logs. The team that owns the rules should be able to change them without a developer. At IES, the finance team adjusted its own alert thresholds 34 times in six weeks without a single developer ticket. The same applies when HR changes a leave policy or IT adds a request type. If you would rather not run the system yourself, AI managed services covers monitoring after launch.

How to roll out an internal chatbot for IT and HR

  1. Export three months of IT tickets and HR inbox questions, and sort them by request type.
  2. Mark each type: answer from a document, read a record, act with approval, or person only.
  3. Name the owner of every source the chatbot will read, starting with the handbook and the runbooks.
  4. Agree the identity rules with security before the build: what a signed-in account may do, and which requests always go to your recovery procedure.
  5. Set up the HR case queue as a separate destination with HR-only access.
  6. Prove the top request types on your own systems in a pilot, then launch in Slack or Teams for one department.
  7. Measure the numbers above every week, and add request types as they hold up.

The automation ROI calculator turns the hours your desks spend on those request types into a payback month. For the wider set of use cases past the service desk, see our article on enterprise chatbot use cases that go beyond FAQ answers. To weigh workplace suites, helpdesk AI agents and custom builds against each other, see enterprise AI chatbot platforms compared.

Frequently asked questions

What is an IT help desk chatbot?

An IT help desk chatbot answers employees in Slack or Teams and resolves routine requests through your systems. These include password resets through your identity provider, access requests routed for approval, and ticket or incident status. It files a complete ticket for anything it cannot resolve.

Can a chatbot reset passwords safely?

Yes, when it hands the employee to your identity provider's own self-service reset, such as Microsoft Entra ID's or Okta's, and does not reset the password itself. A person following your recovery procedure should handle resets of MFA devices and recovery details. Tricking the help desk into those changes is a documented attack route.

Can an HR chatbot see employee data?

It should see only the record of the employee who is asking, read through the HR system with that employee's permissions. Questions about another person, a complaint or a medical matter go to a named HR person through a case queue only HR can read.

Should IT and HR share one internal chatbot?

Yes, as long as IT and HR requests go to separate queues with separate permissions. One chat in Slack or Teams is easier for employees. The chatbot decides which desk a request belongs to before it reads anything.

How long does it take to build an internal service desk chatbot?

An AI pilot takes 2 to 6 weeks. It builds a working prototype on your own staging systems and ends in a go or no-go report on accuracy, response time (latency) and cost. The production timeline depends on how many systems the chatbot reads from and writes to. We scope it with you before you commit.

To see how we build chatbots that work inside your own systems, read about our enterprise AI chatbot builds. You can also book a discovery call and bring last quarter's ticket export.

More on this topic

Put your first workflow on the board

Answer a few questions about your team and what you want automated, then a senior partner scopes it with you on the call.