A Chatbot Answers. An Agent Closes a Ticket. That Is Not an Employee.

The brief for this cycle is a question: could AI handle complete jobs, not just tasks? The 2026 answer is smaller than the job title.

A chatbot returns text. An agent is allowed to use tools, touch a record, and stop when a ticket is closed. Those are different jobs. Calling the second one an employee mixes them.

Four jobs, keep them separate

1. Answer — a reply in a box.

2. Act — call an API, update CRM, file a request.

3. Close — a named receipt: chats resolved, pipeline built, admin tickets done.

4. Hold the company — permissions, escalation, audit, who gets fired when it is wrong.

Job 3 has receipts in 2026. Job 4 is why Gartner is not writing “AI employees” as a product category.

What has a close rate

Salesforce’s 11 September 2026 Agentforce announcement is the vendor receipt, not a census of every company.

Salesforce says it delivered 7 billion Agentic Work Units across Agentforce and Slack over two years, 3.2 billion of those in Q2. AWUs are work units. They are not headcount.

Named closes from that same release:

Engine’s help agent Eva fully resolved 50% of chat inquiries.

Autism Queensland’s employee service agent Paige resolved 70% of administrative requests.

Hibbett’s shopper agent handled 90% of core shopper journeys and went live in six weeks.

Asana’s website agent Piper drove 4× conversation volume; customers deploy Piper in 45 days on average.

Anthropic reports Fin resolved 79% of the conversations it sees autonomously.

Perk says its outbound agent Hunter built 60% of its sales pipeline. Salesforce lists Hunter as pilot now, GA November 2026. Keep that in the pilot column. Do not write it as a generally available employee.

Casey, Paige, Carter, Marshall, Piper, and Fin are listed as generally available. They are job-shaped agents: help, IT/HR, shopper, supply chain, inbound pipe, customer experience. Each one is a ticket class. None of them is “run the company.”

What the survey says, next to the press release

Gartner’s 2026 Hype Cycle for Agentic AI (Rajesh Kandaswamy, 15 April 2026) puts agentic AI at the Peak of Inflated Expectations. The 2026 Gartner CIO and Technology Executive Survey: only 17% of organizations have deployed AI agents; more than 60% expect to within two years. Gartner’s own gloss: most deployments remain narrowly scoped, and fully autonomous agents are not ready for the majority of enterprise use cases.

That is the map. Vendor close rates are real on named jobs. Survey deployment is still 17%. Intent is not a close.

A later Gartner line, reported 9 September 2026 from a May 2026 prediction: by 2027, 40% of enterprises will demote or decommission autonomous AI agents because governance gaps showed up after production incidents. The recommended ladder is observe, advise, act with approval, then act autonomously inside guardrails. Skip a rung and the 40% is the receipt you get later.

What this is not

It is not a general-purpose employee. The documented work is chats, admin requests, shopper journeys, inbound qualification. Escalation is in the product (Casey includes human escalation). Hunter’s long-horizon runtime still says the seller stays in control.

It is not “AI replaced the service org.” Engine still has a service org. 50% of chats closed is a station. The other 50% is still a person.

It is not proof that every agent in a demo is in production. Salesforce’s own press release warns that some named capabilities are still in development. Customers should buy what is shipping.

The map

Four jobs: answer, act, close, hold the company.

2026 has close rates for a few ticket classes. It has a 17% deployment survey and a 40% decommission warning for agents that skip governance. The chatbot is still the answer box. The agent is the ticket. The org chart did not move.

A chatbot answers. An agent closes a ticket. That is not an employee.

Read the map at amtocbot.com.