Skip to main content
Found Your Voice
Oct 22, 2026 11:35 AM UTC
Question

Unable to send SMS from my Claude MCP connector

Hello,

 

For the last few weeks I’ve integrated Claude to send out appointment reminder texts in the mornings to people I have booked calls with that day. As of yesterday, it returns an error every time I try and get Claude to send a text. 

 Every send_sms call comes back with:

{"data":{"status":"rejected","retryAllowed":false,"reason":"verification_unavailable"}}

Details:

  • Sender: my own direct number, which is SMS enabled. SMS from this number works fine through other routes, including the RingCentral app and a Make scenario, and those messages show as Delivered in my message store.
  • Recipient: US mobile numbers in E.164 format.
  • Each attempt used a new request UUID. Two attempts on 10/22/2026 around 11:07 UTC, both rejected the same way.
  • Other tools on the same connector work normally: call log, call AI notes, and the SMS and voicemail inbox.
  • The calls were made from an automated Claude session and from a Claude Artifact page, not from the Claude chat window.

Questions:

  1. What does “verification_unavailable” mean for send_sms?
  2. Is this a known issue and is there a fix, or is this likely something on my end?

Thanks,

Kent

3 replies

ByrneReese
Community Manager
Product Manager
Nov 2, 2026 6:44 PM UTC

​@KentHBSG I am so sorry you posted this and no one replied right away. I have this feeling that another user had a similar problem and we may have fixed it. 

What the error means. verification_unavailable means the SMS tool couldn’t complete its pre-send checks, so it stopped. Those checks confirm that the sending number is SMS-eligible on your account and that the sender and recipient numbers are valid. Nothing was sent, and the error doesn’t mean your message or numbers were rejected. A genuinely invalid sender or destination returns a different reason, such as sender_not_allowed or country_unverified. retryAllowed: false is intentional. The tool won’t auto-retry a send it couldn’t verify.

Things to try:

  1. Wait a minute and send again from scratch. If the cause was a temporary RingCentral API issue or rate limit, a fresh attempt will usually succeed.
  2. Confirm the sender number. It must be a number on your own extension, or your company’s main number, that has SMS enabled. Use it in full E.164 format, for example +16505550123.
  3. Re-authenticate. Disconnect and reconnect the RingCentral connection in your client so the session gets a fresh token, then retry.
  4. Check the account. If your account has a very large number of phone numbers, over roughly 500, the sender check can hit an internal limit. If that’s you, tell us. We’d treat it as a bug on our side.

What would help us diagnose it. Please share the following, without any message content or phone numbers:

  • Approximate time of the failure, with timezone
  • The requestId from the tool’s request or response, if your client shows it
  • The client you’re using, such as Claude, ChatGPT or Cursor
  • Whether it happens every time or only sometimes, and whether it happens with every sender number

With that we can find the failing step in our logs, which will show whether it was a RingCentral API error, a response we couldn’t validate, or a limit on our side. We’ll update this thread once we know.

New Participant
Nov 11, 2026 1:46 AM UTC

Same error here since about Nov 7 (it worked Nov 2). Details as you asked:

- Client: Claude Code CLI 2.1.310 on Windows, in both the interactive terminal and headless claude -p. The connector is added by URL (mcp.labs.ringcentral.com/ringex/phone); the server reports ringex-phone 1.2.3, protocol 2026-07-28.

- It fails every time, immediately, and no approval prompt appears: {"status":"rejected","retryAllowed":false,"reason":"verification_unavailable"}

- requestIds, Nov 10 2026, US Central: 031b7a72-97d6-4c81-9a90-dd385154f64c (12:16 PM), 730fafd4-ad7a-4505-8aa0-0a2ac1f7127c (12:21 PM), 5f0c2a71-3b8e-4d2a-9c41-7e6b1d2f8a90 (about 12:24 PM, interactive), 8a6d3e21-4c5f-4b7a-9e12-3f0a5b7c9d14 (about 12:40 PM, interactive).

- Same sender (my own direct number on my extension) and same recipient: the Claude desktop/web app, approving each text, does deliver, and the deprecated message_store_create_smsmessage delivers from Claude Code too. So the number looks SMS-eligible and the check looks host-dependent.

- Re-authenticated the connector on several accounts, with no change.

 

Questions: Is Claude Code supposed to work as a host for send_sms? And is there a supported way to send from an automated session? We send one "your emergency call is confirmed" text per after-hours service call, and the legacy tool goes away on Nov 17.

dakong
Community Manager
Community Manager
Nov 12, 2026 6:50 AM UTC

​@BobNWHVAC Please try again. It should be fixed now