Integrating Genesys Cloud with ServiceNow for automated ticket creation

General Discussion
1

We are integrating Genesys Cloud with ServiceNow for automated ticket creation upon call arrival.

Before I build the webhook, I need to know how this impacts historical data extraction. If we generate a ServiceNow ticket for every interaction, I will eventually need to dump those correlated records for our data lake. Does the ServiceNow integration automatically append the SNOW ticket ID to the Genesys Cloud interaction record, or do I have to query both APIs and join them via an ETL pipeline later?

2

If your ServiceNow instance is hosted on-premise and you are utilizing GC Edge appliances, verify your network topology before deploying this integration.

The webhook payloads originate from the Genesys Cloud AWS environment, not your local Edge servers. I spent hours troubleshooting a failed webhook only to realize our corporate firewall was dropping the inbound traffic because the network config was only expecting traffic from our local Edges. Ensure the GC public IP ranges are whitelisted to hit your ServiceNow endpoint.

3

To maximize the ROI of this integration, you should absolutely pair it with Agent Assist.

Instead of just creating a blank ticket, we use the real-time transcription from the voice channel to automatically populate the ServiceNow incident summary. The AI surfaces the likely issue based on the first 30 seconds of the call, and the webhook fires an UPDATE payload to ServiceNow. This reduced our average handle time by 18 seconds per call.

4

As a supervisor of a 30-agent team, I don’t write the code for these integrations, but I need to know how this affects my floor.

When the system automatically creates this ServiceNow ticket, how does the agent actually see the ticket number? Does it pop up in their Genesys Cloud script, or do they have to manually search ServiceNow to find the ticket that was just created for the customer they are talking to?

5

The most resilient cloud architecture for this pattern is to decouple the systems using an AWS API Gateway and a Lambda function.

Do not point the Genesys Cloud Data Action directly at the ServiceNow REST API. If ServiceNow experiences an outage, your GC Architect flow will hang and drop the call.

Route the GC webhook to API Gateway, let Lambda instantly return a 200 OK to GC, and then handle the ServiceNow ticket creation asynchronously.

# CloudFormation snippet for API Gateway to Lambda
Resources:
  SNowIntegrationAPI:
    Type: AWS::ApiGateway::RestApi
    Properties:
      Name: "GC-ServiceNow-Proxy"
  SNowLambda:
    Type: AWS::Lambda::Function
    Properties:
      Handler: "index.handler"
      Runtime: "python3.9"