Troubleshooting: SMS won't send or isn't delivered
Diagnose and fix SMS that fail to send or never reach the customer: provider balance, sender number, credentials and webhook.
When an SMS gets stuck on "Sending" or the customer never receives it, the cause is almost always one of three things: provider balance, the sender number, or the channel credentials. This guide helps you isolate the problem fast.
Before you start
- Admin access in Omnifox.
- Access to your SMS provider dashboard (Twilio or another supported provider).
- An SMS channel already connected. If you don't have one yet, see How to connect SMS.
Step 1: Pinpoint where it fails
- Open the conversation in the Inbox and check the message status.
- If it shows Failed or an error icon, hover over it: Omnifox surfaces the reason the provider returned.
- Separate two cases: the message never leaves Omnifox (send error) or it leaves but isn't delivered (provider or destination-number issue).
Step 2: Check your provider balance
The most common cause of silent send failures is a depleted balance.
- Sign in to your provider dashboard (Twilio).
- Verify available balance and that the account is not in trial/test mode.
- Top up if it's at zero. Trial accounts can only message verified numbers.
Step 3: Verify the number and credentials
- In Omnifox go to Settings → Channels and open your SMS channel.
- Confirm the Account SID, Auth Token and Phone Number are current. If you rotated the token at the provider, update it here too.
- Make sure the sender number is SMS-capable and active (not suspended or released).
Step 4: Check the inbound webhook
If you can send but can't receive replies, the webhook is the suspect.
- Copy the Webhook URL the channel shows in Omnifox.
- Paste it into the number's configuration in your provider dashboard.
- Save and send a test SMS from another phone to the number.
Verify it's fixed
- Send a test SMS from Omnifox to your mobile and confirm it turns to Delivered.
- Reply from the phone and confirm the message lands in your inbox.
If it still doesn't work…
- Authentication error (401/403): wrong credentials or a rotated token. Re-paste them.
- Invalid or unauthorized number: in the US and Canada, at-scale sending requires A2P 10DLC registration; without it, carriers block the traffic.
- Truncated or split message: you exceeded 160 characters per segment; see SMS limits and costs.
- One recipient never gets it: they may have replied STOP and been added to the carrier's opt-out list.
Tips
- Set a low-balance alert with your provider so you don't run dry mid-campaign.
- Always test with a real number you own before launching a bulk send.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.