Same store, same number by default. A customer who asked yesterday recognizes who is answering today. Recover abandoned carts on the channel customers actually open.
From --/number/month + one-time activation fee.Prepaid.No fixed monthly fee
Why ZapZap for e-commerce
Automatic send after abandonment, with the customer's and product's name filled in by variable. Random delay between sends, so the pattern does not repeat.
Pre-sale, confirmation, tracking, after-sales: all on the store's number. The customer trusts it and support has the history.
Is size M in stock? How much is shipping to 90000-000? The AI answers. When the case is complex, it hands off to a human.
The problem
Illustrative example
The customer left the cart in the middle of payment. The recovery email landed in the promotions folder and the sale never came back.
Illustrative example
A customer confirmed the order on WhatsApp. The tracking update comes from a different number. They thought it was a scam and asked for a refund.
Illustrative example
Support is scattered across platforms: the agent's personal WhatsApp, a tool bought the other day, another one nobody understands. Fragmented history, and the customer repeats everything.
My WhatsApps
3 instances . 2 online
Sales Support
+55 11 9 8765-4321
Marketing
+55 21 9 9876-5432
Orders Bot
+55 11 9 1234-5678
Messages today
1,847
Connected
2/3
Balance
R$ 78.40
How it works
Every part built to last at scale.
A deterministic hash per contact. Each customer reaches the same instance every time, even with 10 numbers in the pool. The conversation picks up where it left off.
Import the CSV, pick the pool. Variable delay between sends and per-contact variables. Send only to people who agreed to receive, and honor opt-out requests.
5511988776655
Hi, I'd like to know about...
Sales Support
Number connected successfully
5521977665544
Your order #1847 has...
Every instance already has AI available. Turn it on in seconds: it keeps context between messages, transcribes audio and reads images. When it does not know, it hands off to a human.
150+ REST endpoints. Secure proxy: your code only sees the API Key and Secret, and the instance token stays on the backend. Works with n8n, Zapier or any HTTP tool.
// Send a text message
const response = await fetch(
`https://api.zapzapapi.com/v1/${id}/send/text`,
{
method: 'POST',
headers: { 'x-api-key': apiKey },
body: JSON.stringify({
phone: '5511999999999',
message: 'Hi! Your order has been approved'
})
}
);
// Response
{ "status": "sent", "id": "msg_abc123" }
The monitor checks your instances every minute. If one drops, you get a WhatsApp message with a link to reconnect. No need to open the dashboard.
Number disconnected
Support SP went offline. Reconnect now.
Low balance
You have R$ 15.00 left. Top up so nothing pauses.
Daily report
1,847 msgs sent. 2 instances online. 3 campaigns active.
Your numbers exchange automatic messages with other businesses' numbers in the pool, at varying intervals, to build a usage history before going live. It lowers the risk, with no guarantee that the number won't be restricted.
Highlights
Community warm-up
On by default in every instance, with rest hours per number.
Built-in conversational AI
Automatic support set up in the same dashboard as your instances.
Per-instance pricing
Prepaid balance, no lock-in contract.
Protected access
The provider's master token stays on the server only and never reaches your browser.
ZapZap charges per instance, not per conversation window. For an e-commerce store that talks a lot with customers, the cost of the number stays the same, and sending should follow good practices.
Calculator
Adjust the numbers to your scenario. Results update in real time.
Estimated extra monthly revenue
R$ 33,600
Recovering 8% of abandoned carts through WhatsApp brings in R$33,600 more per month.
Create accountAutomatic recovery, reliable tracking, unified support.
Prepaid · No contract · Balance never expires