Number Cannot Be Used
Some websites and apps may decline a number or never deliver an OTP even when your JoltSMS inbox works. This usually isn't a JoltSMS outage—it's the service applying risk checks (anti-abuse, duplicate account detection, country restrictions, etc.).
JoltSMS provides message reception for your rented number. We can't override another service's risk rules or force delivery if they choose not to send.
"The service I requested didn't accept the number. What do I do?"
This is typically caused by checks run by the service (not JoltSMS). They may detect proxies, suspicious automation, repeated sign-ups, or regional mismatches. There isn't anything we can change on our side to bypass those checks.
What you can do
- Try again later (some systems cool down after a window).
- Follow your verification checklist (see below).
- Use a number appropriate to the region the service expects (country/locale rules can be strict).
- Confirm your Inbox receives normal SMS (send yourself a test—if it arrives, JoltSMS is working).
- If the service requires carrier-only or long-term numbers, a short-term rental may be unsupported.
"I've tried multiple times and still don't receive a code."
When your own test SMS arrives but vendor OTPs don't, the provider is likely filtering based on risk signals.
Signals that commonly trigger blocking
Safe-Use & Privacy Checklist
Use JoltSMS responsibly and within each service's Terms. This checklist is for privacy hygiene and reliability—not for evading lawful policies.
IP address hygiene
- Use a reputable provider; avoid IPs known for abuse.
- Align IP geolocation with the number's country when the service expects it.
- If rotating IPs, ensure rotations aren't too frequent or obviously sequential.
Leak checks
- Test for IP/DNS/WebRTC leaks.
- Ensure your DNS resolvers match the expected region.
Browser hygiene
- Clear cookies, cache, localStorage between unrelated sign-ins.
- Keep a clean browser profile; disable unusual extensions.
- Avoid obvious automation; interact at human-like pace.
Fingerprint consistency
- Keep time zone, language/locale, fonts, UA consistent with your number/app region.
- Avoid rapidly switching devices, VMs, or emulators.
Notification sanity checks
- If you rely on Slack/Discord/Webhook/Email, verify those endpoints are healthy.
- Always confirm in the JoltSMS Inbox first.
Action throttling
- Space out retries; excessive attempts often worsen reputation.
- If you hit multiple failures, pause before trying again.
How to tell if this is a JoltSMS issue vs. a provider block
Likely provider block
- • Your self-test SMS appears in Inbox quickly, but the vendor OTP never arrives.
- • The service explicitly says the number is not supported or blocked.
Possibly JoltSMS configuration
- • Your self-test SMS also doesn't arrive in Inbox.
- • In that case, revisit Missing or Delayed Codes (check Inbox, notifications, and number status).
Next steps & alternatives
- Try again later with fewer risk signals (consistent region, clean browser profile, reputable IP).
- If the service requires carrier-owned or long-term numbers, a different number type may be necessary.
- If you continue to see failures across multiple services, contact us with details (see below).
When contacting support, include:
- The JoltSMS number (E.164 if possible)
- Service/app name
- Timestamp(s) in UTC of attempts
- Whether a self-test SMS appears in Inbox
- Any on-screen error verbiage from the service
FAQs
Does JoltSMS block specific services?
No. We receive messages that other services send. If they decide not to send to a given number, we can't make them.
Can you whitelist my number with the service?
No. Whitelisting is controlled by the third-party service.
Will switching numbers help?
Sometimes—if the service flagged the specific number or route. But if the risk signal is your IP/fingerprint/velocity, switching numbers alone won't solve it.