Number Porting Between WhatsApp BSPs: What Breaks and What Survives

Last Tuesday at 7 pm, a boutique furniture retailer in Kochi got a fresh lead on WhatsApp: “Can you ship the teak set to my office tomorrow?” The buyer’s number had just been ported from the retailer’s old BSP to a new one. By the time the lead appeared in the new dashboard, the chat‑window was already showing “Message not delivered”. The lead slipped away, and the next day the retailer saw a ₹12,000 drop in expected revenue.

If you’ve ever watched a WhatsApp inbox go silent after a number‑port, you know the feeling is part‑panic, part‑realisation that something you built on a single BSP can crumble in minutes. For Indian SMBs that run on a razor‑thin margin—often ₹500‑₹3,000 of SaaS spend a month—number‑porting isn’t just a technical footnote; it’s a revenue lifeline.

Below we break down exactly what survives and what breaks when you move a phone number between WhatsApp Business Solution Providers (BSPs). We’ll pepper the discussion with real Indian numbers, concrete examples, and the hard‑won trade‑offs that matter to founders who are juggling GST filings, COD returns, and a team of two.

Why this matters for Indian SMBs

WhatsApp is the primary sales channel for 78 % of Indian SMBs, according to a 2023 KPMG survey. Email sits in the back‑office, while WhatsApp handles everything from first‑touch inquiries to post‑sale support. When a number moves from one BSP to another, three things happen simultaneously:

Customer perception shifts – a “Message not delivered” badge feels like a broken promise. In tier‑2 and tier‑3 cities, where word‑of‑mouth travels faster than any ad, a single missed reply can cost a dozen referrals.
Operational flow stalls – most Indian founders have wired their CRM, payment links, and GST invoicing to the BSP webhook. Pull the plug and the whole automation pipeline stalls.
Cost‑structure changes – the new BSP may charge ₹1,200 / month versus the old ₹800 / month, but the hidden cost of lost leads often dwarfs the subscription fee.

Consider the numbers: a typical D2C brand in Jaipur processes ≈ 150 WhatsApp leads per month. Their conversion rate sits at 12 %, with an average order value of ₹8,500. That’s ₹154,800 of monthly revenue. If a porting hiccup kills just 5 % of leads, you lose ≈ ₹7,740—more than the price difference between most BSP plans.

For founders who are already paying a CA ₹2,500 per GST filing and a logistics partner a 6 % COD surcharge, that extra loss is a tangible pain point. It’s why the decision to port a number deserves the same rigor you apply to choosing a payment gateway.

The problem (with real numbers)

1. Webhook disruption

When you switch BSPs, the old provider’s webhook stops sending events the moment the number is marked “inactive”. The new BSP only starts sending events after the number is verified—a process that can take 24‑48 hours under peak load. During that window:

Metric	Before port	During port	Impact
Avg. inbound WhatsApp messages	180 /mo	0‑30 /mo	83 % drop
Automated order confirmations (via webhook)	140 /mo	10‑20 /mo	85 % drop
GST‑ready invoice generation	120 /mo	5‑15 /mo	87 % drop

2. Template loss

WhatsApp requires pre‑approved message templates for outbound notifications (order updates, payment reminders). Templates are BSP‑specific; they do not migrate automatically. A typical SMB uses ≈ 12 templates (order confirmation, shipping, delivery, payment reminder, refund, etc.). Re‑approval can take 3‑5 business days, and each day the brand falls back to manual copy‑pasting, increasing human error by ≈ 30 %.

3. Contact‑list fragmentation

When a number is ported, the new BSP assigns a fresh WhatsApp Business ID. Existing contacts in the old BSP’s address book become “unknown” on the new side, breaking the “click‑to‑chat” links embedded on product pages and in email signatures. For a small retailer with ≈ 2,500 saved contacts, that translates to ≈ 1,200 broken links that need manual re‑sync.

4. Billing confusion

Most BSPs bill per active phone number plus a per‑message fee. If you keep the old number active for a grace period, you end up paying ₹800 + ₹1,200 = ₹2,000 / month for the same line. Add the per‑message cost (₹0.05 per inbound, ₹0.07 per outbound) and a 150‑message daily volume adds ₹525 extra each month.

5. Regulatory friction

The Indian Telecom Ministry requires a 30‑day notice before a number can be ported to a new BSP. Failure to submit the proper GST‑linked documentation can delay the port by up to 10 days, extending the disruption window.

All these points converge on a single reality: porting is not a plug‑and‑play switch. It’s a coordinated project that can shave ₹5,000‑₹15,000 off your monthly bottom line if not handled with a clear plan.

What works

1. Dual‑BSP “shadow” setup

Running both the old and new BSP in parallel for 48 hours eliminates the webhook blackout. The workflow looks like this:

Clone the webhook URL from the old BSP into the new one.
Duplicate all approved templates manually (or via the API) before the cut‑over.
Map the new WhatsApp Business ID to the existing contact list using a CSV import. Most BSPs accept a simple phone,whatsapp_id file.
Route inbound messages through a load balancer (e.g., a small Node.js proxy) that forwards to whichever BSP reports the number as “active”. This way, customers never see a “Message not delivered” error.

In practice, a boutique apparel brand in Hyderabad used this method and saw only a 2 % dip in lead conversion during the port, compared to the 15 % dip typical for a single‑BSP switch.

2. Pre‑port template audit

Because templates are BSP‑bound, the safest route is to audit every template 30 days before the planned port. Export the list via the old BSP’s API, then submit a bulk request to the new BSP. The WhatsApp Business API allows up to 10 templates per batch, cutting the approval time from 5 days to ≈ 24 hours when you bundle them.

3. Contact‑list sync script

A simple Python script that reads the old BSP’s contact export (contacts.csv) and writes a new CSV with the new Business ID can be run in under 10 minutes for up to 5,000 contacts. Here’s the gist:

import csv, requests

old = csv.DictReader(open('old_contacts.csv'))
new_rows = []

for row in old:
    resp = requests.get(f"https://newbsp.com/api/v1/whatsapp-id?phone={row['phone']}")
    new_rows.append({'phone': row['phone'], 'whatsapp_id': resp.json()['id']})

with open('new_contacts.csv', 'w') as f:
    writer = csv.DictWriter(f, fieldnames=['phone','whatsapp_id'])
    writer.writeheader()
    writer.writerows(new_rows)

Running this script saved a Delhi‑based cosmetics startup ≈ 3 hours of manual data entry.

4. GST‑linked invoicing continuity

Both the old and new BSP can push transaction data to a central invoicing micro‑service (e.g., a Node.js server that writes to a MySQL table). By keeping the invoicing layer agnostic of the BSP, you ensure GST calculations stay intact. The service simply consumes a standardised JSON payload:

{
  "order_id": "ORD12345",
  "amount": 8450,
  "gst_rate": 0.18,
  "payment_status": "PAID"
}

Because the payload format is BSP‑neutral, you avoid any GST‑related regression during the port.

5. Transparent customer communication

A short, Hindi‑language broadcast (using the new BSP’s template “Service Update”) sent 24 hours before the port reduces friction. Example text:

“नमस्ते! हम अपनी सेवा को बेहतर बनाने के लिए नंबर पोर्ट कर रहे हैं। अगले 48 घंटों में आपका संदेश तुरंत नहीं पहुँच सकता, पर हम जल्द ही वापस आ जाएंगे। धन्यवाद!”

Brands that sent this notice saw a 30 % lower complaint rate during the transition.

What doesn’t

1. Instant “one‑click” port

WhatsApp’s own documentation states that porting a phone number is a manual process that involves both the old and new BSP, plus the telecom operator. No provider currently offers a fully automated “click‑to‑port” button. Attempting to shortcut this step results in failed port requests and additional ₹500‑₹1,000 penalties from the carrier.

2. Template auto‑migration

Even if you copy the exact JSON of a template, the new BSP treats it as a fresh submission. The approval workflow is independent; you cannot bypass the 24‑hour review window. Brands that assumed templates would migrate automatically found themselves sending manual messages for up to 7 days, increasing human error and response latency.

3. Seamless contact‑ID continuity

WhatsApp Business IDs are globally unique and tied to the BSP’s internal account. When you move, the old ID becomes orphaned. There is no API to “re‑assign” the same ID to a new provider. The only workaround is the CSV import described earlier, which still requires a one‑time mapping.

4. Zero‑cost dual billing

Keeping both BSP accounts active during the transition is the safest route, but you will pay for both. There is no “grace‑period discount” offered by the major Indian BSPs (WATI, Gupshup, Karix). Attempting to negotiate a free overlap often ends in a ₹2,000‑₹3,000 monthly surcharge with no guarantee of continuation.

5. Automatic webhook failover

Most BSPs do not expose a fallback URL that triggers when the primary webhook stops responding. Without a custom proxy, inbound events simply disappear. Building a proxy adds ₹1,200‑₹2,000 in development cost (if you hire a freelancer), which many solo founders deem too pricey.

Cost / pricing in INR

Below is a realistic cost breakdown for a typical Indian SMB (₹2,500 / month SaaS budget) that decides to port a number from BSP A (₹800 / month) to BSP B (₹1,200 / month). All figures are based on publicly listed pricing as of March 2024 and include the hidden costs discussed earlier.

Item	Current (BSP A)	New (BSP B)	Additional cost during port
Base subscription	₹800	₹1,200	+₹400 (first month)
Inbound message fee (150 msgs/day)	₹0.05 /msg → ₹2,250 /mo	₹0.05 /msg → ₹2,250 /mo	No change
Outbound message fee	₹0.07 /msg → ₹3,150 /mo	₹0.07 /msg → ₹3,150 /mo	No change
Template re‑approval (12 templates)	–	₹1,200 (one‑time)	+₹1,200
Dual‑BSP overlap (30 days)	₹800	₹1,200	+₹2,000
Proxy development (optional)	–	–	₹1,500‑₹2,500 (one‑time)
Lost leads (5 % of 180 leads/mo, ₹8,500 AOV)	–	–	≈ ₹7,740
Total first‑month impact	₹6,200	₹9,500	≈ ₹7,740 (lost leads) + ₹4,400 (overlap+templates) = ₹12,140

How to keep the net increase under ₹2,000

Negotiate a 30‑day overlap discount – many BSPs will shave ₹500 off the second month if you commit to a 12‑month contract.
Batch template submission – reduces the one‑time ₹1,200 to ₹600 if you use a partner that offers bulk approval.
DIY proxy – a 4‑hour build using a free Heroku dyno costs ₹0 (apart from the time you spend). For a founder with Node.js skills, this eliminates the ₹1,500‑₹2,500 expense.
Stagger the port – move low‑traffic numbers first (e.g., regional sales reps) to test the workflow, then port the primary sales number during a historically quiet week (e.g., the week after Diwali).

By applying these levers, a typical SMB can limit the effective cost of porting to ₹3,500‑₹4,000 in the first month—a figure that fits comfortably within a ₹5,000‑₹7,000 SaaS budget.

Frequently asked questions

How long does the official number‑port process take in India?

The telecom operator mandates a 30‑day notice to the current BSP, followed by a 15‑day verification window. In practice, most providers complete the hand‑off in 7‑10 business days if all GST and KYC documents are in order.

Will my customers see a “Message not delivered” badge during the switch?

Yes, unless you run a dual‑BSP proxy. The badge appears as soon as the old BSP marks the number inactive. Sending a pre‑port broadcast in Hindi/Marathi can reduce the churn impact by up to 30 %.

Do I need to re‑verify my business with the new BSP?

Every BSP requires a fresh WhatsApp Business verification (company PAN, GSTIN, and address proof). The process typically takes 2‑3 days if you upload clear PDFs and the GST number matches the telecom subscriber record.

Can I keep my old number and just add a new one?

You can add a secondary number to the new BSP, but the primary WhatsApp Business ID stays with the original provider. To fully migrate, you must port the primary number; otherwise you’ll be juggling two inboxes—a headache for a 2‑person team.

What happens to my existing chatbot flows?

Chatbot scripts are BSP‑agnostic if you host them on your own server and call the WhatsApp Cloud API directly. However, many low‑code chatbot builders (e.g., BotStar, Landbot) store the flow inside the BSP’s dashboard. In those cases, you’ll need to export the flow and re‑import it into the new provider, which can take 1‑2 days of manual work.

Is there any way to avoid paying for both BSPs during the overlap?

The only workaround is a “soft port”: keep the old BSP active only for inbound webhook events while routing all outbound messages through the new BSP. This requires a custom proxy and adds ₹500‑₹800 in development time but saves the ₹2,000 monthly overlap fee.

By treating number‑porting as a project, not a checkbox, Indian SMB founders can keep their WhatsApp sales engine humming, protect a critical slice of revenue, and stay within a realistic SaaS spend. The key is to plan the overlap, audit every template, and script the contact sync—the three levers that turn a disruptive switch into a smooth upgrade.