Vonage Contact Center and ServiceNow Voice integration guide

1 Overview
- 1.1 Functional Scope
2 Operational constraints and system boundaries
- 2.1 Usage and environment constraints
- 2.2 Functional Scope Boundaries

Overview

You can integrate Vonage Contact Center (VCC) with ServiceNow Voice (SNOW) to enable agents to manage voice interactions without leaving the ServiceNow environment.

In this section, you can find the technical specifications and configuration steps required to integrate your environment with ServiceNow Voice to enable the following:

Handle calls directly within ServiceNow.
Automatically create and manage interaction records.
Synchronise agent presence between Vonage and ServiceNow.
Route voice interactions through ServiceNow’s Advanced Work Assignment framework.

This guide contains the following sections:

Integration logic and end-to-end flow

Functional Scope

The integration is optimized to align telephony events with specific ServiceNow business modules. It focuses on automating record management and enhancing agent workflows within two primary use cases:

Customer Service Management (CSM): Facilitates customer-facing support by correlating inbound calls with Customer/Consumer records and automating the lifecycle of Cases and Service Requests.
IT Service Management (ITSM): Supports internal service desks by linking voice interactions to Incident and Task records, utilizing the internal User (sys_user) table for caller identification.

Operational constraints and system boundaries

To ensure stable operation, administrators and agents must adhere to the following architectural boundaries.

Usage and environment constraints

To maintain session integrity and data accuracy, agents must adhere to the following environmental requirements:

Single browser tab support: The CTI connector supports only one active browser tab. Multiple tabs cause UI errors and dropped calls.
Manual authentication: Silent or automated background login is not supported. Agents must interactively authenticate via the CTI panel when initializing their ServiceNow workspace.
UI state disruption: Refreshing the browser during an active interaction disrupts the UI state. While audio may persist via WebRTC, the CTI interface will lose synchronization with the call lifecycle - the call disconnects for several seconds (duration of the disconnection depends on your machine’s performance and internet speed). Once the page has loaded, the call reconnects, and the UI state resumes.

Functional Scope Boundaries

The current release features the following architectural boundaries:

Agent session concurrency: A single Vonage user account cannot be active across multiple ServiceNow instances or browser sessions simultaneously.
1:1 Account mapping: Only one VCC account can be linked to one ServiceNow instance. Multiple account links cause authentication conflicts.