In brief
The guest typed their number and no code came. Wrong number, provider rate limit, unapproved sender ID, empty credits, provider outage and foreign numbers: six causes, six fixes.
SMS verification is the simplest guest Wi-Fi method: type a number, receive a code, get online. Because the chain is short, finding where it broke is easy too. This post walks through the six points behind "the code never arrived", how to recognise each, and what to do.
First, the chain: the guest types a number into the portal, the box generates a code and sends it straight to the SMS provider's API, the provider hands it to the mobile operator, and the operator delivers it to the phone. The guest's number leaves the box only to reach the provider; the hotspot-box.com platform never sees it. So the fault lies with the guest, the box, the provider or the operator.
1. The number was typed wrong
The most common cause and the least suspected. A leading zero, a missing digit or a forgotten country code. The portal checks the format but cannot know whether it is the right person's number.
How to tell: the box sent the code, the provider reports "delivered", the guest received nothing. What to do: ask the guest to read the number aloud. Show an example format under the number field on the portal.
2. The provider throttled repeated sends to one number
The guest taps "resend" several times without waiting. Providers treat repeated sends to the same number within a short window as abuse and delay or drop them.
How to tell: the first code arrives, the second and third do not; or none arrive and the provider panel shows "rejected". What to do: ask the guest to wait a minute. Put a countdown on the portal's resend button.
3. The sender ID is not approved
In Türkiye the sender name shown above an SMS (the header or sender ID) has to be approved by the provider and the operators. Messages sent with an unapproved or misspelled sender ID are silently dropped; you may not even get an error.
How to tell: no number receives codes, credits may or may not drop, the provider report shows a sender ID error. What to do: check the approval status in the provider panel. The sender ID set on the box must match the approved name letter for letter.
4. Credits ran out
Hotspot-Box works with credit packs (1,000, 2,000 or 10,000) or with your own provider account. In both cases, a zero balance means no code.
How to tell: the panel warns you when SMS credits drop below 100, by e-mail, Telegram or webhook. If the warning came and no pack was bought, this is the cause. With your own account, check the balance in the provider panel. What to do: renew ahead of time. Add the balance to your checklist before busy periods such as holidays or the start of the season.
5. Provider outage
The provider's API or its link to the operator can fail. You changed nothing; codes simply stop.
How to tell: the box logs "send failed" and the provider's status page shows an incident. What to do: define a backup provider chain on the box. When the first provider returns an error, the box hands the code to the second. Two provider accounts are a small cost; a Wi-Fi that does not work on a busy Saturday evening is not.
6. Foreign numbers
Some domestic providers do not deliver to foreign numbers or price them separately. Even a correctly typed number with a country code can be dropped.
How to tell: local numbers work, foreign numbers never receive anything. What to do: define a separate provider route for foreign numbers on the box. Numbers starting with +90 go through the first provider, everything else through the second.
Summary table
| Symptom | Likely point | First move |
|---|---|---|
| One guest fails, others succeed | Wrong number | Check the number together |
| First code arrives, resends do not | Provider rate limit | Wait a minute |
| Nobody receives, no error | Unapproved sender ID | Check sender ID status at the provider |
| Nobody receives, credit warning in panel | Credits exhausted | Renew the pack |
| Nobody receives, box logs errors | Provider outage | Backup provider chain |
| Only tourists fail | Foreign number | Separate provider route |
The fallback: coupons
If the code still does not arrive, the guest should not be left offline. You can generate and print coupon codes in bulk from the panel. A stack of coupons at the till is the fastest fix in your staff's hands when the SMS chain breaks. The coupon code is written to the records as the verification detail, so no gap appears in the chain. Sending codes over WhatsApp can also be set up as an extra option alongside SMS.
The code arrived but was rejected
Beyond the six points there is one more case: the code reaches the phone, the guest types it, the portal refuses it. Three causes stand out. The code has expired; the guest saw the message late and needs a new one. The guest tapped "resend" several times and typed the code from an older message; only the latest is valid. Or digits got mixed up; zero and O, one and I sit next to each other on the keyboard. A line on the portal saying "enter the most recent code" cuts all three.
Example scenario
Picture a fictional seaside cafe. Complaints rise at the start of summer: local customers are fine, tourists get no code. The provider does not deliver to foreign numbers. The fix takes two steps: a second provider account for foreign numbers and a routing rule on the box. During the switch, a stack of coupons goes to the till. At the end of the season a look at the panel shows every tourist login went through the second provider and every local login through the first.
Three habits for routine upkeep
- Log in with your own phone once a week.
- Route the credit warning to Telegram; e-mails get missed.
- Test the backup provider monthly: disable the first one briefly and request a code.
See the products page for provider options and credit packs, and the FAQ for other questions.