Many instances in the same account
As many numbers as the operation needs, each isolated, with the same price per active number and no per-message fee. Remove a number and it stops counting.
For lead operations, sales teams and call centers
A lead operation lives on volume: many contacts, several numbers, one team answering. A single number concentrates all the risk and all the bottleneck, and a chip that drops midday takes the target down with it. Spread sending across your numbers, answer and qualify with AI, send each lead to the CRM by webhook and keep the cost at R$15 per active number per month, with no per-message fee. Create the account and connect the first numbers.
Updated on
All the volume on one number: when it is limited or drops, the whole operation stops with it
The team answers in different ways and the good lead goes cold in the queue of whoever is slowest
Leads arrive from several channels and ads and nobody knows which number should handle them
A new chip put to work the same day goes straight to a block and eats the replacement budget
A per-message or per-tier cost makes the price of each lead unpredictable exactly when the operation grows
Conversation data stays trapped on phones and never reaches the CRM, so the sales team works blind
Each number is its own instance in the same account, isolated from the others. You follow the status of all of them in one dashboard and pay R$15 per active number per month.
A new number joins the Family and goes through community warm-up, with automatic typing indicator, variable intervals and non-standard sending patterns, before it gets volume. Volume enters in steps, not all at once.
The Family spreads campaign sending across your numbers, and the per-instance AI with the Flow Builder answers, qualifies and hands the attendant only the lead who replied with what matters.
Webhooks send each reply to the CRM or spreadsheet in real time, identified by number. You measure which number, which list and which message generate replies.
What to use
The ZapZap modules that solve exactly the pain points of this scenario.
As many numbers as the operation needs, each isolated, with the same price per active number and no per-message fee. Remove a number and it stops counting.
Community warm-up and sending spread across the Family's numbers, with a varied pace, to reduce aggressive sending patterns. It lowers the risk, it does not remove it.
Schedules the campaign with times, delays and batches instead of firing everything at once. Pace is what separates a sustainable operation from a burned chip.
Lead reply straight into the CRM, number creation by API and collaborator access to one instance, so the team can work without sharing the owner's password.
Examples to get started. Personalize them with the customer's name and your business details.
Hi, [name]! This is [Company]. You asked for information about [product]. Can I explain quickly how it works? Just reply here.
[name], just checking in: does it still make sense for you to hear from a consultant today? If you prefer another time, tell me and I will adjust.
Thanks, [name]. I have passed your details to a consultant, who will contact you on this same number. If you do not want to receive messages anymore, reply STOP.
Lead operations handle personal data at volume: use only contacts with a legal basis and consent, offer a clear way out (for example, replying STOP) and honor it. ZapZap is an unofficial solution: WhatsApp can limit or block numbers, and the operation should plan for chip replacement and learn from every block.
The pricing page does not publish a limit. The price is R$15 per active number per month for any quantity, with no tiers. If the operation will go beyond a few dozen numbers, talk to support to agree on capacity before migrating.
No. Spreading sending reduces the risk concentrated in one number, but each number is still subject to WhatsApp's rules. What lowers risk is warm-up, a human pace, a consented list, messages that get replies and volume in steps. None of it removes the risk.
By webhook. Each instance sends received messages and status events to the URL you register, and the REST API lets you send the reply back. It works with n8n, Make, Zapier or your back end.
Yes. The management API creates, lists, queries and removes instances with key and secret, and you can store the campaign or team identifier in the metadata field. Before creating, GET /instances/cost shows the activation fee and the balance you need.
Collaborator access can be granted on an instance, with limited permissions, so the team works without the account owner's password.
We do not recommend it, and ZapZap's acceptable use policy requires consent from recipients. A cold list is the shortest path to reports and blocks, and no tool makes up for that.
Create your account, connect a number in minutes and test the API with warm-up and anti-ban. R$15 per active number/month, prepaid, no lock-in.