[URGENT] Zoom Phone Smart Embed: some zp-xxx-event not firing (while zp-contact-match-event works)

Hi everyone,

We are facing a critical issue with Zoom Phone Smart Embed in our internal web application. Since this afternoon, call-related events have suddenly stopped firing, and we need an urgent resolution.

The Issue:

  • zp-contact-match-event is being received correctly. (Confirmed via window.addEventListener(‘message’))

  • zp-call-ringing-event, zp-call-connected-event, and zp-call-ended-event are NOT being received at all**.**

  • This was working perfectly until a few hours ago. No changes were made to our code.

Our Environment:

  • Browser: Chrome

  • OS: Window11

  • Zoom Desktop Client Version: 6.7.8

  • Implementation: Using the Smart Embed iframe with the events parameter.

Troubleshooting already performed:

  1. Verified that “Automatically Call From Third Party Apps” is ON in the Zoom Portal.

  2. Verified that our domain is in the Approved Domains list in the App Marketplace.

  3. Checked the browser console: No CORS or CSP errors, but call events are simply missing from the postMessage stream.

  4. Restarted the Zoom Desktop Client and re-logged in.

Is there a known service outage or a recent API update affecting Smart Embed event delivery?

Any insights or workarounds would be greatly appreciated as this is impacting our production environment.

Thank you.

Hi @user170
Thanks for reaching out to us , I am currently looking into this and will report back to you as soon as I have more information

Thank you for the quick response. I appreciate you looking into this.

If there’s any possibility that the issue is on our end—such as a specific configuration we might have missed or a recent change in implementation requirements—please let us know as soon as possible. We are ready to make any necessary adjustments immediately.

Looking forward to your update.

Thank you @user170
This is an issue on our end and we are working on fixing this ASAP
Will update you when this is fixed

Thanks for your patience @user170
We had an outage on our end and we appreciate your patience. This was resolved on Tuesday afternoon

1 Like