Dialpad Logo
Dialpad and Google Cloud

The Next Phase of Customer Service AI

A survey of 150 Director and VP+ leaders across Retail and Healthcare examines where AI stands in customer service today: deployment, sophistication, architecture, measurement, and the barriers that separate early movers from the rest.

n=150 respondents · Director and VP+ seniority

75 Retail + 75 Healthcare · 50 / 50 industry split

12 questions across maturity, architecture, measurement & governance

Contact Center, Digital, CX, Technology and Care Operations leaders

Where organizations are on the AI journey

23%

Planning · n=35

42%

Piloting · n=63

35%

Deployed · n=52

Executive Summary

The next phase will be defined less by introducing new AI capabilities and more by operationalizing existing ones

The distribution of organizations across planning, piloting, and deployment stages reveals a market that has largely moved beyond AI experimentation and into operationalization. With 77% of organizations now actively piloting or deploying AI, the conversation is no longer centered on whether AI belongs in customer service, but on what it takes to make AI perform consistently at scale.

This shift is exposing a new set of challenges. Organizations have established AI's customer-facing communication layer, but many have yet to build the underlying systems, governance models, and data foundations required to support autonomous execution. As a result, the gap between AI deployment and AI performance is becoming increasingly apparent.

The next phase of maturity will therefore be defined less by introducing new AI capabilities and more by operationalizing existing ones. Across both Retail and Healthcare, competitive advantage is shifting toward organizations that can effectively connect AI to systems of action, preserve customer context across channels, and establish clear frameworks for human-AI collaboration.

77%deployed or piloting AI in customer service; the adoption question has largely been settled
25%have autonomous resolution enabled. Deployment and capability maturity are not the same milestone.
83%of Planning-stage organizations are blocked by undefined AI decision rules. Governance, not technology, is the gate.
43%have enough data to state whether AI is paying off, despite 68% having ROI measurement frameworks in place

8 Findings

All Industries · n=150 · Retail and Healthcare combined unless noted

01. The Deployment Illusion

AI is in the building. Autonomous AI is not.

The AI capability stack drops sharply after retrieval and routing. There are two distinct cliffs: −19 points from Sentiment & Intent to Proactive Engagement, then another −18 to Autonomous Resolution. Organizations have built the foundation but haven't climbed the stack.

AI Capability Stack: % with each capability enabled (n=150)

Information Retrieval

80%

Navigation & Routing

75%

Real-Time Agent Support

69%

Sentiment & Intent

62%

Proactive Engagement

43%

Autonomous Resolution

25%

13%

fully preserve cross-channel context when customers switch. Another 53% have partial context; 21% mostly lose it.

The 55-point drop from Information Retrieval (80%) to Autonomous Resolution (25%) represents the gap between AI that knows things and AI that does things. Most organizations are firmly in the former.

02. The Execution Gap

AI understood the request. It could not complete it.

Most conversations about AI failure focus on comprehension: AI that misunderstands intent, misreads context, or escalates unnecessarily. The data points to a different problem. The second most common trigger for AI-to-human handoffs is not confusion. It is capability. 21% of handoffs occur because AI understood the request but lacked the technical ability to complete it.

Execution Readiness: % Agree+ (n=150)

Real-time data at interaction start

62%

AI directly connected to action systems

45%

Full cross-channel history available

33%

21%

of AI-to-human handoffs are triggered by capability, not confusion. AI understood the request but had no path to complete it.

That is not an AI problem. It is an infrastructure problem being managed as a staffing one.

Only 45% of organizations have AI directly connected to the systems it needs to act on customer information. Only 33% have the customer's full cross-channel history available at the point of interaction. The result is an AI layer that can understand what needs to happen but has no path to make it happen. Every time that gap is hit, the interaction transfers to a human, the cost rises, and the resolution that AI was supposed to deliver does not.

The so-what: Organizations measuring AI by containment rate and escalation rate are not seeing this failure. A handoff triggered by technical inability looks identical in the data to a handoff triggered by customer preference or emotional complexity. Until organizations can distinguish why handoffs happen, they cannot fix the ones that should not be happening at all.

03. The Channel Memory Problem

AI can retrieve information. It cannot remember the customer.

Organizations have point-in-time data. They do not have cross-channel memory. And the channel where memory breaks down most visibly is the one customers still reach for when a problem is serious.

AI Sophistication by Format, full distribution (n=150)

Not in UseBasicConversationalAction-OrientedAutonomous

Chat / Messaging

5%
17%
33%
34%
11%

Agent Assist

6%
17%
33%
35%
9%

Voice AI

13%
25%
32%
23%
7%

62% of organizations have real-time customer data at the start of each interaction. Only 30% maintain context across voice and digital. Only 13% preserve it fully when a customer switches channels. Voice AI runs 15 points behind chat and 14 points behind Agent Assist on sophistication, with nearly 3× the "not in use" rate. The result: the channel customers default to for complex or emotionally charged issues is the least equipped to carry their history into the conversation.

This is not a voice problem in isolation. It is a channel architecture problem. AI can retrieve information. It cannot remember the customer. Those are not the same capability, and most organizations have built only the first one.

The so-what: Cross-channel memory appears to be a deployment prerequisite, not a feature added later. Among Deployed organizations, 54% maintain cross-channel context. Among Piloting organizations, 18% do. That 36-point jump does not happen gradually. It happens at the moment of full deployment, which means organizations still in pilot are likely underestimating how much architecture work sits between them and scale.

04. The Rules Wall

Undefined decision rules stop AI from acting, not capability.

The top AI-to-human handoff trigger is scope, not technical failure. 29% cite requests falling outside AI's defined decision rules as the primary trigger. Among Planning-stage organizations, 83% cite undefined rules as a barrier to autonomous AI. At Deployed stage: 25%. That 58-point drop tracks almost exactly with the gap between organizations that have deployed and those that haven't.

Undefined Decision Rules as Barrier, by Deployment Stage

Planning

83%

Piloting

46%

Deployed

25%

Defining what AI can and cannot do is the entry ticket to deployment, not something that emerges from it. Organizations that have done it are deployed. Organizations that haven't are not.

05. The Measurement Paradox

Most organizations measure AI. Fewer than half can prove it's working.

68% say AI metrics are tied to measurable ROI, but only 43% have enough data to state whether AI is paying off. The measurement infrastructure exists; the evidence base does not. And 54% cannot yet distinguish a truly resolved ticket from a deflected one, so the resolution data they are collecting may be overstating AI's actual performance.

Measurement Confidence: % Agree+ (n=150)

AI metrics tied to measurable ROI

68%

Review resolution outcomes consistently

59%

Monitoring alerts if AI stops resolving

53%

Can distinguish resolved vs. deflected

46%

Enough data to state whether AI pays off

43%

25pp

gap between "we have ROI metrics" (68%) and "we can prove it's working" (43%)

Most organizations have built measurement infrastructure. The problem is evidence quality. And the evidence quality problem starts with how resolution is defined. When asked what must be true for an interaction to count as resolved, 39% of organizations include "customer stopped responding for a set period" as a valid criterion. Silence is being counted as success. A further 51% count "case closed without a human agent", regardless of whether the underlying issue was actually addressed.

The metric choices compound the problem. Containment Rate (52%) ranks above Resolution Rate (43%) as the most commonly used AI performance metric. Organizations are measuring whether AI kept the customer away from a human before they are measuring whether AI solved the customer's problem. Avoidance is being tracked more carefully than outcomes.

ROI claims built on these definitions are not measuring AI performance. They are measuring AI activity. The gap between the two is where AI's real value, or lack of it, actually lives. Until organizations tighten what counts as resolved, the measurement infrastructure they have built will continue producing numbers that look good and mean less than they should.

06. The Maturity Divide

AI has conquered volume. It has not touched judgment.

Across both industries, AI follows the same pattern: high-volume, transactional service areas first; sensitive and clinically complex areas last. The pattern is consistent, and it follows the same logic across both industries: structure first, judgment last.

No AIDeflectiveConversationalTransactionalAgentic

Retail (n=75)

Order Management & Support

56%

Product Discovery & Availability

45%

Account / Profile Updates

43%

Returns, Refunds & Billing

37%

Engagement & Loyalty

33%

Complaints & Escalations

24%

Healthcare (n=75)

Appointment & Scheduling

49%

Administrative Support

43%

Follow-ups & Care Coordination

33%

Insurance, Billing & Payment

33%

Referral Management

25%

Clinical & Medication Queries

17%

Grievances & Complaints

17%

Order Management leads at 56%, the highest of any service area in the dataset. Clinical Queries and Grievances sit at 17%: both healthcare service areas where an error has direct patient consequences. The gap between them is not accidental.

07. The Human Operating Model

AI needs designed collaborators, not backstops.

61% have designed clear rules for what AI handles and when humans take over. The remaining 39% are operating without that structure. Of those, 11% have reduced human agents to pure overflow with no defined role, no triggers, and no handoff logic.

Role of Human Agents in AI-Assisted Service (n=150)

Intentionally designed: clear AI vs. human rules

61%

Escalations handled without predefined rules

29%

Humans as unstructured overflow only

11%

Scaling AI in customer service requires designing the human role with the same care as the AI role. Treating human agents as backstops rather than designed participants is a governance gap, not an efficiency choice.

08. The Two Industry Walls

Retail is blocked by fragmentation. Healthcare is blocked by regulation.

The largest single divergence in the dataset: regulatory constraints hit Healthcare at 63% vs. Retail at 29%, a 34-point gap. Retail's ceiling is structural, driven by systems and integration gaps. Healthcare's ceiling is set by compliance and governance. The path to scale is different in each industry because the obstacle is different.

Primary Barriers to Autonomous AI, Retail vs. Healthcare (n=75 each)

RetailHealthcare

Regulatory / Compliance

34pp

Trust in AI Accuracy

5pp

Fragmented Systems / Data Silos

8pp

Technical Integration Gaps

5pp

Undefined Decision Rules

1pp

Customer/Patient Acceptance

7pp

The takeaway

The barriers to AI autonomy extend beyond technology itself. Organizations report a mix of operational, governance, and trust-related challenges, indicating that scaling AI requires progress across multiple foundational areas rather than a single capability improvement.

What Separates Leaders from the Rest

AI adoption is no longer the primary challenge. Turning capability into outcomes is.

Across both Retail and Healthcare, organizations are actively deploying and piloting AI capabilities. The greater challenge is turning those capabilities into consistent customer outcomes. The organizations making the most progress are not necessarily investing in more AI. They are addressing the operational, architectural, and governance gaps that stand between AI deployment and AI performance.

01. Define decision rules before expanding autonomy

The top trigger for AI-to-human handoffs is not capability failure but requests falling outside AI's defined authority. Organizations should establish clear decision boundaries, escalation triggers, and approval thresholds before increasing AI autonomy.

02. Connect AI to the systems required for resolution

AI cannot resolve issues it cannot act on. Connecting customer service AI to operational systems — CRM, order management, payments, scheduling, workflow platforms — is essential to closing the gap between understanding a request and completing it.

03. Measure outcomes, not activity

Many organizations continue to prioritize containment, deflection, and handle-time metrics. Leaders should focus on measures that reflect customer outcomes — resolution rate, customer effort, and business impact.

04. Design the human role intentionally

Human involvement should not be treated as a fallback. Organizations need clear rules for when employees intervene, what decisions require human judgment, and how AI and people work together throughout the customer journey.

The next phase of customer service AI will be shaped less by advances in the technology itself and more by how effectively organizations operationalize it. Clear decision authority, connected systems, meaningful measurement, and well-defined human involvement are increasingly becoming the factors that separate successful deployments from stalled initiatives.

Retail & Healthcare: Two Industries, Two Problems

The path to effective customer service AI is not the same for every industry.

AI in customer service is entering a new phase of specialization. Early adoption was defined by broad experimentation, with organizations across industries deploying similar technologies and following comparable playbooks. That approach is becoming insufficient. The differentiator is shifting away from the technology itself and toward the environment in which it operates, with industry-specific realities increasingly determining how organizations scale and where they encounter friction.

Organizations are no longer competing on their ability to deploy AI, but on their ability to adapt it to the realities of their business. There is no singular path to AI maturity, and generic, one-size-fits-all approaches are approaching their ceiling. Competitive advantage now belongs to organizations that focus on deep backend integration, outcome-based measurement, and deliberate human-in-the-loop governance.

This survey examines two industries, Retail and Healthcare, each with distinct customer service operating realities, distinct constraints, priorities, and risk profiles that shape how AI is deployed and scaled. The industry findings unpack the factors that accelerate or constrain AI adoption and highlight the capabilities organizations need to build to succeed within each environment.

Retail · n=75

The Integration Race

Primary investment driver: handle higher volumes without adding headcount (64%) and reduce wait times (60%). Competitive pressure is explicit: 29% cite keeping pace with competitors, a motivation that does not appear in Healthcare.

59%

cite Fragmented Systems / Data Silos as their top barrier, highest-ranked for Retail

AI deployments are among the most mature in the dataset: Order Management has reached 56% Transactional or Agentic. Fragmented systems and integration gaps prevent AI from accessing the data it needs to act across the full service footprint.

Healthcare · n=75

The Regulated Frontier

Primary investment driver: reduce administrative burden on staff (65%). Healthcare AI investment is staff-driven, not competitive. The motivation is relief from administrative load, not market position.

63%

cite Regulatory / Compliance Constraints as their top barrier, highest of any factor in the dataset and 34 points above Retail

Clinical and complaint areas are kept below the autonomous threshold by design, given patient safety stakes.