WhatsApp verification proves you control a phone number by receiving a one-time code over SMS or voice call, then entering it in WhatsApp or WhatsApp Business (or completing Cloud API / platform registration). A Create Numbers custom UK mobile can be used once it is live on a SIM, eSIM or virtual host and can accept that OTP. WhatsApp is large enough that getting this right matters commercially: Meta indicated more than 3 billion monthly active users in Q1 2025 remarks, and Sensor Tower reported over 54 million UK WhatsApp app monthly active users by March 2025 (Sensor Tower — Leading social brands UK Q1 2025).
Personal WhatsApp vs WhatsApp Business vs Business Platform
Pick the product that matches how you message customers before you fight the OTP screen. WhatsApp Messenger is the consumer app; WhatsApp Business is the free business app for SMEs (profiles, quick replies, catalogues); WhatsApp Business Platform (Cloud API / BSP partners) is the programmable stack for larger volumes. Meta’s help materials require a number you own that can receive SMS or calls, and they list unsupported categories such as some VoIP, toll-free and premium styles depending on product path (WhatsApp Help — Register for WhatsApp Business). Esendex’s 2025 round-up cited roughly 200 million WhatsApp Business monthly actives globally (July 2023 figure) and estimated about 55,000 UK medium-to-large businesses using WhatsApp in 2024 (Esendex — WhatsApp statistics 2025).
| Product | Who it fits | Number rules (high level) |
|---|---|---|
| WhatsApp Messenger | Personal / informal | One primary number per app account on a device |
| WhatsApp Business app | SMEs on handsets | Own number; SMS or “call me” voice code |
| WhatsApp Business Platform | API / BSP / Contoso-scale | Own number; SMS/voice OTP; migration rules if already on consumer app |
You generally cannot run the same number on consumer WhatsApp and the Business app/platform at once without migrating or deleting the old registration. Plan which surface owns the Create Numbers mobile.
Number eligibility and what Meta rejects
Use a number you control end-to-end, in full international format, that can receive international SMS or voice OTP. Mobile numbers are the most reliable; landlines and some voice-capable virtual mobiles can work if they accept international calls; short codes, many toll-free numbers, and IVR-gated lines are poor fits unless IVR can be disabled for the activation call (Bird docs summarising accepted types; Meta developer phone-number guidance). Create Numbers supplies UK mobiles (07) — a strong default for Business app verification when SMS is working.
| Usually workable | Often problematic |
|---|---|
| UK 07 mobile on MNO/MVNO SIM or eligible VMN | Short codes |
| Voice-capable virtual mobile that receives OTP SMS/call | IVR / call trees blocking the automated voice code |
| Landline that accepts international voice OTP | Numbers that cannot receive UK/US-origin verification calls |
| Fresh number not already registered to another WhatsApp user | Banned numbers until appeals succeed |
Providers such as tyntec note verification codes may originate from the UK or US. If your line blocks international inbound voice/SMS, platform onboarding can fail even when UK domestic SMS works (tyntec help).
Before you tap “Send code”
Do not start OTP until the Create Numbers mobile is ported and tested. Fulfilment is typically a PAC in 2–4 weeks (delivery); rushing WhatsApp against an unused PAC wastes lockout timers. WhatsApp’s own help warns that guessing codes can lock you out for a period, and that weak connectivity or call-blocking apps break registration (WhatsApp Help). Ofcom’s CMR 2025 recorded 88% overall mobile customer satisfaction in 2024 — but rural reception satisfaction lagged urban (77% vs 81%) (Ofcom CMR 2025), so move to strong Wi‑Fi/signal before verifying.
| Checklist | Pass criteria |
|---|---|
| Number live | Inbound SMS from a friend works |
| International path | Can receive OTP SMS/call (test host if virtual) |
| Correct product installed | Business vs Messenger vs API decided |
| Format ready | Country = United Kingdom; no trunk 0 after +44 |
| Blockers off | No call-blocking / task-killer killing the SMS |
| Access to SMS inbox | Handset SIM tray or gosimless email/SMS log |
Step-by-step: WhatsApp Business app on a Create Numbers mobile
Complete registration on the handset that will run day-to-day Business messaging, with the SMS inbox visible in the same session. Esendex reported 83% of WhatsApp downloaders open the app daily (2025 stats compilation) — treat the Business number as production infrastructure, not a toy (Esendex).
- Finish Get connected so the custom number receives SMS.
- Install WhatsApp Business (not only Messenger) from the official store.
- Accept terms; choose United Kingdom and enter the number without a leading
0(example shape:7xxx xxx xxxbeside +44). - Request the SMS code; watch the SIM inbox or gosimless SMS-to-email log.
- If SMS fails when the timer ends, use Call me for the automated voice code (WhatsApp Help).
- Enter the 6-digit code exactly; do not guess.
- Set up your business profile (name, category, hours) before sharing the QR or link publicly.
| Step outcome | If it fails |
|---|---|
| No SMS | Confirm number live; try voice; check virtual SMS log |
| Voice fails | International inbound blocked; fix host/network |
| “Number not valid” | Re-check +44 format; unsupported number type |
| Instant lockout | Wait out timer; stop guessing |
Using gosimless for WhatsApp Business
Create Numbers partners with gosimless for virtual hosting aimed at WhatsApp Business without a second plastic SIM. GoSimless markets UK virtual mobiles from about £5.99 / month, SMS-to-email, and multi-number control on one device (gosimless.com). That path is ideal when personal WhatsApp already occupies your consumer SIM and you need a second verified identity. Full hosting context: Virtual number hosting.
| gosimless + CN pattern | Why use it |
|---|---|
| Personal WhatsApp on consumer SIM | Keep friends/family separate |
| Business WhatsApp on Create Numbers via gosimless | Memorable 07 + shared SMS inbox |
| Optional call forwarding | Voice customers still reach you |
During verification, keep the gosimless SMS log / email open on a second screen before you request the code so you can paste within the timer.
WhatsApp Business Platform (API) notes
API / BSP registration still hinges on an eligible number and OTP, but adds Meta Business Manager, package selection and, if the number already lives in the consumer app, an official migration path rather than a naive second registration. Meta’s developer docs require ownership, country/area codes (no short codes), SMS or voice capability, and note that numbers already on WhatsApp must be deleted or migrated first (Meta — Business phone numbers). If you are buying a Create Numbers mobile purely for API inbound, decide the BSP early so display name and green-tick business verification (Meta Business verification — separate from phone OTP) can proceed in parallel [TBC: your recommended BSP list].
| Track | Phone OTP | Meta Business verification |
|---|---|---|
| Proves | Control of the 07 | Legal business identity |
| Blocks go-live if missing | Cannot message on that number | Limits official business features / display |
| Owner | You + SMS path | You + Companies House / docs via Meta |
Running Business and personal accounts on one phone
Android commonly supports WhatsApp + WhatsApp Business side by side; iPhone users often need dual-SIM / eSIM, Continuity tricks, or a virtual number so the Business line is not fighting the personal SIM. GoSimless explicitly markets “two numbers, one device” for this gap (gosimless.com). Sensor Tower’s UK figures show WhatsApp’s audience dwarfs many social apps (54m+ MAU) — assume staff already have personal accounts that must remain untouched (Sensor Tower).
| Handset reality | Practical approach |
|---|---|
| Android | Install both apps; assign Create Numbers to Business |
| iPhone, dual-SIM | Put business number on second SIM/eSIM |
| iPhone, single SIM | Virtual number (gosimless) + Wi‑Fi/data |
| Shared team device | MDM / written access policy; prefer API for teams |
After verification: hygiene and quality
Verification is not the finish line — protect the device session, publish the number only when stable, and avoid spammy broadcast behaviour that triggers Meta rate limits or user blocks. Ofcom notes classic SMS/MMS volumes continue to decline while online messaging grows (CMR 2025 highlights hundreds of billions of OCS messages) — customers still expect WhatsApp replies to feel personal (Ofcom CMR 2025). Keep SIM swap security tight so attackers cannot steal the number and re-verify WhatsApp onto a handset you do not control.
| Do | Don’t |
|---|---|
| Enable two-step authentication in WhatsApp | Share device unlock codes |
| Document who owns the handset / gosimless login | Run marketing blasts cold without opt-in discipline |
| Re-test OTP after every SIM swap | Assume the session survives forever |
| Match profile name to your real trading name | Use a number still mid-port |
Troubleshooting verification failures
Work the matrix in order: reachability → format → product rules → timers → host limitations. WhatsApp’s help suggests sending a test SMS to the candidate number and opening https://www.whatsapp.com/business/ on the phone’s browser to confirm connectivity (WhatsApp Help). If you are still inside Create Numbers’ 2–4 week fulfilment window, pause WhatsApp until Get connected is done.
| Symptom | Likely cause | Fix |
|---|---|---|
| No SMS, no voice | Number not live / barred | Finish port; network support |
| SMS OK domestically, voice OTP fails | International inbound blocked | Adjust host/network; retry SMS |
| Code never arrives on virtual line | SMS log lag / sender filtered | Refresh gosimless log; ask host about short codes |
| “Too many guesses” | Typed wrong codes | Wait out lockout; do not keep guessing |
| Number already registered | Old WhatsApp still owns it | Delete device registration or migrate officially |
| Works then suddenly asks again | New phone / cleared data / SIM swap | Re-verify with inbox ready |
Frequently Asked Questions
Should I verify WhatsApp the day I pay Create Numbers?
No — wait until the number is live on your SIM or virtual host after PAC fulfilment (2–4 weeks typical). Early attempts fail and can burn timers. Follow Get connected first.
Should I use SMS or “Call me” first?
Try SMS first on a UK mobile; switch to Call me when the SMS timer expires without a code. Voice is essential for some landline/virtual setups. Disable call blocking beforehand.
Should I put the Create Numbers mobile on personal WhatsApp first “just to test”?
Avoid that if the end state is WhatsApp Business or API — you may force a delete/migration later. Test SMS with a normal text from another phone instead. Register straight into the intended product.
Should agencies verify client numbers on staff personal phones?
Only with a written hand-back plan. Prefer business-owned handsets, gosimless dashboards or the API. Staff leavers otherwise take the WhatsApp session with them.
Should I enable WhatsApp two-step authentication immediately?
Yes — add the PIN as soon as registration completes so a stolen SIM swap is harder to convert into a stolen WhatsApp. Store the PIN in a company password manager. Pair with network-side SIM security (SIM swap).
Should I expect a green tick from phone verification alone?
No — the tick relates to Meta Business verification / official business presence, not the 6-digit phone OTP. Complete both tracks if brand trust matters. Phone OTP only proves number control.
Should international founders use a UK Create Numbers mobile for UK customers?
Yes, if UK customers expect a local 07 and you can always receive the OTP (locally or via gosimless SMS-to-email while abroad). Confirm gosimless overseas use in their FAQs. Keep hosting subscribed while the number is public.
Should I re-verify after every SIM swap?
Be ready to — WhatsApp may trust the device for a while or challenge you immediately. Have the new SIM’s SMS ready before you swap. Never swap mid-campaign without a backup admin.
Should I use the same number on WhatsApp and SMS marketing platforms?
You can, but coordinate opt-in and sender reputation so one channel’s complaints do not poison the other. Keep transactional OTPs separate from promo traffic where possible. Document the architecture for your DPO.
Should I contact Create Numbers or Meta if the code never arrives?
Contact whoever controls SMS delivery first (network or gosimless), then Create Numbers if the number never went live, and Meta/WhatsApp only for in-app account errors. Carry PAC, order and SMS-log screenshots. Most “WhatsApp bugs” are still undelivered OTP SMS.