Enterprises already run mature ITSM processes. Many also run customer-facing service operations with different priorities and tools. The trouble starts when one issue touches both worlds. Context leaks, ownership blurs, and customers feel the delay.
ServiceNow can reduce that friction. But the platform only helps if teams treat workflows as shared execution paths instead of separate lanes.
Vonage Premier for ServiceNow Voice is designed to keep context intact when issues cross from IT service management to customer service management in ServiceNow workflows.
Where Cross-Team Friction Actually Starts
Handoffs usually break in familiar places. One team captures the story in its own language. Another team needs the story in a different format, with different fields and priorities. The case moves, but the context does not always move cleanly with it.
That creates three predictable outcomes. Customers repeat themselves. Agents rebuild history from fragments. And the record becomes a patchwork of notes that are hard to act on.
Jonathan Kershaw, Director of Product Management at Vonage, made this point directly:
“Without real-time voice data, case creation occurs post-call with incomplete, inconsistent, and mistyped notes. This leads to poor categorization, missing context in escalations, longer resolution cycles, and more repeat contacts.”
In ITSM and CSM, categorization and context are not admin details. They are the difference between a fast escalation and a stalled queue.
Why Voice Context Matters More When Ownership Shifts
Many of the most complex service interactions still happen on the phone. That is where urgency, emotion, and technical nuance show up at the same time. It is also where agents are most likely to prioritize the live conversation over perfect documentation.
If voice context is captured late, the handoff team often receives a summary that misses key detail. That slows triage and increases rework.
Vonage’s approach is that better continuity comes from capturing context before, during, and after the interaction. That matters when a case escalates mid-call. It also matters when work moves between teams after the call.
The Workflow Moves That Reduce Handoff Drag
The most practical way to reduce ITSM and CSM friction is to remove manual translation steps.
With Vonage Premier for ServiceNow Voice, voice is integrated natively, so agents do not have to rebuild identity, asset context, and incident history from scratch.
Transcription feeds AI assistance while the interaction is live. Workflow tools can also trigger escalations during the call instead of forcing teams to wait until wrap-up.
Kershaw outlined the goal:
“With voice native inside ServiceNow: intelligent routing instantly queries the CMDB using the caller’s identity, matching them to incidents and assets. The agent sees full customer context immediately, eliminating manual search. Real-time transcription feeds Now Assist. The incident auto-updates during the call, and Flow Designer can trigger mid-call escalations.”
For teams trying to operationalize this, the takeaway is simple. Reduce the number of times humans have to re-enter the same story in a different system or format.
How To Prove Handoffs Are Improving
Cross-team improvements can feel subjective unless you anchor them to the right metrics.
Kershaw recommends starting with leading indicators that show workflow change quickly:
- Average handle time and after-call work time show whether agents are still doing heavy admin.
- Case note completeness shows whether records travel cleanly.
- Re-open rate shows whether cases were resolved with enough context to stick.
He also points to first contact resolution as the board-level outcome. When handoffs stabilize, resolution becomes faster and repeat contacts drop.
Moreover, this is where service organizations can connect operational hygiene to their AI strategy.
If the record is incomplete, AI assistance will produce inconsistent outputs. If the record is strong, populated in real time from native voice data, automation becomes easier to govern and scale. The quality of the interaction data is what determines how far AI can go.
How This Links Back to Screen Switching and Automation
Cross-team friction and screen switching tend to rise together. When agents toggle between separate voice desktops and ServiceNow, they lose time and they lose record quality. That makes handoffs noisier.
For the operational baseline and metrics-driven view of that problem, see our companion article on the real cost of screen switching in service operations.
For the practical “conversation to case action” workflow example with Jonathan Kershaw, watch the video interview.
