Weekly signal

This week (June 15–23, 2026) saw vendors and integrators move agentic customer service from proofs-of-concept into production patterns: platform-level agent features and governance (Salesforce Summer ’26 release) plus multiple vendor launches that close the loop between conversation, identity, decisioning, and operations. The common theme is operationalizing voice + chat agents with grounded data, end-to-end workflow execution, and explicit security controls — not just better replies.

What changed

1. Salesforce pushed a broad Summer ’26 Agentforce update that makes agent observability, Model Context Protocol (MCP) interoperability, voice agents, citation support for “bring your own channel,” and a hard move to the new agent builder (creation in legacy builder disabled starting July 2026). This is a platform-level nudge forcing teams to adopt the new builder and to design agents that call governed tools rather than free-text APIs.

2. CloudInteract and Red Kite published a working pattern running autonomous AI voice agents on Amazon Connect + Bedrock with Pega decisioning to execute real outcomes (bookings, eligibility checks) and hand off with full context — a production deployment pattern for regulated customer service workflows. They demonstrated it at PegaWorld. The pattern emphasizes orchestration (AI conversation → decision → action) over purely conversational plumbing.

3. Celebrus launched Celebrus AI, an identity-resolved conversational analytics layer that connects live first-party behavioral data to popular agent models (Anthropic, Microsoft Copilot, OpenAI). That makes real-time customer grounding available to agents and copilots for safer personalization and measurement.

4. WitnessAI and other security vendors released agentic governance controls for discovering agents, governing MCP connections, and applying prompt-injection / data-leak protections — a sign that security tooling for non-human identities is becoming mainstream for CX deployments.

5. Virtana introduced agentic SLA management — agents that monitor KPIs, correlate impact, and trigger remediation and customer communications automatically, turning SLAs into operational controls. This links reliability to experience in an automated loop.

What to do with it

1. Inventory your agent footprint and plan migrations to the new builder or platform updates now (Salesforce customers: prepare to stop creating agents in legacy builder July 2026). Start by exporting agent definitions, test suites, and tool schemas.

2. If you run voice CX or regulated workflows, evaluate the Amazon Connect + Pega pattern as a blueprint: prioritize decisioning & identity integration early so agents can act (book/modify/authorize) instead of only conversing. Build clear handoff contexts for human agents.

3. Add live first-party grounding (identity & behavioral signals) to your agent design to reduce hallucination and increase personalization — test Celebrus-style integrations in a VPC/MCP pattern or via controlled data adapters.

4. Treat agent governance and non-human identity security as production requirements: deploy discovery, MCP allowlists, and prompt-injection defenses before opening agents to sensitive channels.

5. Reframe SLA work: pilot outcome-based SLA agents that both detect customer-impacting degradations and run templated remedial customer comms and escalations. Measure containment, escalation, and customer satisfaction together.