By Sagar Shankaran, Founder of CallSphere
The UK NHS scaled AI agent pilots across London trusts in 2026. Here's the deployments, the procurement model under the AI Buying Catalogue, the outcomes.
Key takeaways
The vendor cohort named in this post produced one of the more consequential April 2026 announcements for healthcare buyers. The platform changed shape, the pricing model evolved, and a wave of named enterprise customers committed publicly. Together those signals reshape the vendor shortlist for any team running a healthcare AI agent RFP this quarter or next.
This post breaks down what shipped, what's now in production, what the contract looks like, and what to do about it as a buyer or a competing vendor.
Public confirmation from the last 30 days produces a consistent picture:
These are the public-facing numbers we can confirm. Internal benchmarks from buyers we've spoken with under NDA skew slightly higher on resolution rate and slightly lower on cost, primarily because most enterprises are routing fallback intents to cheaper models like Haiku 4.5 or GPT-4o-mini rather than running everything on the flagship reasoner.
Three questions that cut through the marketing in any vendor evaluation:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for healthcare in your browser — 60 seconds, no signup.
Demand the answers in writing during the procurement cycle. Vendors who refuse to commit are signaling something important about their actual production behavior.
Buyers in London NHS consistently flag three priorities in their RFPs in 2026:
Vendors that meet all three are winning the bake-offs. Vendors that meet only two are losing them in London NHS-based decisions. The differential matters because buyers in this region tend to do more reference checking than US-coastal buyers.
After watching dozens of bake-offs in this segment in Q1-Q2 2026, the consistent patterns:
There is no single right answer. There are several wrong ones, and the wrong ones tend to be the ones that look right on paper but fail one of the deployment-criteria checks above.
CallSphere ships a turnkey AI voice and chat agent platform for healthcare teams that need this kind of agentic capability without a six-month enterprise rollout. The platform handles the SIP and WebRTC plumbing, the model routing across Claude, GPT, and Gemini, the CRM and calendar integrations, and the HIPAA, and PCI controls out of the box.
Still reading? Stop comparing — try CallSphere live.
See the healthcare AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
Most teams are live in production in under two weeks at a per-minute or per-conversation price that lands at a fraction of the platform alternatives named earlier in this post. The trade-off is the typical one — less customization, faster time to value. For most healthcare teams that's the right trade.
For teams evaluating against the vendors named here, the deployment shape is the same — define the goal, wire the tools, set the guardrails — but the time-to-live and total cost are radically different when you do not have to assemble it yourself from primitives.
How big is the healthcare AI agent market in 2026? Estimates run $4-8B in 2026 software spending across the named vendors, growing 80-120% year-over-year. The estimates are wide because pricing models vary so much that comparing total spend across vendors is hard.
What's a realistic deflection or resolution rate target? 60-75% on tier-1 intents in year one is reasonable. 80%+ requires sustained tuning, deeper tool integration, and disciplined intent expansion. Targets above 90% in year one are usually unrealistic and will lead to unhappy customers when escalation paths break.
Should we buy from an incumbent or a pure-play? Incumbents (Salesforce, Zendesk, Microsoft) win on integration. Pure-plays (Sierra, Decagon, Ada) win on agent quality. The gap is narrowing through 2026 — by end of year it may not matter much for most use cases.
What's the riskiest part of a healthcare AI agent rollout? Knowledge base quality. The agent is only as good as the underlying content it can ground answers in. Most failed deployments traced back to outdated, contradictory, or poorly structured knowledge bases — not to model issues.

Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
A2A unlocks cross-vendor agent coordination, but most enterprise voice/chat workloads still ship faster on a single-vendor stack. Here is how to choose.
Working memory, permanent memory, sandboxes, harnesses, governance — the practical blueprint enterprises are using to ship long-horizon AI agents in 2026.
At Cloud Next 2026 Google renamed Vertex AI to Gemini Enterprise Agent Platform and absorbed Agentspace. What actually changed and why a rebrand made sense.
AI Control Tower is the governance layer for ServiceNow's Project Arc — policy, monitoring, and audit logs for autonomous agents. Here is how it works.
Anthropic confirmed JPMorgan Chase, Goldman Sachs, Citi, AIG, and Visa in production on Claude as of May 2026. What each pattern of usage looks like.
CAISI announced new agreements with Google DeepMind, Microsoft, and xAI in May 2026. What gets tested, what changes for enterprise AI buyers, what to watch.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco