Each patient gets messages from the same clinic number. Your system sends confirmations and return reminders, and the patient replies on WhatsApp.
From --/number/month + one-time activation fee.Prepaid.No fixed monthly fee
Why ZapZap for clinics and aesthetics
The deterministic pool keeps, by default, the same contact for each patient. A familiar number makes people more confident to reply.
Your scheduling system sends the confirmation through the API or a webhook the day before. The patient replies Yes or asks to reschedule on WhatsApp.
A patient messages at 10 p.m. asking for a time. The AI replies with the slots your system provides and logs the request for the front desk.
The problem
Illustrative example
A booked slot becomes a no-show, the chair sits empty and nobody calls to confirm again.
Illustrative example
The receptionist loses 2 hours a day sending manual confirmations from her personal WhatsApp. When she is out, nobody knows the password.
Illustrative example
A patient gets a message from a new number, gets suspicious and does not confirm. On the day, they do not show. You only find out when the time slot has passed.
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.
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.
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.
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.
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" }
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...
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 message. For a clinic with many confirmations a month, the cost of the number does not change with the volume of reminders.
Calculator
Adjust the numbers to your scenario. Results update in real time.
Possible recovery per month
R$ 10,000
What you lose today
R$ 20,000
If automatic confirmation recovered half of the no-shows (an assumption of the calculation), that would be R$10,000 more per month.
Create accountAutomatic confirmation from your system, and a front desk focused on in-person care.
Prepaid · No contract · Balance never expires