Service leaders already know the pattern. A call comes in and an agent starts hunting. They jump between the telephony desktop, ServiceNow, and whatever system holds account and asset history. The customer waits while the agent reconstructs context.
What looks like a few quick toggles can turn into a structural productivity tax at scale. It also weakens the case record that service teams rely on when work escalates or crosses queues.
Vonage Premier for ServiceNow Voice is designed to address exactly this, removing screen switching in service operations and tightening workflows for teams running ServiceNow.
Where Screen Switching Really Burns Time
Screen switching does not usually show up as one dramatic failure. It shows up as small delays that compound over time.
Jonathan Kershaw, Director of Product Management at Vonage, emphasized this point, claiming that “customer leakage stems from our compounding micro-moments.”
“First, the delay at call answer while searching for customer records. Second, agent distraction during the live conversation due to system-toggling. Third, time lost at wrap-up with manual note-taking and coding. Fourth, the invisible time correcting inaccurate records.”
Kershaw argues that agents can toggle between up to nine systems per interaction in some environments. He also estimates the resulting friction can waste 20 to 30 minutes per agent per day. For a 100-agent operation, that can translate into 33 to 50 person-hours of lost capacity each day.
The knock-on effects compound quickly. Longer calls increase queues, more wrap-up time reduces availability, and poorer notes create rework and reopens.
The “Toggle Tax” Isn’t Just Time, It’s Data Quality
ServiceNow succeeds when the system of record stays clean. That means the right categories, fields, dispositions, and context live in the case.
When voice capabilities sit outside ServiceNow, agents have to translate what happened into fields after the fact, adding delay. It also invites inconsistency and errors. Even small inaccuracies can derail escalations when work crosses teams.
This becomes more challenging as organizations push for more automation and AI support. Generative AI tools only work as well as the input context. If voice context stays fragmented, the summaries, recommendations, and next actions stay incomplete.
How To Measure Screen Switching Without a Science Project
You do not need perfect instrumentation to build a defensible baseline. You need the right signals.
Kershaw recommends tracking four before-and-after metrics across a short sample window:
- After-call work time: isolates admin burden.
- Average handle time: captures both the conversation and the wrap-up.
- Case note completeness: shows whether the ServiceNow record stays consistently populated.
- Re-open rate within 48 hours: often reflects missing context from the initial interaction.
Kershaw also highlighted that the driver is not always call complexity, however, system complexity plays a major role.
A two-week sample on one queue can give platform owners enough evidence to justify workflow changes and prioritize automations.
What Changes When Voice Lives Inside ServiceNow
Vonage Premier for ServiceNow Voice is a native integration that powers the ServiceNow Voice UI and UX from the ground up. Agents work entirely inside ServiceNow’s own interface, with no second application, no additional login screen, and no indication that a separate platform is running underneath.
For ServiceNow-heavy teams, this means voice is handled entirely within the system where the case lives. Agents never leave ServiceNow to manage an interaction. That directly addresses the two-desktop pattern that drags down both speed and data quality, by eliminating the other desktop entirely.
When agents start every interaction with customer context, identity signals, and case history already visible, the conversation begins with clarity rather than catch-up.
The data quality benefit is equally significant. When voice is native to ServiceNow, case records are populated in real time, not reconstructed from memory after the call. That means cleaner categorization, more complete notes, and records that travel intact when work escalates or crosses teams.
How This Connects to Cross-Team Service Handoffs
Screen switching is the visible symptom. Cross-team friction is often the downstream cost.
When issues cross IT service management and customer service management teams, agents need clean context and consistent records that travel with the case. Fragmented voice data makes that harder at every stage, from initial triage to escalation and resolution.
Next in this content arc is our companion piece on bridging ITSM and CSM to reduce friction when issues cross teams. It digs into what breaks when ownership shifts and how teams can keep context intact across queues.
For the practical “conversation to case action” workflow example with Jonathan Kershaw, watch the video interview.
