Sending SMS From Call Queue Through Phone API

API Endpoint(s) and/or Zoom API Event(s)
POST /v2/phone/sms/messages

Description
I am trying to send sms in a server-to-server app. The original use-case was to automatically send an sms from our marketing team to leads when a certain action is performed. After building out this logic, I found out that Zoom does not allow you to send SMS on behalf of other users. This is a serious limitation when it comes to automation (competitors offer this feature). My workaround was to instead assign that users number to a call queue and send the SMS from there. I am unable to get this working. I have created a call queue, enabled sms, assigned my number to the call queue, and assigned my user as a member to the call queue. I am also an admin on the queue if that matters. My server-to-server app has the required granular scopes.

Sample Post Body:
{

“attachments”: ,

“message”: “Testing sending a message from Zoom api”,

“sender”: {

“user_id”: “XXX…”,

“phone_number”: “+1XXXXXXXXXX”

},

“to_members”: [

{

“phone_number”: “+1XXXXXXXXXX”

}

]

}

Error:*
The post SMS api states that the sender parameter in the body has two required fields: phone_number and user_id. The description for phone_number clearly states “This must be an SMS capable phone number allocated to Zoom Phone within the customer account. Enter the number in E.164 format. This can be a phone number assigned to a user, a call queue or to the Programmatic API endpoint…”.

When I use my user_id (I am a member of the call queue) , I get the following:*
{

“code”: 7028,

“message”: “Do not allow to send SMS.”

}

When I use the call queue id as the user_id, I get:
{

“code”: 1001,

“message”: “User does not exist: XXX…”

}

When I exclude the user_id, I get:
{

“code”: 1024,

“message”: “User does not exist due to missing required params.”

}

How am I supposed to use this api with a call queue? Is the documentation just incorrect?

Hi @ebrewer
Thanks for reaching out to us.
Could you allow me some time to troubleshoot this on my end?
I am aware of the limitation when trying to send SMSs on behalf of another user and I know this is not possible. But I do not know if the workaround you are proposing should work.
So give me some time to reproduce this on my end, and will get back to you with an update.
Thanks again
Elisa

Hi @elisa.zoom do you have an update on this? I need to know if I should create a separate solution or go with another product. Thanks.

Hi @ebrewer
Sorry for the late reply here.
From my testing, I got the same errors than you did, since the call queue is not considered a user and SMS requiere to include the sender’s user_id, this is expected.
As of right now, there is not a workaround for what you are trying to achieve