Every HR vendor now ships a box that talks. The words on the box are “AI”, “copilot”, or, this year, “agent.” Buyers searching “HR chatbot vs agent” or “agentic HR vs copilot” are trying to tell those boxes apart before a demo wastes a quarter. The distinction is not branding. It is whether the software suggests, or whether it reads, acts, and continues.
This page stays on that distinction. It mentions typical chatbot- and copilot-class players only in passing (Workday Illuminate, Microsoft Copilot-class HR assistants, generic HR helpdesk bots) without inventing features they have not published. Kumo claims are limited to /agentic-hr-employee, /intelligence, and the rest of the public site. For the named 2026 field, use the field guide.
Three jobs that get sold as one word
An HR chatbot answers questions in a chat window. It retrieves a policy paragraph, a holiday balance, or a “how do I…” article. When the window closes, you still run hiring, leave, pay, and reviews. Generic HR helpdesk bots live here. They are useful. They are not employees.
An HR copilot sits beside a system of record and suggests the next click or drafts a paragraph. You remain the operator. Microsoft Copilot-class HR assistants (Copilot in Microsoft 365 talking to HR content, or Copilot-style panes inside an HCM) belong in this bucket unless a public page shows them owning the workflow. Workday Illuminate, on Workday’s own newsroom, is “the next generation of Workday AI”: purpose-built agents and self-service inside Workday, not a new People OS. Treat Illuminate as the in-suite assistant / agent layer of an HCM you already run.
An agentic HR employee takes a goal, plans the work, uses tools, looks at what the last tool actually returned, and continues the mission. Sensitive steps wait for a human. The log shows what happened. That is a colleague, not a feature. Kumo’s name for that colleague is Kumo HR Agent 2.0.
Suggest versus read-act-continue
Suggestion is cheap to demo. Paste a job description, get a rewrite. Ask “what is our parental leave?”, get a paragraph. The operator still opens the HRIS, still screens the CV, still chases the contract, still publishes the policy.
Read-act-continue is a loop. The software opens the file. It reads a CV against the role you opened, not a keyword cloud (see AI CV screening). It reads a contract as a first-pass HR checklist. Kumo is explicit: this is not legal certification and does not replace counsel. It reads a policy against gaps. Then it calls a tool, looks at the real result, and decides the next move. If the result was wrong, the plan changes. When the mission is done, it files an artifact and leaves a trail.
If a vendor cannot show that loop (document in, tool result in, next step out), you are looking at a chatbot or a copilot, even if the homepage says “agentic.”
| Approach | What it does | What you still do |
|---|---|---|
| HR chatbot | Answers questions in a chat window | You still run hiring, leave, pay, and reviews |
| HR copilot | Suggests the next click or drafts a paragraph | You still operate the HRIS, screen by screen |
| Helpdesk / service bot | Deflects tickets; sometimes opens a case | Someone still owns the workflow behind the ticket |
| Kumo HR Agent 2.0 | Plans the mission, reads the documents, runs the tools, keeps going | You confirm sensitive steps. The full log is yours. |
Players you will hear in the same breath
Workday Illuminate shows up because Workday is the HCM many enterprises already run. Public Workday pages describe Illuminate agents for HR and finance, an Agent System of Record, and self-service / case agents that work inside Workday. That is copilot-to-agent territory on a system of record, not proof that you no longer need operators. Deeper comparison: Kumo vs Workday.
Microsoft Copilot-class HR assistants show up because employees already live in Outlook, Teams, and SharePoint. They are strong at asking and drafting against content the tenant already holds. They are not, on any public Microsoft page we will invent here, a People OS. If a demo only drafts the email or summarises the policy, you have a copilot.
Generic HR helpdesk bots (the widget on the intranet that knows the handbook) show up because they are easy to buy and easy to confuse with “AI HR.” They reduce tickets. They do not hire, onboard, or run payroll. Enterprise service layers (the Moveworks- and Leena-shaped products in the 2026 field guide) go further: they publish plan-and-execute on the stack you already have. That is still a front door, not a People OS.
IBM watsonx Orchestrate is the enterprise version of that front door plus a control plane. It is a serious agent layer. It is still a layer. See Kumo vs IBM if that is the comparison you actually have.
What “agentic HR employee” means at Kumo
Kumo’s published definition is narrow on purpose. An agentic HR employee is a colleague, not a feature. Kumo HR Agent 2.0:
- Reads CVs, contracts, and policies: the file, not the filename.
- Sees each tool’s real result and continues the mission. This is a loop, not a one-shot answer.
- Keeps going until the work is filed as an artifact you can open later.
- Pauses for confirmation on sensitive actions.
- Stays honest. The honesty kernel means it cannot claim unfinished work. The log is the record.
That colleague sits on the People OS (hiring, onboarding, payroll, leave, performance, policies, compliance) described on /platform and /platform/capabilities. You can still click. The point is that you will not want to. External agents can use the same work through API and MCP.
Pricing, if you need a number we are allowed to print: from $7 per employee per month on /pricing. Global hiring, if you need it: EOR in 180+ countries on /global.
Questions that puncture a demo
Ask these out loud. The answers sort chatbot from colleague.
- After the chat, who still clicks the HRIS? If the answer is “you,” it is a chatbot or a copilot.
- Does it open the CV, the contract, or the policy, or do you paste text into a prompt?
- When a tool returns something unexpected, does the plan change, or do you get a confident paragraph anyway?
- What happens on a sensitive step? Is there a confirm gate, or only a disclaimer?
- Can it show the log (every retrieval, tool call, and approval), or only the last message?
- Does it sit on a People OS, or on someone else’s system of record?
Kumo’s answers are on the agentic HR employee page and /intelligence: read, see, continue, confirm, honesty kernel, full audit trail, private data never used for training.
What we skipped. Feature lists for Microsoft Copilot SKUs, Illuminate agent matrices, and helpdesk-bot scorecards we could not verify on a public page. No invented customer quotes. No first-place badge. Contract review at Kumo remains a first-pass HR checklist, not legal certification.
If you only remember one line
Chatbots answer. Copilots suggest. An agentic HR employee does the work, and shows you what it did. If you want to see that employee rather than another prompt box, book a demo.