Export sales and overseas support teams
A local residential IP in each number's own country: sign-ins hold still while many numbers stay online, each on its own IP.
Native ISP IPs come from local home-broadband carriers, leased monthly with the same address on renewal; phones and computers both connect.
Buyers in Brazil, Mexico, India, the Gulf and southern Europe ask for quotes, order and chase deliveries straight on WhatsApp. Give each market a local number and sign it in through a home-broadband exit in that same country, and it chats like a local business.
Brazil
Mexico
Argentina
India
Indonesia
Malaysia
Turkey
United Arab Emirates
South Africa
Germany
Spain
ItalyBrazil Portuguese enquiries pour in; reps' numbers live on Brazilian home-broadband exits Brazil residential IPs India English and Hindi buyers side by side; pre-sales and after-sales numbers get separate exits India residential IPs United Arab Emirates Gulf wholesale and distribution buyers; Arabic and English numbers each get an IP United Arab Emirates residential IPs Germany European B2B follow-ups, with a German exit serving buyers across neighbouring markets Germany residential IPs From the numbers reps close deals on, to automated notices from the backend, to fresh enquiries from ads: every link in the chain gets the exit it needs.
Each rep's WhatsApp Business accounts bind to a native ISP IP in the number's country: a Brazilian number, a Brazilian exit. Trips, new networks or a new laptop leave the sign-in place as it was, and client chats stay intact.
Native ISP IPRun several WhatsApp Web sessions on one computer, each browser profile holding one number on one exit. Numbers stay independent, and the next shift simply opens the same profile to take over.
Native · broadcastOrder confirmations, shipping notices and after-sales follow-ups leave your backend as template messages. Pin outbound requests to one datacenter IP, and provider allowlists and firewall rules only ever list that address.
Datacenter IPOpen each ad from the country it targets: are the prefilled message, greeting and auto-reply in the local language, and do enquiries land on the right number? One short-term IP per round.
Short-term IPDeal-closing numbers need steady sign-ins, big teams also watch cost, the API needs one known source and ad checks need country coverage.
| Job | IP type | When to use it | Notes |
|---|---|---|---|
| Reps closing deals daily | Native ISP IPFrom $5/IP/month | A number serves one country's buyers for good and is answered every day. | Pair each number with one static residential IP on the register; renewals keep the address. |
| Support desks with many numbers | Broadcast IP$4/IP/month | A support or distribution desk runs lots of numbers and wants one exit each at a lower cost. | Broadcast IPs also stay fixed, leased monthly, handy for kitting out many numbers. |
| Cloud API notices | Datacenter IP$3/IP/month | The backend calls the API all day to send notices, images and invoices. | Outbound requests only; webhooks still reach your server directly and tokens stay on it. |
| Ad entry checks | Static residential · Short-termFrom $0.17/IP | After a new ad, greeting or auto-reply goes live. | 1–24 hour leases, one per country; unused packs carry over to the next round. |
| Checking out new enquiries | Dynamic residential · TrafficFrom $0.8/GB | Before following up, view the buyer's website, public business profile and local prices from their country. | Billed per GB, one sticky session per country, packs that don't expire. |
Many a WhatsApp ban or repeated re-verification starts with the sign-in setup: a dozen numbers behind one office IP, or one number hopping between office Wi-Fi, home and mobile data in a single day.
| Aspect | Office network + personal phones | NexIP, one exit per number |
|---|---|---|
| Sign-in place | Moves with people and networks, several times a day | One IP in the number's own country |
| Several numbers | A string of numbers behind one exit | Separate exits, so one number's trouble stays its own |
| Shift handover | The next agent rescans on another computer | Open the same browser profile, same exit |
| API source | Cloud scaling changes the outbound address | A fixed datacenter IP, allow-listed once |
A WhatsApp Business proxy setup: native ISP IPs for deal numbers, broadcast IPs for big desks, a datacenter IP for the API, and checks or research bought per round or per GB; checkout shows the final price.
Reps' deal numbers: a home-broadband exit in each number's country, one each, renewed monthly.
Desks with many numbers: long-term fixed exits that cost less in bulk.
Cloud API backends: a dedicated datacenter IP, one address for every allowlist.
Ad entry checks: one IP for 1–24 hours, a round per target country.
Enquiry research: per GB, unlimited concurrency, packs that don't expire.
HTTP, HTTPS and SOCKS5 all work: browser profiles for web sessions, the router or a SOCKS5 proxy client for phones, environment variables for API servers.
Create a browser profile per number pointed at its exit, authenticate by IP allowlist, and shifts just open it with no passwords passed around.
chrome --user-data-dir=profiles/br-rep-a \
--proxy-server=http://GATEWAY:PORTSet proxy variables on the servers that send notices and invoices, and every outbound API call leaves from one datacenter IP.
export HTTPS_PROXY=http://USER:PASS@GATEWAY:PORT
node order-notify.jsConfirm the exit IP and its country with one command, match it to the number's country code, then log it.
curl -x socks5h://USER:PASS@GATEWAY:PORT https://example.com/Deal numbers do well on native ISP IPs (From $5/IP/month): one per number, exiting in the number's own country, unchanged for the lease. Desks with many numbers can use broadcast IPs, and Cloud API servers a datacenter IP.
The sign-in setup is a common factor: numbers sharing one IP, a sign-in place that keeps moving, or an exit that doesn't match the number's country all invite re-verification. A fixed local home-broadband IP per number, plus a normal chat rhythm, makes numbers far steadier.
One per number. Ten numbers get ten fixed exits, and the agents who answer a number share its exit; with numbers and IPs paired one to one, handovers and troubleshooting stay simple.
Route that phone through the number's exit on your router, or install a SOCKS5-capable proxy client on the phone, so WhatsApp and the other apps use that IP. The Wi-Fi HTTP proxy field alone isn't enough, since apps may ignore it. Point the same number's web session at the same exit.
Outbound addresses change when cloud servers scale or move. Routing every outbound request through one datacenter IP (From $3/IP/month) keeps provider integrations, firewall rules and logs on a single source.
Lease a short-term IP per target country (From $0.17/IP), find the ad in Meta's Ad Library, open it from that exit and tap into the chat, check the language of the prefilled message, greeting and auto-reply, and keep screenshots. City-level exits are subject to availability.
Native ISP, broadcast and datacenter IPs are leased per IP per month (From $3/IP/month); short-term IPs come in packs (From $0.17/IP); rotating residential IPs bill per GB (From $0.8/GB) in packs that don't expire.
Still have a question?