A short code can take a different route than an app
When you enter a carrier’s star-and-hash code, the phone may send it as a USSD request—Unstructured Supplementary Service Data—through the mobile network’s signaling system. Instead of opening a website or app, the phone asks the carrier’s computers to handle a brief command. The carrier can reply with text or a menu, and your next tap or typed response continues the exchange.
That back-and-forth is why a code can show information tied to your account, such as a balance, without requiring you to navigate a carrier app. It is a live conversation with the network, not a lookup stored on the phone.
The same-looking code may do something else
Star-and-hash strings are not all one kind of command. Some are sent to the carrier as USSD; others are interpreted by the phone itself or depend on its manufacturer and software. A diagnostic screen, for example, may come from the handset rather than the carrier. The characters alone do not tell you which system will respond.
Codes also vary by carrier and country, so a string that opens a useful menu on one network may do nothing—or have a different effect—on another. The key distinction is where the request is handled: by the carrier, or by the phone. That determines what information the code can show and why there is no universal star-code directory that works on every device.
