One question: does the "not respond" status also occur when only Genesys is involved?
I'm thinking of 3 possible causes for this status:
1 - The agent didn't accept the interaction (it's worth putting it in auto-answer mode to test if it still doesn't work)
2 - The agent reject the interaction
3 - Some communication problem caused Genesys to not find the agent's Webrt.
In Genesys, perform the following test:

If everything turns green, great.
If something turns red, it's a network communication problem.
Then perform the same test using ServiceNow.
(I don't have one here, but I believe it's similar to Salesforce)

------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
------------------------------
Original Message:
Sent: 03-27-2026 06:01
From: Hafid Bourich
Subject: Calls are not being delivered to the Unified Experience from Genesys and ServiceNow
Hi everyone,
We are currently trying to implement the Unified Experience from Genesys and ServiceNow. We have followed all the steps in the documentation and completed the required configuration on both the ServiceNow and Genesys Cloud sides.
The status mapping between Genesys Cloud and ServiceNow appears to be working correctly. However, calls are not being delivered to the agent within ServiceNow.
It seems that at the moment the interaction is offered, the agent is immediately set to a "NOT RESPONDING" status in Genesys Cloud. Additionally, the call notification does not appear in the ServiceNow workspace, so the agent has no opportunity to accept the call interaction.
Does anyone have suggestions on how to resolve it?
Thank you
#API/Integrations
------------------------------
Hafid Bourich
Technisch Consultant
------------------------------