AI Voice Agents, WhatsApp in the Agent Desktop, and AI Triage at the Front Door

By DripPublished

The gist

Customer support is shifting from manual call handling to AI-led intake, while omnichannel work is collapsing into one desktop and one customer record.

This week’s developments

Home Depot Brings AI Voice Agents to the Front Door of Support

The Home Depot this week announced AI-powered voice agents with Google Cloud and Gemini Enterprise, replacing IVR menus with conversational intent detection and moving call navigation, routing, and first-response resolution from agents to AI. That matters because voice is the hardest service channel to automate, and this puts AI at the front door of support, not just behind the scenes.

The pattern is moving in the same direction, but the evidence is still case-based. Klarna said genAI handled up to 75% of support interactions before bringing more humans back into complex and premium cases; NAGA Group said AI fully resolved about 66% of chat support and plans to extend automation to email. Other firms have cut human oversight after deployment: Uber reduced about 10% of its Community Operations workforce, Microsoft and Commonwealth Bank of Australia reportedly trimmed Tier-1 support roles, and Commonwealth Bank later reversed course after its AI voice bot struggled with call volumes. ServiceNow has taken a different approach, keeping staff in the loop through dashboards and escalation review.

For service leaders, this is the next step beyond supervised copilots: governing end-to-end flows across voice, chat, routing, and QA. The career edge now belongs to people who can tune escalation rules, read containment and resolution metrics, and define where human judgment stays mandatory.

How should your support team adapt to AI voice automation?

If you're an individual contributor

  • IVR handling is fading; AI supervision is the new entry-level edge.
  • Learn to spot bad routing, failed containment, and escalation triggers—your value shifts to catching what AI misses.

Sources

If you manage a team

  • Your team is moving from call handling to exception judgment.
  • Coach reps on escalation review, QA, and AI override decisions; stop spending most time on script compliance.

Sources

If you lead the organization

  • Voice automation is now an operating model issue, not a pilot.
  • Rework staffing, QA, and escalation design around containment metrics and human-in-the-loop rules before volume forces it.

Sources

United Telecoms Brings WhatsApp Into the Same Service Desktop

United Telecoms this week added direct WhatsApp integration to its contact-centre platform through Meta’s WhatsApp Business Platform, letting agents handle WhatsApp in the same desktop as voice, live chat, and SMS with one customer record behind each conversation. That is the clearest sign yet that WhatsApp is being treated not as a separate inbox, but as a native support channel inside the case-handling environment where history, follow-up, and handoffs already live.

The shift extends the unified-context model from a shared customer view into channel absorption. The point is not just that agents can see more of the customer in one place; it is that a high-volume messaging channel is being pulled into the standard workflow so continuity survives channel changes. United Telecoms did not publish WhatsApp-specific response-time or productivity data, so the evidence is architectural, not performance-based. But the direction is clear: support stacks are being built so WhatsApp, like voice or chat, feeds the same service record and can connect onward to CRM and helpdesk systems such as Salesforce, HubSpot, Zendesk, and Freshdesk.

For support professionals, the progression is from managing channels to managing cases across channels without losing context. Teams will need agents who can read cross-channel history, maintain asynchronous conversations, and execute follow-up inside one integrated workflow instead of bouncing between tools.

How should we redesign workflows for WhatsApp in one service desktop?

If you're an individual contributor

  • WhatsApp is now part of the same case flow, not a side inbox.
  • Your edge is cross-channel context and clean follow-up; learn to handle async WhatsApp without losing the customer story.

Sources

If you manage a team

  • Your team’s speed now depends on one shared service record.
  • Coach agents on case continuity, handoffs, and async messaging; stop treating WhatsApp as a separate skill silo.

If you lead the organization

  • Channel strategy is becoming operating-model strategy.
  • Invest in unified desktop and CRM/helpdesk integration; hire and train for context handling, not channel-by-channel work.

Sources

OKI Puts AI Triage at the Contact-Center Front Door

OKI’s CTstage AI Concierge shows the next step in the sequence: conversational intent detection, initial inquiry triage, guided self-resolution, live-agent fallback, and response support that summarizes calls and logs interaction history. That is a narrower, more defensible use case than full autonomous answering, and the source does not claim end-to-end replies from scratch or quantify deflection or average handling time gains.

Read after Peresoft’s governed retrieval into self-service actions, the pattern is tightening around the front door of service operations. AI is now being inserted to sort, route, and summarize high-volume work before a human takes over, rather than only surfacing knowledge or executing contained workflows. OKI’s target sectors—finance, retail, government, transportation, manufacturing, logistics, healthcare, and defense—are exactly where labor pressure and traceability requirements make this easier to deploy. For support leaders, the progression is clear: the near-term job is not replacing agents, but redesigning intake so AI handles the repetitive first pass, preserves auditability, and frees staff for the cases that actually need judgment.

How should we redesign roles for AI-led front-door triage?

If you're an individual contributor

  • Front-door triage is automating; your edge is judgment, not speed.
  • Learn to supervise AI intake, spot bad routing, and handle exceptions well — that’s how you stay indispensable.

Sources

If you manage a team

  • Your team’s value is shifting from first response to exception handling.
  • Coach reps on AI-assisted triage, QA, and escalation judgment; stop spending so much time on rote intake work.

Sources

If you lead the organization

  • Your service model should assume AI handles the repetitive first pass.
  • Rework staffing, workflows, and governance now so AI sorts and summarizes intake while humans focus on traceable judgment calls.

Sources

Part of these trends

Stay ahead in Customer Support / Service

Get the weekly Customer Support / Service brief in your inbox — the developments, what they mean by seniority, and what to do next.