SMS Delivery Diagnostic & Troubleshooting in Ringover provides a centralized framework to identify, diagnose, and resolve outbound or inbound text messaging failures. Understanding message status indicators, carrier filtering rules, E.164 formatting requirements, and account credit limits ensures uninterrupted business texting. In this guide, you’ll learn how to interpret SMS statuses, run a step-by-step diagnostic check, resolve carrier and credit blocks, and gather the exact data needed when escalating to Ringover Support.
Prerequisites
- An active Ringover Business.
- For US/Canada business texting: an approved A2P 10DLC or Toll-Free verification registration.
Troubleshoot SMS delivery issues and carrier errors
1. Identify your SMS delivery status
Check the visual status indicator displayed beneath your sent message in the Ringover WebApp to pinpoint where delivery stopped.
| SMS Status | Technical Meaning | Immediate Action |
|---|---|---|
| Delivered | Ringover transmitted the SMS and the receiving mobile carrier confirmed handoff to the recipient's handset. | If the recipient claims they did not receive it, ask them to check their device's blocked contacts or spam folder. |
| Pending / Sending | The message is queued at the carrier gateway or waiting for the recipient's phone to reconnect to a cellular network. | Wait up to 24–48 hours for carrier retry cycles before resending to avoid duplicate charges. |
| Failed / Not Delivered | The message was rejected either by Ringover's billing/formatting checks or blocked by the destination carrier. | Follow the step-by-step diagnostic tree below to isolate the exact root cause. |
2. Run the step-by-step SMS diagnostic tree
Work through these four verification checkpoints in order whenever an SMS fails to send or deliver.
Checkpoint A: Number formatting and line capabilities
Verification of international E.164 syntax and line type compatibility.
Run this check first if your message fails immediately upon hitting send.
- Format the recipient's number strictly in international E.164 format (
+[Country Code][Number], such as+33612345678or+14155550199) with no spaces, dashes, or leading zeros. - Confirm that the destination number is a mobile number (standard landlines, toll-free numbers in certain regions, and short codes cannot receive standard P2P/A2P SMS).
Checkpoint B: Account credits, permissions, and sending limits
Verification of available wallet balance, user privileges, and segment quotas.
Check this when outbound SMS stops working across multiple recipients simultaneously.
- Go to your Ringover Dashboard > Billing to verify that your account has positive prepaid SMS credits.
- Review your message length: a standard GSM-7 SMS holds 160 characters (or 70 characters if using emojis or special Unicode characters). Messages exceeding these thresholds split into multiple billable segments, and overly long concatenated messages may be rejected by carriers.
- Each SMS fragment is billed according to your destination, as rates vary between Europe, the UK, and the US. Keep in mind that a single SMS may be split into several fragments.
- The character counter starts at 160 and decreases to 0, representing one SMS fragment.
- Be mindful of special characters, such as emojis 😀 or accented letters like “ç”, as they can reduce the character limit and increase the number of fragments used. Try to use them sparingly to avoid additional charges!
Checkpoint C: Carrier filtering, opt-outs, and compliance blocks
Check this article for more details : 🔗 How STOP, START and HELP work in Ringover
- Verify that the recipient has not previously replied
STOP, which triggers an automatic carrier-level opt-out block until the recipient repliesSTART. - Remove public URL shorteners (such as
bit.lyortinyurl.com), ALL-CAPS text, or high-risk promotional keywords that trigger automated carrier spam firewalls. - For US/Canada destinations, confirm your brand and campaign are approved under A2P 10DLC regulations; unregistered traffic is systematically blocked by North American carriers.
3. Check CRM integration SMS sync issues
If your SMS delivers in Ringover but fails to appear inside your connected CRM (such as HubSpot, Salesforce, or Pipedrive), inspect your integration mapping.
- Go to your Ringover Dashboard > Store > Integrations and click on your active CRM.
- Confirm that the Log SMS messages toggle is enabled for both incoming and outgoing texts.
- Ensure the contact's phone number in your CRM is saved in E.164 format so the integration can match the thread to the right contact record.
4. Gather required details before contacting Ringover Support
If an SMS continues to fail after completing all diagnostic checkpoints, collect at least two recent examples (less than 48 hours old) so our telecom engineers can trace the carrier logs.
- Sending Number: Your full Ringover phone number in E.164 format.
- Recipient Number(s): The destination mobile number(s) in E.164 format and their mobile network operator (if known).
- Exact Date, Time, and Time Zone: The precise timestamp of each failed SMS attempt (within the last 48 hours).
- Message Content & Direction: Whether the issue affects outbound, inbound, or both directions, along with the exact text body sent.
- Error Screenshot: A screenshot from your Ringover WebApp showing the failure icon or error message.
FAQ
Why did my single SMS split into multiple messages and deduct extra credits?
Standard GSM-7 text messages allow up to 160 characters per segment. Including a single emoji, accent, or non-standard Unicode symbol switches the encoding to UCS-2, reducing the limit to 70 characters per segment. Messages exceeding that limit are automatically split into concatenated segments.
Can I send SMS messages to international mobile numbers?
Yes, provided your Ringover account has sufficient prepaid credits for international SMS rates and the destination country's carriers do not restrict incoming international A2P/virtual number traffic. Always enter the full + country prefix.
Why can I receive SMS on my Ringover number from individuals, but not verification codes (2FA/OTP)?
Many banks, social networks, and authentication providers send 2FA codes via short codes or restrict delivery to VoIP/virtual numbers for security reasons. Virtual numbers cannot guarantee receipt of automated short-code OTP messages.
🎉 You now know how to diagnose and resolve SMS delivery issues in Ringover and can keep your customer text communications running smoothly!