Missing or Delayed Codes
If your OTP isn't showing up, walk through this quick checklist. In most cases the code is either in the Inbox already, routed to a notification, or blocked by a simple configuration issue.
TL;DR
Check the JoltSMS Inbox first
Go to Inbox and search/filter by your number. If you use Slack/Discord/Webhooks/Email, the message may have been routed there—it can still be in the Inbox.
Send yourself a test SMS
From a personal phone, send a simple text (e.g., "test 123") to your JoltSMS number and confirm it appears in Inbox.
Verify notifications
Check Slack/Discord channels aren't muted; confirm the Webhook/Email endpoint is correct and not erroring.
If you still don't see it, contact us
Include your number, the sender/app, approximate time, and (if possible) the message body.
Step 1 — Check the Inbox
- Open Inbox and select the affected number.
- Use search to find recent messages.
- Confirm the timestamp is within the last few minutes (OTPs often expire fast).
What to look for
- • The OTP arrived but your downstream notification didn't (muted Slack channel, disabled Discord bot, failing webhook, or filtered email).
- • Multiple codes—some providers resend; always use the latest timestamp.
Step 2 — Test by sending yourself an SMS
- From your own handset, send a simple SMS to the JoltSMS number.
- You should see it in Inbox within a few seconds (allow up to 60s).
- If your test arrives but the vendor's OTP does not, the vendor may block virtual/shared/rental numbers or throttle retries.
Tip: Some apps only deliver OTP to the last verified number or to numbers in specific regions. If you recently switched numbers or countries, update your profile in that app.
Step 3 — Confirm Notifications are healthy
If you rely on Slack/Discord/Webhooks/Email to surface codes:
Slack / Discord
- • Check the channel is correct, not archived, and not muted.
- • Verify the integration is enabled in JoltSMS.
Webhooks
- • Confirm the URL, auth headers, and TLS certs.
- • Make sure your endpoint returns 2xx quickly; long/5xx responses may be retried or dropped by your stack.
- • Check spam/junk folders and any mail rules.
Even if a notification fails, the message should still appear in Inbox. Always check it first.
Common reasons OTPs don't arrive
App/vendor blocks rental or VoIP ranges
Some services only send to carrier-owned numbers or to previously verified numbers.
Rate limiting / cooldown
Too many requests in a short time; wait a few minutes and request a new code.
Region/country mismatch
The app might only send OTPs domestically or from specific short codes.
Number capabilities
Ensure the rented number is SMS-capable for your target country.
Do Not Disturb / carrier features
On the sender side (less common for inbound, but can affect routes).
Vendor outage or routing issue
If your own test SMS arrives but the vendor OTP never does, it's likely upstream.
How to tell "no data" vs. "delayed delivery"
No data
Your own test SMS also fails to appear in Inbox → likely configuration/number issue.
Delayed
Your test SMS appears promptly, but vendor OTP appears minutes later (or not at all) → upstream throttling or blocking.
Advanced checks (optional)
- Numbers page: Ensure the number is Active and assigned to your workspace.
- Notification logs (if available): Look for 4xx/5xx responses on webhooks.
- Try a different sender/app: Helps isolate vendor-specific blocks.
- Try a different JoltSMS number / region: Some services are picky about ranges.
When to contact support
If the Inbox shows nothing for both vendor OTPs and your own test SMS—or you suspect provider/vendor blocking—reach out and include:
- Affected JoltSMS number (E.164 format if possible)
- Sender/app name (e.g., Bank XYZ, WhatsApp, Apple, etc.)
- Approximate timestamps (UTC) for the last 2–3 attempts
- If any message did arrive, a redacted screenshot (remove sensitive data)
- Whether Slack/Discord/Webhook/Email notifications are enabled and working for other messages
We'll investigate routing and advise next steps.