Hello Meg,
The conversation object is sent only once when the Screen Pop extension point is triggered. It does not get updated as the interaction state changes. The Screen Pop extension point fires specifically during the alerting phase (when the call is ringing), which is why your Apex class terminates immediately - it's designed to execute once, not continuously.
For Screen Pop on CONNECTED State:
To screen pop when the call is answered (CONNECTED) instead of alerting, you cannot use the Condensed Conversation Information alone. You must:
1.Use the Subscribe Events (postMessage Web API or Lightning Message Service).
2.Build a custom Lightning component that listens for interaction state change events.
3.Trigger your screen pop logic when the state changes to "CONNECTED".
The Condensed Conversation Information can provide conversation data, but it won't detect state changes by itself. You need the Subscribe Events to monitor when the interaction moves from alerting to connected.
In summary: For your use case, you'll need to combine both approaches - use Subscribe Events to detect the CONNECTED state and access conversation data as needed for your screen pop logic.
------------------------------
Gabriel Garcia
NA
------------------------------