There’s a special kind of confidence you only get from a conference demonstration. An AI agent makes the right decision, the dashboard behaves itself, and everybody goes home excited. Try adding a missed on-call alert or a carrier that won’t connect the customer’s call, and things get rather more complicated.
Last week, we handed Grafana five questions ahead of ObservabilityCON. This week, we’re marking the answers. Its AI observability usage charges began October 1, so customers have every reason to ask what that extra visibility buys them when something actually goes wrong.
Zoomtopia has a rather different test. Zoom’s now measuring whether customers return after an AI interaction, and its October contact center release puts more useful context in front of human agents. Genesys is bringing more ServiceNow work into the same queue, with live voice transcription confirmed in its October 19 release. I’d like to know what happens when either handoff loses the conversation or its owner.
ServiceNow’s London forum offers another chance to see autonomous service operations in practice, while Freshworks has widened the asset and dependency information available to IT teams. Both approaches could help when a customer-facing service breaks. The question is how quickly.
We’ve heard plenty of plans. Here’s where the vendors are making progress, what their evidence proves, and which questions still need an answer.
TL;DR
-
Grafana’s ObservabilityCON report card now has confirmed releases to assess: generally available Assistant Watchers and OpenTelemetry-enabled Agent Observability, plus expanded Knowledge Graph context. Customer-journey and incident-response additions remain in preview, leaving questions about costs, human approval, and service recovery.
-
Genesys’s October 12 ServiceNow updates improve email routing and make accepted work easier to measure. Its October 19 release also adds real-time voice transcripts to ServiceNow Agent Workspace, subject to eligible Genesys Cloud licensing and regional rollout.
-
Zoom’s October 17 Contact Center release improves ServiceNow screen pops and call routing. Zoomtopia’s new Unified Context Layer aims to preserve customer history across interactions, while U.S. Oral Surgery Management uses Zoom Contact Center and Phone data to follow patient transfers between centralized scheduling and individual practices.
-
Freshworks has expanded Freshservice’s asset visibility, while Grafana’s October 19 paging update and Twilio’s new Brazil and Thailand voice incidents show why incident recovery needs careful measurement. Infobip’s October 19–20 messaging problems add another supplier to that test.
What Did Grafana Announce at ObservabilityCON 2026?
Grafana picked an awkward month to make its case. AI observability charges began October 1, while its notification history raised uncomfortable reliability questions. ObservabilityCON supplied some actual releases to judge: Assistant Watchers and OpenTelemetry-enabled Agent Observability are generally available. Watchers can catch changes missed by ordinary alerts, and Knowledge Graph now spans Grafana Cloud stacks. Service ownership mapping remains in private preview.
There’s a customer angle, too. Session Replay is in public preview and Critical User Journeys in private preview. They could help explain a failed web interaction; I’d still like Grafana to trace a dropped contact center transfer. LexisNexis Risk Solutions described an investigation-to-ServiceNow-to-on-call workflow. Its Neil Wilson highlighted “connecting service ownership, dependencies, operational knowledge, and customer impact.” Who checked recovery?
Then there’s the bill. Faster full-text log search is generally available without an additional charge. Grafana Pro still lists $1.50 per 1,000 additional agent generations and $2 per million evaluation or guard tokens after allowances, with other platform, telemetry, and model costs separate. Price one resolved incident for us.
Grafana’s notification history complicates the reliability pitch. On October 19, it closed the Thailand SMS case by clarifying that some destinations aren’t supported. Did backup push or phone alerts reach the engineer? That’s a rather important distinction from “recovered.”
Managed Sandboxes, in public preview, can prepare proposed fixes for human approval. Grafana Workflows is also in public preview; the October 21 IRM session promises people control over findings. If a suggested fix changes contact center routing, who signs off and who can reverse it?
What Did Genesys Change About Contact Center and ITSM Handoffs?
Genesys and ServiceNow have made a series of practical improvements to service management and contact center handoffs over the past few months.
On October 12, Genesys updated Unified Experience so ServiceNow email details, including the sender, subject, and message content, can help route work by priority or skill. Eligible emails in ServiceNow CSM Workspace can also receive automatic acknowledgments. Handy, although I wouldn’t count a polite auto-reply as a resolved customer problem.
The integration already routes ServiceNow ITSM incidents as work items, while September brought agent-first callbacks and July expanded ITSM digital messaging. That could save customers unnecessary transfers, provided somebody actually accepts the work when it reaches their queue.
Genesys made that distinction easier to measure on October 12. The old ‘Answered’ metric included work offers agents declined or let time out. Those now count as ‘Answer Attempted’, while ‘Answered’ measures accepted work. It’s a welcome correction, and I’d happily see other vendors make it too. The change applies to the Work Automation add-on.
Live voice has now arrived, too. Genesys’s October 19 release confirms real-time transcripts in ServiceNow Agent Workspace, where Now Assist can use them during calls. That could spare agents plenty of retyping. Eligible licenses include CX 1 with Digital Add-on II and CX 2, 3, or 4 variants, with regional rollout scheduled through the week.
What Did Zoom Announce at Zoomtopia 2026 for Contact Centers?
Zoomtopia gave us something more useful than another containment percentage. Zoom’s new Unified Context Layer aims to preserve customer history across Contact Center, Phone, and other interactions. U.S. Oral Surgery Management already uses Zoom Contact Center and Phone data to follow patient calls from centralized scheduling to individual practices across more than 130 locations. That’s closer to the handoff evidence I’d like to see, although I’d still want to know what happens when a transfer fails.
September’s ‘resolved without return’ metric gets closer. Zoom counts a contained chat or voice interaction as resolved only if that customer doesn’t return within a defined window. I’d ask how long the window lasts and whether a follow-up call after a chat counts.
More interesting for service teams is Zoom’s October 17 Contact Center release, now marked ‘Released’. ServiceNow screen pops use a single window, while CTI panels can display Virtual Agent summaries. Administrators can group recommended transfer queues and adjust waiting callers’ priority. Zoom also lists outbound BYOC/BYOP number-based routing, subject to enablement. Those are useful changes to test on a real call. The planned warm-transfer-to-flow feature was pulled after deployment problems. Better that than discovering the problem mid-transfer.
There’s a deadline too. Customers using the legacy CTI V2 adapter URL, including ServiceNow integrations, should update it before December 1 to avoid potential service disruption. September’s analytics changes distinguish system-disconnected calls from customer hang-ups.
Zoom’s maintenance diary lists October 19–21 work moving Zoom Phone SIP registrations from AMS3 to FRA3, with possible brief disconnections. That isn’t a confirmed Contact Center outage. Still, I’d like Zoomtopia to show what happens when a transfer drops: who notices, and can the caller get through on the second try?
What Did ServiceNow Announce at World Forum London 2026?
ServiceNow heads into its October 20 London forum with plenty to explain. Its October 6 AI Workflow Factory is available, while Autonomous Engineer remains in early access. We’ve already covered the wider AI governance promises. I’d rather know what happens when a customer-facing workflow breaks and the service desk has to find somebody who can fix it.
