Short answer: Almost any +91 number you own works, provided it can receive an international SMS or voice call and is not currently active on WhatsApp. A mobile number is the safe choice. Landlines and toll-free lines are allowed but need the registration call routed to a person. Your number does not determine what you pay.
What Meta actually requires
Meta’s business phone numbers documentation, updated 21 May 2026 and read on 4 October 2026, gives four eligibility requirements. The number must be owned by you, have a country and area code — “short codes are not supported” — be able to receive voice calls or SMS, and have scaled capabilities.
That is the whole list. No requirement that it be a mobile, newly purchased, or registered to the same legal entity as the WhatsApp Business Account. Registration works by sending a one-time code to the number, and everything else follows: if a code can reach a human there, the number can probably be registered.
One consequence catches people out. A registered number “can still be used for everyday purposes, such as calling and text messages, but cannot be used with WhatsApp Messenger”. The phone keeps working. WhatsApp on that phone does not.
Which kinds of +91 number actually work
Meta publishes a table rating each number type for SMS and voice one-time passwords — the most useful thing on the page, and almost nobody quotes it.
| Number type | SMS code | Voice code | Practical verdict for India |
|---|---|---|---|
| Mobile | Standard | Standard | Recommended by Meta. Use this unless you have a reason not to |
| Fixed line (landline) | Not recommended | Standard | Works via voice. Disable call forwarding and IVR first |
| Freephone (toll-free) | Not recommended | Standard | Works via voice; confirm international reception with your provider |
| VoIP | Not recommended | Standard | Allowed. Confirm your provider passes international calls through |
| Personal number | Not recommended | Not recommended | Avoid |
| Inbound only | Not recommended | Standard | Works via voice |
| Pager | Not supported | Not supported | No |
| M2M / IoT | Not recommended | Not recommended | Avoid |
“Not recommended” is not “not allowed” — it is Meta’s estimate of whether the code will arrive. Every non-mobile type depends on the line accepting an international call and putting a person on it.
That is where toll-free numbers fail. Meta is blunt: “A WhatsApp registration call cannot navigate an IVR.” Numbers behind an IVR can be registered, but you must allow-list the numbers the registration call comes from and redirect it to an employee or a mailbox. Those that cannot receive the call “are not supported”.
A 140 or 1600 series number will not work either, for structural reasons rather than a WhatsApp rule. TRAI’s direction of 17 December 2025 required IRDAI-regulated entities to adopt the 1600 series “for making service and transactional calls to the consumers” by 15 February 2026, following RBI, SEBI and PFRDA-regulated entities. These are outbound resources; a registration code arrives inbound. Keep them for the channel they were allocated for — see our 140 and 1600 series guide.
The number you already use on WhatsApp
“Numbers already in use with WhatsApp cannot be registered unless they are deleted first.” That means deleting the WhatsApp account on that number inside the app, not merely uninstalling it. A number banned on WhatsApp must be unbanned through the appeal process first.
This is a one-way door. If your sales team’s shared handset is the number customers already message, you lose that inbox when you migrate it. Export the chat history first, and tell the team before you do it.
Two numbers do not double your capacity
This is the most expensive misunderstanding on the list.
Messaging limits are “the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period”. Crucially, they are “calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio”. Meta spells out the consequence: “it’s possible for one number to consume all of the portfolio’s messaging capability within a given period.”
Buying a second +91 number for more sending headroom therefore does not work. It buys a second sender identity drawing on the same pool.
A new portfolio starts at 250, rising to 2,000 by completing a scaling path — verifying your business, having your partner verify it, or delivering 2,000 messages to unique recipients over a 30-day window using high-quality templates. After that it rises automatically to 10,000, then 100,000, then unlimited, provided you are “sending high-quality messages across all of your business phone numbers and templates” and “in the last 7 days, your business has utilized at least half of your current messaging limit”. Each increase lands “within 6 hours”.
A separate cap governs how many numbers you may register at all: two on a new portfolio, rising automatically to 20 once the business is verified or the portfolio reaches a messaging limit of 2,000.
Worked example: a new number before a campaign
A Hyderabad retailer has 60,000 opted-in contacts and registers a fresh +91 number on a brand-new portfolio four weeks before a festival push. At the opening limit of 250 unique recipients per 24 hours, reaching all 60,000 takes 240 days. Not four weeks — eight months.
Taking the slowest route up, the ladder has a floor of about 29 days: eight days to deliver the 2,000 messages that complete a scaling path at 250 a day, then at least seven at each of the 2,000, 10,000 and 100,000 steps. Verifying the business skips straight to 2,000 and brings that floor to roughly 21 days — worth about eight days, and free.
A rupee figure makes it concrete. Interakt‘s published Growth-plan marketing rate for Indian destination numbers was ₹0.958 per message on 4 October 2026, taxes extra. The full 60,000-contact send costs ₹57,480 before tax at that rate — but at the 250 tier you cannot spend more than ₹239.50 of it in a day, and at 2,000 no more than ₹1,916. The budget is not the binding constraint. The ladder is. Our pricing guide covers the per-message layer.
Your number does not set your price
Two assumptions about a +91 number are wrong.
It does not determine the rate. Meta’s pricing documentation states that “charges for messages are based on the country calling code of the recipient WhatsApp phone number.” A +91 number messaging a UK customer is charged at the UK rate; a Dubai-registered business messaging Indian customers pays Indian rates.
It does not determine the billing currency either — that follows the Sold-To country. Meta states that eligible customers “must ensure all WABAs in their business portfolio are migrated to INR by December 31, 2026 to avoid disruptions, since as of January 1, 2027 Meta will no longer deliver the messages of non-INR WABAs of eligible customers.” That deadline is under three months away. If you are not certain your WABA is on INR billing, check this week.
Does DLT registration apply to your WhatsApp number?
The TCCCPR framework and WhatsApp run on different plumbing. TRAI’s 2018 regulations define commercial communication as “any voice call or message using telecommunication services” and telecom resources as “any telegraph used to send voice call or messages”, with obligations landing on access providers — the licensed basic, cellular, unified access and virtual network operators. A WhatsApp template is delivered by Meta over the internet, not by that network.
We found no TRAI instrument today either extending DLT registration to WhatsApp or expressly exempting it. The honest position: DLT plainly governs your SMS and voice traffic, and nothing published establishes a DLT obligation for WhatsApp. That is a reading of the regulations, not legal advice. Consent is separate — the DPDP Act applies however you collected the contact.
The +91 prefix trap
Cheap to fix, expensive to miss. If you omit the plus sign and country code when sending, Meta prepends your own number’s country calling code to the recipient. For an Indian sender, Meta’s documentation shows (631) 555-1234 being delivered to +916315551234 — a real Indian number belonging to someone else.
Normalise every number to E.164 with the leading plus before it reaches the send queue. This is the one that can send a customer’s statement to a stranger.
FAQ
Can I use my personal mobile number for the WhatsApp API?
Technically yes, if you delete its WhatsApp account first. Practically, don’t — it becomes a business asset you can no longer use on WhatsApp personally.
How many numbers can I register?
Two on a new business portfolio, rising automatically to 20 once your business is verified or your portfolio reaches a messaging limit of 2,000.
Can I get my number back off the platform?
Not immediately, and not through the API. Only portfolio admins can delete a number, in WhatsApp Manager, and a number “can’t be deleted if they have been used to send paid messages within the last 30 days”.
Do I need a GST certificate or a registered company?
Meta’s eligibility requirements for the number say nothing about either. Business verification is a separate process with its own document requirements, and it unlocks the higher number cap and the first messaging-limit step.
Does a landline need anything special?
It must accept international calls, and you should disable call forwarding and IVR features before requesting the code.
Can I move the number to another provider later?
Yes. Display name, quality rating, messaging limits, Official Business Account status and “any High quality message templates previously approved” carry across; low-quality, rejected and pending ones do not. Migrations stall on prerequisites: approved business verification, an approved display name with no pending change request, and two-step verification switched off — which only WhatsApp Manager can do, not the API.
Verification note
Every figure and rule above was checked against a live primary source on 4 October 2026. Meta’s documentation changes without notice — re-check before acting on it.
What we could not verify, and therefore left out: Meta’s India INR list rate card. That table is populated by an authenticated endpoint and rendered empty on 4 October 2026, as on previous attempts. We have not reused a rate from an earlier post, so no Meta per-message rupee figure appears above. The only rupee rate quoted is Interakt’s, named as such.
Sources
All read 4 October 2026.
- Meta, Business phone numbers (updated 21 May 2026) — eligibility, number types, IVR registration, number cap, deletion, prefixing.
- Meta, Messaging Limits (updated 21 May 2026) — portfolio-level limits, the tier ladder, scaling criteria.
- Meta, Pricing on the WhatsApp Business Platform — recipient-country-code charging; the INR deadline.
- Meta, Migrating phone numbers among solution partners — migration prerequisites.
- TRAI, TCCCPR 2018 — definitions.
- PIB press release, 17 December 2025 — TRAI direction on 1600-series adoption.
- interakt.shop/pricing — per-message rates for Indian destination numbers.
XReach51 sells WhatsApp, SMS, voice and IVR messaging in India, so we have a commercial interest here. Everything above is sourced to Meta’s and TRAI’s own documents so you can check it yourself.