Skip to content

Customer Support and Success

Help Desk and Ticketing: from Remedy to AI agents

Help desk software is moving from a queue that routes tickets to people into a system where AI agents resolve most routine requests end to end. The bigger shift is pricing: vendors like Intercom and Zendesk now bill per resolution instead of per seat. Humans keep exceptions, judgment calls, and anything touching identity.

Verified Updated Oct 10, 2026By Deepak Gupta
3.2

Autonomy level

3.2 of 5 · Agents with approvals

launch score

Projected 4.0 by 2031

Tasks automated
3.0
Approval load
3.0
Production maturity
3.5

Overall is the mean of the three sub-scores. How scores work

Autonomy by era: On-prem 0.2, SaaS and cloud 0.8, AI-assisted 1.6, Agentic 3.2, Next 5 years 4.0.

Key numbers

The same job, five eras

Drag across the eras to see who did the work, with what, and what broke.

Ticket arrives
Capture the request
0.2 / 5

Era 1 · 1990-2007

On-prem

0.2
Who did the work
Tier 1 agents on phones and inboxes, a Tier 2 escalation desk, and a small admin team that kept the on-prem ticketing system running.
Tools
BMC Remedy Action Request SystemShared email inboxes (Outlook, Lotus Notes)ACD phone queues and IVRInternal wikis and printed runbooks
Representative product
BMC Remedy Action Request System
What broke
Customisation required admins and change projects. Email threads lost or answered twice.

Autonomy 0.2/5 · Manual

Zendesk
Ticket #1042
Ticket #1043
Ticket #1044
0.8 / 5

Era 2 · 2007-2017

SaaS and cloud

0.8
Who did the work
Larger Tier 1 teams, often outsourced to BPOs, plus a new support operations role that owned macros, triggers, and reporting.
Tools
ZendeskFreshdeskDesk.comHelp ScoutKayakoIntercom Messenger
Representative product
Zendesk
What broke
Cost scaled linearly with ticket volume and seats. Macro and trigger sprawl nobody could audit.

Autonomy 0.8/5 · Tool-assisted

Ticket #1042
Capture the request
Suggested reply drafted
Accept
1.6 / 5

Era 3 · 2017-2023

AI-assisted

1.6
Who did the work
Same team shape, with support operations adding bot builders and conversation designers who wrote decision trees and intents.
Tools
Zendesk Answer BotIntercom Resolution BotAdaSalesforce Einstein for ServiceFreshdesk Freddy (first generation)
Representative product
Zendesk Answer Bot
What broke
Bots deflected but could not act. Decision trees broke on any phrasing they had not seen.

Autonomy 1.6/5 · Copilot

Agent works the ticket
✓ Capture the request
✓ Checked policy
✓ Flagged 1 exception
Approve exception
3.2 / 5

Era 4 · 2023-2026

The Agentic Shift

3.2
Who did the work
Smaller Tier 1, with humans moving to escalations, QA of agent conversations, and the knowledge and procedures that agents run on.
Tools
Fin (formerly Intercom, now part of Salesforce)Zendesk AI agentsSalesforce Agentforce for ServiceSierraDecagonFreshworks Freddy AI Agent
Representative product
Fin (formerly Intercom, now part of Salesforce)
What broke
Self-reported resolution rates are hard to compare. Agents act on stale or wrong knowledge with confidence.

Autonomy 3.2/5 · Agents with approvals

Tickets
handled
Approved by you
4.0 / 5

Era 5 · 2026-2031

Next 5 years

4.0
Who did the work
A compact team of escalation specialists, agent supervisors, and procedure designers, with security owning the recovery and verification paths.
Tools
Agent platforms from help desk incumbentsAgent-native service platformsVoice agentsAgent identity and authorization layersConversation QA and evaluation tools
Representative product
Agent platforms from help desk incumbents
What broke
Agent-to-agent conversations with no human in either seat. Proving an AI resolution was real for billing and audit.

Autonomy 4.0/5 · Exception-only

What job does help desk and ticketing software do?

A help desk exists to take a customer's problem, make sure nobody loses it, and get it to a resolution as cheaply and quickly as possible. Everything else, the ticket number, the SLA timer, the macro library, the routing rule, is scaffolding around that one job.

As founder of LoginRadius, a CIAM platform I scaled to over a billion users, I have seen how much customer success matters, and I wrote about that discipline in pushing the boundaries of customer success. The lesson that carries over: the ticket was never the product. The outcome was. For thirty years the industry priced and staffed around the ticket. AI agents are forcing it to price and staff around the outcome.

Era 1 · Before SaaS · 1990-2007

How did help desk and ticketing work before SaaS?

Verified

Support in this era lived in three places: a phone queue, a shared email inbox, and, in larger companies, an on-prem ticketing system. Remedy was the name most IT and support leaders knew. Its Action Request System shipped in 1991 and became the default way big enterprises logged, assigned, and tracked requests.

The software ran on your own servers and needed admins to customise forms and workflows. Changing a field or a routing rule was a project, not a setting. Smaller teams skipped all of it and worked from a shared inbox, where the real routing system was whoever replied first.

Phones carried the urgent work. Customers waited in ACD queues, agents typed notes into the ticket afterwards, and knowledge lived in binders, wikis, and the heads of senior agents. Remedy itself changed hands twice in two years, bought by Peregrine in 2001 and sold to BMC in 2002 after Peregrine's bankruptcy.

What broke was visibility. Tickets were invisible to customers, duplicates piled up across email and phone, and nobody could say how long anything really took.

  1. Remedy Corporation founded in Mountain Viewsource
  2. Remedy ships the Action Request Systemsource
  3. BMC Software buys Remedy from bankrupt Peregrine Systemssource

Era 2 · The Cloud Move · 2007-2017

What changed when help desk and ticketing moved to the cloud?

Verified

Zendesk launched in 2007 from Copenhagen and showed that a help desk could be a browser tab you signed up for in an afternoon. Freshdesk followed in 2010 from Chennai with the same idea at a lower price. Desk.com, Help Scout, and Kayako filled in the rest of the market.

The unit of value became the seat. You paid per agent per month, and every new hire meant another licence. That model worked because support capacity really was a function of headcount: more tickets needed more people.

The SaaS desks added what on-prem never had. Customer-facing help centres, web forms that created tickets, live chat widgets, macros for common replies, triggers and SLA timers, and dashboards anyone could read. Zendesk went public in 2014 on the strength of that model.

What broke was scale. Macros and trigger rules multiplied until nobody understood the routing. Help centre articles went stale. Volume still grew linearly with customers, so the only lever was hiring more agents or offshoring to a BPO.

  1. Zendesk launches its browser-based help desksource
  2. Freshdesk founded in Chennai, later renamed Freshworkssource
  3. Zendesk goes public on the NYSEsource

Era 3 · The Copilot Years · 2017-2023

What did AI copilots change in help desk and ticketing?

Verified

Machine learning arrived as a suggestion engine. Zendesk introduced Answer Bot in 2017, which read an incoming ticket and offered the customer help centre articles before an agent picked it up. Intercom shipped its own Answer Bot in 2018 and the successor Resolution Bot in 2020.

These bots matched questions to known answers. They could not take an action, so a refund, an address change, or a password reset still went to a human. Deflection was the metric, and deflection often meant a customer gave up rather than got helped.

Inside the console, ML did triage: intent and sentiment tags, language detection, suggested macros, and skills-based routing. Agent assist tools proposed replies and pulled up related articles. The human still read every ticket that mattered and clicked every button that changed anything.

The market consolidated as growth slowed. Zendesk was taken private in 2022 by a Hellman and Friedman and Permira led group in a deal worth about $10.2 billion, just before ChatGPT reset expectations for what a support bot could do.

  1. Zendesk introduces Answer Bot inside Guidesource
  2. Intercom ships Answer Botsource
  3. Intercom launches Resolution Botsource
  4. Zendesk taken private in a $10.2 billion dealsource

Era 4 · The Agentic Shift · 2023-2026

The Agentic Shift: What do AI agents do in help desk and ticketing today?

Verified

The turn came in March 2023, when Intercom launched Fin on GPT-4, answering only from a company's own content and handing off when unsure. By 2026 Fin reports a 76% average resolution rate across more than 12,000 customers (vendor-reported), and it now updates accounts and processes refunds and payments, not just answers. Klarna showed the volume case in February 2024: its assistant handled two-thirds of service chats in its first month, which the company equated to 700 full-time agents. By May 2025 its CEO was telling Bloomberg the company would hire humans again, because cheaper AI had meant lower quality.

Incumbents bought their way in. Zendesk agreed to buy Ultimate in March 2024 and completed its purchase of Forethought in March 2026. In June 2026 Salesforce signed a definitive agreement to acquire Fin, which had renamed itself from Intercom, for about $3.6 billion, and it closed the deal on 10 September 2026. Fin now runs inside Salesforce AI Labs beside Agentforce, which Salesforce reported at $1.2 billion in annual recurring revenue in its first fiscal quarter of 2027. Agent-native companies are well funded: Decagon raised $250 million at a $4.5 billion valuation in January 2026, and Sierra announced a $950 million raise at a valuation above $15 billion in May 2026. They sell agents that rebook, refund, and change plans for brands such as Gap, SiriusXM, Duolingo, and Chime.

Pricing is shifting too. Zendesk moved to outcome-based pricing for AI agents in August 2024, and Fin charges $0.99 per outcome. Salesforce started at $2 per conversation, moved to $0.10 per action in 2025, and its Agentforce Service page now sells on a pay-per-resolution basis. When software does the work, the seat is a weaker unit, which is the argument I made in AI didn't kill SaaS, it killed the seat.

Vendor resolution rates are self-reported, and Gartner found in late 2025 that only 20% of service leaders had actually cut headcount because of AI. A later Gartner survey of more than 320 leaders found 85% expanding what human agents handle, with 31% implementing or planning AI-driven layoffs. Customers are not asking to be rid of people either: 87% told Gartner that a route to a human is essential. The phone line is now a target too: as I wrote in your phone line became the front door, automating it hands attackers a patient, polite agent that never gets suspicious.

  1. Intercom launches Fin on GPT-4source
  2. Zendesk switches AI agents to outcome-based pricingsource
  3. Salesforce makes Agentforce Service Agent generally availablesource
  4. ServiceNow announces customer service AI agents and says they handle 37% of its own case workflowssource
  5. Klarna's CEO says it will hire human support staff again after AI delivered lower qualitysource
  6. Decagon raises $250 million at a $4.5 billion valuationsource
  7. Zendesk completes its acquisition of Forethoughtsource
  8. Sierra announces a $950 million raise at a valuation above $15 billion, led by Tiger Global and GVsource
  9. Attackers talk Meta's AI support assistant into resetting Instagram account passwordssource
  10. Salesforce signs a definitive agreement to buy Fin (formerly Intercom) for about $3.6 billionsource
  11. Salesforce completes its acquisition of Finsource

Era 5 · The Next Five Years · 2026-2031

What will help desk and ticketing look like by 2031?

Verified

My bet is that by 2031 the help desk stops being a place where tickets wait. Most routine requests will be resolved by an agent before a ticket would have existed, across chat, email, and voice, and the queue that remains will be exceptions, disputes, and anything that changes who controls an account.

Gartner predicts agentic AI will resolve 80% of common customer service issues without a human by 2029. I think that holds for common issues at companies with clean knowledge and good backend APIs, and fails everywhere else. The constraint is not the model. It is whether the agent can safely call the refund system, the order system, and the identity system with the right scope.

Two things change the shape of the work. First, the customer side gets agents too: Gartner expects machine customers to start a large share of service requests, and its 2026 customer survey already found 58% of customers who use GenAI have used it to complete a task for them (74% in B2B). I expect support agents to negotiate with other agents. That is the world Future Tech describes as agent-answered calls. Second, pricing will likely finish its move to outcomes, as I argued in the pricing model that proves you're actually AI-native, and I expect vendors to compete on audited resolution more than on seats.

The human team gets smaller and more senior. It owns procedures, policies, escalations, and the identity checks no agent should run alone.

My prediction · by 2031 · medium confidence

By 2031, AI agents will resolve the majority of inbound help desk volume end to end at most mid-size and large companies, outcome-based pricing will be the default for support software, and human teams will handle exceptions, disputes, and identity-sensitive changes.

What has to be true

  • Backend systems (orders, billing, identity) expose scoped APIs agents can call safely
  • Agent identity, per-action authorisation, and audit become standard in support platforms
  • Independent, comparable measures of resolution replace vendor self-reporting
  • Regulators and customers accept agents as long as a human path remains available

Projected autonomy 4.0 of 5

  1. Gartner predicts agentic AI will resolve 80% of common service issues by 2029source
  2. Gartner survey finds 87% of customers want access to a human when GenAI handles servicesource

Then vs now: who does each step?

The job broken into its steps, and who or what does each one in each era.

Who or what does each step of Help Desk and Ticketing, by era
Job stepOn-premSaaS and cloudAI-assistedAgenticNext 5 years
Capture the requestAgent types phone or email into RemedyWeb form, email, or chat widget creates a ticketBot collects details and tags intentAI agent takes the conversation on any channelCustomer's own agent opens the request with context attached
Route and prioritiseTeam lead assigns by handTrigger rules and round-robinML intent and sentiment routingAgent decides to resolve or escalateOnly exceptions reach a human queue
Find the answerSenior agent memory and bindersAgent searches the help centreBot suggests articles; agent assist draftsAgent retrieves from knowledge and account dataAgent reads live system state, not articles
Take the action (refund, change, cancel)Agent works in a separate back-office systemAgent clicks through apps from the sidebarStill a human, guided by macrosAgent calls APIs within set limitsAgent acts within scoped, audited permissions
Verify identity and recover accountsAgent asks security questions by phoneAgent checks email and knowledge answersHuman, with a scripted checklistShould stay human; some vendors automate itCryptographic verification, human approval for changes
Check qualitySupervisor listens to a sample of callsCSAT surveys and manual QA on a sampleSentiment scoring on every ticketAI reviews every agent conversation; humans auditContinuous evaluation tied to billed outcomes

How does the help desk and ticketing team change?

The support team is not disappearing; it is changing shape. Gartner reported in late 2025 that only 20% of service leaders had cut agent staffing because of AI, and in 2026 that 85% were expanding what human agents are responsible for. The work moves from answering the same question for the thousandth time to owning the cases agents cannot close.

The new roles sit between the agent and the business. Someone has to write the procedures agents follow, decide what an agent may refund, review its conversations, and own the handoff from sales so the agent knows what was promised. I covered that last point at API World in the sales to support handoff, and in writing in what AI actually changes about the sales to support handoff.

Roles that shrink

  • Tier 1 agents answering repeat questions
  • Macro and trigger administrators
  • Outsourced BPO seats for routine volume
  • Decision-tree bot builders

Roles that appear

  • Agent supervisor who reviews and corrects AI conversations
  • Procedure designer who writes the workflows agents run
  • Knowledge owner accountable for what agents are allowed to say
  • Escalation specialist for disputes and high-value customers
  • Support security lead for verification and recovery paths

Skills to learn

  • Writing clear, testable procedures in plain language
  • Reading conversation transcripts for failure patterns
  • Understanding refund, billing, and order system APIs
  • Identity verification and social engineering awareness
  • Measuring resolution quality, not just deflection

What gets easier for the humans?

BeforeAfter
Customers wait in a queue for a password tip or an order statusRoutine answers arrive in seconds on any channel, any hour
Agents copy the same macro hundreds of times a weekAgents spend their day on cases that need judgment
Support cost grows with every new customer and seatCost tracks resolved outcomes, not headcount
QA reviews a small sample of conversationsEvery conversation is scored, and humans review the outliers
Multilingual support means hiring per languageAgents answer in the customer's language from the same knowledge

Decisions that stay human

  • Approving identity changes, MFA resets, and account recovery
  • Refunds, credits, or exceptions above a set value
  • Complaints, disputes, and anything with legal or regulatory exposure
  • Deciding what the agent is allowed to do and say
  • Serving a customer who asks for a person

Where should agents not act alone?

Risks and failure modes, through a security and identity lens.

  1. 01

    The help desk is the social engineering perimeter

    CISA's advisory on Scattered Spider describes attackers posing as employees to get help desk staff to reset passwords and move MFA to a device they control. Caesars disclosed a social engineering attack on an outsourced IT support vendor in 2023. I covered the pattern in [your help desk is the new perimeter](/help-desk-is-the-new-perimeter/). An AI agent that can reset credentials inherits that attack, at machine speed.

  2. 02

    Account recovery through an agent

    Over the weekend of 30 and 31 May 2026, attackers took over Instagram accounts by asking Meta's AI support assistant to add a new email address, then passing back the verification code it sent to that address. The bot then offered a password reset. Meta said on 1 June that the issue was fixed. Recovery is where identity is weakest. An agent should never be able to change an email, phone number, or MFA factor on its own say-so.

  3. 03

    A confident wrong answer becomes a commitment

    In Moffatt v. Air Canada (2024 BCCRT 149), a British Columbia tribunal rejected the airline's argument that it was not liable for what its chatbot said and ordered a partial refund of C$650.88 plus interest and fees. In April 2025 Cursor's support bot, presented as a person named Sam, told users a one-device-per-subscription policy existed. It did not, and its co-founder said so publicly. Treat every agent statement about policy or price as something the company will be held to.

  4. 04

    Prompt injection through customer messages

    Every inbound message is untrusted input to a model that can call tools. OWASP ranks prompt injection as the top LLM risk. Customer text, attachments, and pasted content must never be able to widen what the agent is allowed to do.

  5. 05

    Over-scoped agent credentials

    An agent that can issue any refund or edit any account is a standing privileged identity. Give each agent its own identity, per-action scopes, value limits, and short-lived tokens, and log which human policy authorised each action.

  6. 06

    Third-party and BPO exposure moves into the agent stack

    Outsourced support already widens the trust boundary, as the [Adobe BPO breach](/adobe-bpo-breach-hackerone-2026/) showed. Agent platforms, their model providers, and their integrations become new third parties holding customer data and write access.

  7. 07

    Outcome billing rewards false resolutions

    When a vendor is paid per resolution, a customer who leaves without asking again can count as resolved. Audit what your contract counts, sample closed conversations, and tie billed outcomes to repeat-contact rates.

How should you evaluate an agentic help desk and ticketing vendor?

Questions to put to any vendor before you let its agents act.

  1. Does each agent run under its own identity, and can I see and limit the exact scopes (refund ceiling, account fields it can edit, systems it can call) per action rather than per deployment?
  2. Can the agent change an email address, phone number, password or MFA factor on its own, and if not, how is that blocked in the product and not only in the prompt?
  3. What does your audit trail record for every agent action: the conversation, the policy that authorised it, the tool call and its result, and can I export it to my SIEM?
  4. Which actions need a human approval, who sets the thresholds, and can I turn a single action type off immediately without redeploying the whole agent?
  5. If the agent makes a wrong refund or sends a wrong policy statement, how do I find every affected conversation, reverse the action, and notify the customer?
  6. Where does customer data go, which model providers see it, how long is it retained, and is it used to train anything, for you or for them?
  7. How do you define a billed resolution, who can audit it against repeat contacts, and what happens to the bill when a customer comes back about the same issue?

Who is building agentic help desk and ticketing?

Incumbents adding agents vs agent-native entrants. Capability lines are checked against each vendor's own site.

Incumbents

  • AI agents, now including Forethought, that take action across connected systems on messaging, email and voice, claimed to resolve up to 80% of interactions, with pricing based on successful outcomes.

    Checked Oct 10, 2026Compare

  • Service agent runs multi-step workflows such as scheduling and order management on voice, web, portals, SMS and WhatsApp, escalates to staff with full context, and is sold on pay-per-resolution pricing; Salesforce also owns Fin since September 2026.

    Checked Oct 10, 2026Compare

  • AI agent that connects to backend systems to process refunds, update orders and reschedule bookings across email, web chat, WhatsApp and social.

    Checked Oct 10, 2026Compare

  • AI agents for customer service that resolve inquiries, manage fulfilment and hand complex cases to live agents with context; in May 2025 ServiceNow said agents automate 37% of its own support case workflows.

    Checked Oct 10, 2026

Agent-native

  • AI agent across voice, chat, email and Slack that updates accounts and processes refunds, reading and writing third-party systems through APIs, data connectors or MCP; Fin reports a 76% average resolution rate, charges $0.99 per outcome, and has been owned by Salesforce since September 2026.

    Checked Oct 10, 2026Compare

  • One agent across chat, SMS, WhatsApp, email, voice and ChatGPT for brands like Gap, SiriusXM and Rocket Mortgage, sold on outcome-based pricing.

    Checked Oct 10, 2026

  • Voice, chat and email agents driven by Agent Operating Procedures written in natural language, used by Chime, Duolingo and Oura.

    Checked Oct 10, 2026

Open source

  • Self-hostable support platform whose Captain agent answers routine questions from your help centre and documents and hands off to a person when needed.

    Checked Oct 10, 2026

Side-by-side comparisons: Top 5 AI Customer Service Tools 2026: Intercom Fin vs Zendesk AI vs the Rest.

Questions people ask

How is AI changing help desk software?

Help desks are moving from routing tickets to people to letting AI agents resolve routine requests end to end. Products like Fin, Zendesk AI agents and Salesforce Agentforce now take actions such as refunds and order changes, vendors increasingly charge per resolution instead of per agent seat, and the category is consolidating: Salesforce bought Fin for about $3.6 billion in 2026.

Will AI agents replace customer support agents?

Not entirely. AI agents are taking over repeat Tier 1 questions, but Gartner found in late 2025 that only 20% of service leaders had cut staff because of AI, and most are expanding human roles. Humans keep escalations, disputes, identity changes and customers who ask for a person.

What is outcome-based pricing for customer support AI?

You pay when the AI resolves something instead of paying per human seat. Zendesk introduced outcome-based pricing for AI agents in August 2024, Fin charges $0.99 per outcome, and Salesforce now sells its Agentforce Service agent per resolution. Read the contract carefully, because what counts as resolved drives the bill.

What percentage of support tickets can AI resolve today?

Vendor figures range widely. Fin reports a 76% average resolution rate, Zendesk claims up to 80%, and Freshworks said in October 2024 that private-beta users resolved an average 45% of customer support requests on their own. All of these are self-reported. Your rate depends on knowledge quality and whether the agent can act in your systems.

What was the first help desk software?

Enterprise help desk software took off with on-prem systems in the early 1990s. Remedy's Action Request System, which shipped in 1991, became the standard in large companies. Cloud help desks arrived with Zendesk in 2007 and Freshdesk in 2010.

Is it safe to let an AI agent reset passwords or MFA?

No, not on its own. Help desk resets are the main entry point for groups like Scattered Spider, and in May 2026 attackers talked Meta's AI support assistant into resetting Instagram passwords by feeding it their own email address. Keep identity and recovery changes behind strong verification and human approval.

What is the difference between a chatbot and an AI agent in customer service?

A chatbot answers questions, usually by matching them to articles or decision trees. An AI agent can also act: look up an order, issue a refund, change a plan, or rebook a trip by calling backend systems, then hand off to a human with context when it cannot finish.

What is agentic customer service?

Agentic customer service means an AI agent that does the work instead of only answering. It reads the request, checks account and order data, takes an action such as a refund or plan change through an API, and hands the case to a person with context when it cannot finish. The difference from a chatbot is permission to act.

Who owns Intercom and Fin now?

Salesforce. Intercom renamed itself Fin in 2026, Salesforce agreed in June 2026 to buy it for about $3.6 billion, and the deal closed on 10 September 2026. Fin now sits in Salesforce AI Labs next to Agentforce and says it still serves its existing customers.

Do customers want to talk to AI or a human?

Most want a human available. A Gartner survey of 3,566 customers in early 2026 found 87% say it is essential that companies using GenAI offer a way to reach a human agent, while 50% say GenAI makes their interactions easier. Make the human route easy to find, not a last resort.

Sources

  1. Remedy Corporation, accessed Oct 9, 2026
  2. Zendesk, accessed Oct 9, 2026
  3. Freshworks, accessed Oct 9, 2026
  4. Zendesk Launches Guide, a Next Generation Knowledge Solution, to Provide Smarter Customer Service, accessed Oct 9, 2026
  5. Intercom: Deliver instant resolutions with Answer Bot, accessed Oct 9, 2026
  6. Introducing Fin: Intercom's breakthrough AI chatbot, built on GPT-4, accessed Oct 9, 2026
  7. Fin: The #1 AI agent for customer service, accessed Oct 9, 2026
  8. Fin pricing, accessed Oct 9, 2026
  9. Klarna AI assistant handles two-thirds of customer service chats in its first month, accessed Oct 9, 2026
  10. Zendesk to Acquire Ultimate, accessed Oct 9, 2026
  11. Zendesk first in CX industry to offer outcome-based pricing for AI agents, accessed Oct 9, 2026
  12. Zendesk Completes Acquisition of Forethought, accessed Oct 9, 2026
  13. Zendesk AI agents, accessed Oct 9, 2026
  14. Salesforce's Agentforce Is Here: Trusted, Autonomous AI Agents to Scale Your Workforce, accessed Oct 9, 2026
  15. Salesforce Introduces New Flexible Agentforce Pricing, accessed Oct 9, 2026
  16. Freddy AI Agent, accessed Oct 9, 2026
  17. Introducing Freddy AI Agent for Superior CX and EX, accessed Oct 9, 2026
  18. ServiceNow Reimagines CRM for the AI Era, accessed Oct 9, 2026
  19. Sierra, accessed Oct 9, 2026
  20. Decagon, accessed Oct 9, 2026
  21. Chatwoot, accessed Oct 9, 2026
  22. Gartner Predicts Agentic AI Will Autonomously Resolve 80% of Common Customer Service Issues Without Human Intervention by 2029, accessed Oct 9, 2026
  23. Gartner Survey Finds Only 20% of Customer Service Leaders Report AI-Driven Headcount Reduction, accessed Oct 9, 2026
  24. Gartner Survey Finds 85% of Service and Support Leaders are Expanding Human Agent Responsibilities, accessed Oct 9, 2026
  25. Gartner Survey Finds 87% of Customers Say Companies Using GenAI for Customer Service Must Provide Access to a Human Agent, accessed Oct 9, 2026
  26. CISA AA23-320A: Scattered Spider, accessed Oct 9, 2026
  27. Caesars Entertainment Form 8-K, 14 September 2023, accessed Oct 9, 2026
  28. Hackers hijacked Instagram accounts by tricking Meta AI support chatbot into granting access, accessed Oct 9, 2026
  29. OWASP Top 10 for LLM Applications 2025, accessed Oct 9, 2026
  30. Salesforce Signs Definitive Agreement to Acquire Fin, accessed Oct 10, 2026
  31. Salesforce Completes Acquisition of Fin, accessed Oct 10, 2026
  32. AI proliferates in contact centers as leaders pursue workforce redesign, not mass layoffs (CX Dive, reporting Gartner), accessed Oct 10, 2026
  33. Most Service Leaders Are Expanding Agent Responsibilities, Not Cutting Jobs, Gartner Finds (CX Magazine), accessed Oct 10, 2026
  34. Customers Want Access to Human Agents From Companies Using GenAI for Customer Service: Gartner (Insurance Canada, republishing Gartner Q&A), accessed Oct 10, 2026
  35. Sierra: Year two in review, accessed Oct 10, 2026
  36. AI Customer Support Startup Decagon Valued at $4.5 Billion (Bloomberg), accessed Oct 10, 2026
  37. Klarna Is Hiring Customer Service Agents After AI Couldn't Cut It on Calls (Entrepreneur, citing Bloomberg), accessed Oct 10, 2026
  38. AI Gone Wild: Airline Has to Honor a Refund Policy Its Chatbot Fabricated (Manatt, on Moffatt v. Air Canada, 2024 BCCRT 149), accessed Oct 10, 2026
  39. Customer support AI went rogue at Cursor (Fortune), accessed Oct 10, 2026
  40. Agentforce Service, accessed Oct 10, 2026
  41. Better customer experiences. Built on Sierra, accessed Oct 10, 2026

Published Oct 9, 2026. Last verified Oct 10, 2026. Eras 4 and 5, vendors, and scores are re-checked every six to eight weeks; see the changelog and methodology.