When a text fails to send, VipeCloud flags it in red on the contact record and in Conversations. This article covers how to open the error details for a failed text, what to check first, the failures VipeCloud catches before the carrier receives a text, and what each carrier error code means.
What Should I Check First When a Text Fails?
Most failed texts come down to one of four things, and you can fix each of them yourself. Check them in this order before you look up the code.
Check that the contact has a mobile phone number on their contact record.
Check that the contact hasn't opted out of your texts.
Check that your account has text credits available.
Check that your campaign registration is approved.
How to View the Error Details for a Failed Text
The error details tell you which entry below applies to your text.
Open the contact record, or open the conversation in Conversations.
Find the failed message. It has a red badge that starts with Error - followed by a carrier code or a reason.
Click the red badge to open the Text Error Details pop-up.
The pop-up shows an Error Code and an Error Message when the carrier rejected the text. When the text failed before it reached the carrier, there is no Error Code, and the pop-up shows only the Error Message with the reason VipeCloud recorded. In the web app, the pop-up also shows the Message ID.
If a failed text shows a Send failed badge, VipeCloud has no detail recorded for it, and the pop-up says so. This is on our side.
Why Does My Failed Text Have No Error Code?
Some texts fail inside VipeCloud before the carrier receives them, so there is no carrier code to show. These texts still show in red, and the badge and the Text Error Details pop-up show the reason instead of a number. The most common reasons:
This contact has opted out. - The contact opted out of your texts, so VipeCloud did not send it. You can text them again only after they opt back in. See How To Manually Unsubscribe Or Re-Subscribe Contacts In The Webapp.
Texas Text Messages Unavailable Without Explicit Verification Per SB-140 - The contact has a Texas phone number that hasn't been verified for texting under Texas SB 140. See Texas Senate Bill 140 (SB 140) and Text Messaging Compliance.
Incorrect To number - The contact's mobile phone number couldn't be read as a number VipeCloud can text. The reason is followed by the number on file, so you can see what was entered. Correct the mobile phone number on the contact record and send the text again.
AI Booking Agent send errors - When the AI Booking Agent can't send its text, the reason it ran into appears on the message.
Long reasons are shortened on the badge. Click the badge to read the full reason in the pop-up.
10000 to 10004: Texting provider account errors
Codes 10000, 10001, 10002, 10003 and 10004 come from settings on our texting provider's account, and their messages can mention a subscription plan, a subproject, a space, a trial account or API tokens. For example, 10000 reads "Subprojects are not available as part of your currently selected subscription plan". None of them refer to your VipeCloud plan or settings. This is on our side.
11200: HTTP Retrieval Failure
The texting provider couldn't load an image or link in the message. Check that the image or link opens in your browser, attach it again, and send the text again.
11750: The response body to SignalWire's request is longer than allowed
The message or its attachment was too large for the texting provider. Shorten the message or use a smaller file, then send it again.
11751: MMS -> Media exceeds mobile operator size limit
The file attached to your text is too large for the carrier to deliver. Reduce the file size and send the text again.
12100: Document Parse Failure
The texting provider couldn't read the message's format. This is on our side.
12300: Invalid Content-Type
The message reached the texting provider in a format it didn't accept. This is on our side.
13221: Dial -> Number: Invalid Method Value
The texting provider couldn't connect to the number. This is on our side.
15002: Call Progress: Queue Timeout
The message waited too long in the provider's queue and timed out. Send the text again.
21210: 'From' phone number not verified
The number the text was sent from isn't verified with the texting provider yet. This is on our side.
21212: Invalid 'From' Phone Number
The texting provider didn't accept the number the text was sent from. This is on our side.
21217: A call or SMS is placed to a destination which is not enabled for the region
The contact's number is in a country or region your number can't text. Check the country code on the contact's mobile phone number, and correct it if it was entered wrong.
21219: 'To' phone number not verified
The texting provider hasn't verified the contact's number for this sending number. This is on our side.
21601: From number is not an SMS-capable phone number
The number the text was sent from can't send texts. This is on our side.
21602: Message body is required
The text was blank. Add your message and send it again.
21603: Invalid 'From' Phone Number
The number the text was sent from isn't formatted the way the provider expects. This is on our side.
21604: Invalid 'To' Phone Number
The contact's mobile phone number is invalid or formatted incorrectly. Correct it on the contact record and send the text again.
21610: Message blocked by user reply with STOP
The contact replied STOP, so the carrier blocks your texts to them. You can text them again only after they text START to your number.
21611: This 'From' number has exceeded the maximum number of queued messages
Your sending number has too many texts waiting to go out. Wait a while and send the text again.
21617: The concatenated message body exceeds the 1600 character limit
Your message is longer than 1,600 characters. Shorten it or split it into separate texts.
21620: Invalid media URL(s)
One of the images or files in your text couldn't be reached. Attach it again and send the text again.
21623: Number of media files exceeds allowed limit
Too many files were attached to one text. Remove some attachments, or send them in separate texts.
21717: Number must be assigned to a Campaign to send messages
Carriers only deliver texts from numbers linked to an approved campaign registration. Check that your campaign registration is approved. See Texting 101.
30002: Account suspended
The texting provider suspended the messaging account over a policy or usage issue, and our team has to review it with the provider. Ask in chat for a review of a texting account suspension, and include the Message ID and the Error Code from the Text Error Details pop-up.
30003: Unreachable destination handset
The contact's phone couldn't be reached. It may be turned off or out of service. Send the text again later.
30004: Message blocked
The carrier or the contact's own phone settings blocked the text. Reach the contact another way, such as email.
30005: Unknown destination handset
The carrier couldn't confirm the contact's number exists. Confirm the number with the contact and correct it on the contact record.
30006: Landline or unreachable carrier
The number is a landline or is on a carrier that doesn't accept texts. Add a mobile phone number to the contact record, or reach the contact by phone or email.
30007: Carrier violation
The carrier filtered the text because it didn't meet the carrier's rules, which can be about volume, timing or content. Our team can review the message with the carrier. Ask in chat for a carrier violation review, and include the Message ID and the text you sent.
30008: Unknown error
The carrier didn't say why the text failed. Send the text again.
30010: Message price exceeds max price
The texting provider's price limit stopped the text. This is on our side.
30011: MMS Sent: Expired, Rejected, Failed, or Not Supported
The carrier didn't deliver the text as an MMS. Send it again as a plain SMS: under three segments, about 459 characters, and without images or videos. Emojis lower that character limit considerably.
30022: Campaign Registry Throughput Limit Exceeded
Your number sent more texts in a short time than your campaign registration allows. Wait a while and send the failed texts again.
30027: T-Mobile Daily Message Limit Reached
T-Mobile's daily limit for your number has been reached. Send the text again tomorrow.
4000: Invalid capabilities for phone number
The sending number doesn't support this type of message. This is on our side.
4001: Insufficient balance - cost for phone number registration exceeds balance
The texting provider's balance didn't cover a phone number registration. This is on our side.
53603: Internal failure while processing media
The texting provider couldn't process the attached file. Attach a different file or format, such as a JPG instead of a PNG, and send the text again.