WhatsApp says the new UK number is already registered, or the code never arrives

If you need the number for one specific app, plan for the case where that app says no. The app decides whether a registration goes through. It looks at the number, but also at the phone, the connection and the sign-up history of both. We cannot see those checks and we cannot change them.

We do not offer a replacement number or a refund because an app declined. A second line would sit behind the same phone and the same connection, so it would usually meet the same refusal, and the QR of a UK number is single use. We would rather say that up front than let it become an argument later.

What the line does give you is a real UK mobile number on an eSIM that receives incoming SMS and incoming calls. It does not include mobile data, outgoing calls or outgoing SMS, so it sits alongside your normal SIM. Details are on /uk-esim/ and the published terms are on /refund/.

The message reads as if someone else owned the number. It does not prove that. Each +44 line is published as unused before your first activation, and a previous owner is not the usual explanation for this error.

Other things produce the same wording. An earlier attempt of yours may have left a registration half finished on the app's side. The number may already be linked to an account of your own that you forgot about. Or the app is declining this attempt because of the phone or connection you are registering from, and shows its existing-account message. From the screen you cannot tell these apart, which is why the steps below start with the cheap, reversible ones.

The app is refusing the registration. A code from any other app or sender is proof that the line itself receives SMS.

"Too many attempts, try again later" is a cooldown. Stop requesting codes and wait it out; asking again every minute does not help delivery and tends to keep the lock in place.

"We couldn't send an SMS" or a code that never appears points to delivery, or to a number typed wrongly. Check the format first, then try the other-app test.

A code that arrives for one app but not another is the most useful clue you can get. It means the line works and the second app is declining. Telegram adds one wrinkle: its FAQ, checked October 2026, says it may send the login code inside Telegram instead of by SMS if you recently used one of its apps on another device. If Telegram is signed in anywhere, look there before concluding nothing was sent.

Requesting codes over and over. It does nothing for delivery.

Moving the eSIM to another phone. An eSIM is tied to the phone that installed it, and the UK QR is single use and cannot be reissued, so you could lose a paid line that cannot be recovered. When this page says use another device, it means the app on another device, never the eSIM.

Installing the eSIM with a VPN, iCloud Private Relay or Private DNS on. Turn all three off while you install, because they can interrupt the profile download.

Run the other-app test and note the result. If a code from a different app arrives, the line is fine and the app is the one refusing. Wait several hours, delete and reinstall the app cleanly, and if you can, start the registration from another device while the eSIM stays where it is. The code still arrives by SMS on the phone holding the eSIM, and you type it in on the other device.

If no app delivers any code, check that the +44 line shows signal, using the troubleshooting guide linked below. Reception is patchy in a few markets according to buyer reports, Russia, China and Hong Kong among them, so look at /uk-esim-coverage/ for where you are. Your order and line status are at /number-status/.

We cannot promise that any app will accept the number, we do not issue replacement numbers for an app refusal, and UK number orders are not refunded. If a payment or order problem sits on top of this, the support chat can look at it.