BUG: zp-input-sms fails to navigate or pre-fill number in Zoom Phone Smart Embed

API and Webhooks
1

API Endpoint(s) and/or Zoom API Event(s)

Description

We are facing a critical regression with the zp-input-sms command in the Zoom Phone Smart Embed widget.

Workflow: Our CRM includes a “Send SMS” button that uses postMessage to trigger the Zoom widget, navigate to the SMS tab, and pre-fill the recipient’s phone number.

Problem: As of recently (the feature was working correctly in January 2026), the zp-input-sms command has become a no-op. While the widget is active and logged in, sending the command does not trigger any UI change. The widget stays on the current tab (e.g., Keypad) and the “To:” field is never populated.

Error?

There is no explicit error message in the parent console. It is a silent failure.

  • The iframe acknowledges the communication (verified because the widget emits a zp-sms-log-event back to the parent).

  • However, the widget UI fails to navigate to the SMS tab or open the compose view.

How To Reproduce

1. Request / Body We are using the exact postMessage implementation from the official documentation:

JavaScript

document.querySelector('iframe#zoom-embeddable-phone-iframe').contentWindow.postMessage({
  type: 'zp-input-sms',
  data: {
    number: '+13055550199'
  }
}, 'https://applications.zoom.us');

2. Authentication method or app type

  • App Type: Zoom Phone Smart Embed (Iframe integration).

  • Auth: User is logged into the widget with a valid Zoom Phone license and SMS enabled.

3. Steps to reproduce the behavior:

  1. Load the Zoom Phone Smart Embed iframe in an authorized HTTPS domain.

  2. Log in as a user with SMS capabilities.

  3. Execute the zp-input-sms command via postMessage.

  4. Observe: The widget remains on the “Keypad” (or current) tab. No SMS compose view is opened, and the phone number is not pre-filled.

4. Additional Environment Info:

  • Iframe Source: [https://applications.zoom.us/integration/phone/embeddablephone/home](https://applications.zoom.us/integration/phone/embeddablephone/home)

  • Browser: Tested on latest Chrome and Edge.

  • Isolation: The issue persists in a minimal, standalone HTML file with zero custom logic, confirming it is not a conflict with our CRM code.