Use cases

WhatsApp API use cases

What product, marketing and support teams do with the ZapZap API, and which feature solves each case.

Transactional notifications

The problem

Order shipped, appointment booked, invoice due: customers want the information on the channel they actually open.

How ZapZap solves it

Your system calls the send text endpoint when the event happens, or fires it from an n8n, Make or Zapier automation. Reply events come back to your webhook.

See also

AI support that qualifies and escalates

The problem

Repeated questions eat up the team, and leads go cold while they wait for an answer.

How ZapZap solves it

Per-instance AI answers, qualifies and hands over to a person when needed. You set the behavior in the dashboard.

See also

Humanized campaigns

The problem

Burst sending looks like spam and raises the risk of a ban.

How ZapZap solves it

Marketer schedules batch campaigns with humanized intervals, and warm-up and anti-ban features lower the risk without eliminating it. Use only lists of people who agreed to be contacted.

See also

Group automation

The problem

Community and sales groups get out of hand: spam, unwanted links and leads that pile into a single group.

How ZapZap solves it

Group Doorman spreads leads across groups in rotation, Group Guardian moderates, and Group Secretary summarizes with AI what happened.

See also

Team inbox

The problem

Several agents need to answer from the same number, with a shared history.

How ZapZap solves it

Connect the instance to Chatwoot and distribute conversations among agents and teams.

See also

Lead capture and qualification

The problem

A cold form converts poorly, and the contact reaches sales without context.

How ZapZap solves it

Sales Funnel qualifies the lead in sequential screens and onboards by tag. Integrate with Typebot, RD Station or Google Sheets.

See also

WhatsApp inside your product

The problem

Agencies and SaaS companies need one number per customer without running everything by hand.

How ZapZap solves it

Create and manage instances through the API, linking each one to your system with the metadata field. Billing follows the prepaid model per active number.

See also

Frequently asked questions

Can I use the same number for several cases?

Yes. One instance answers, sends and receives webhooks at the same time. To separate operations, use different numbers: each active number costs R$15 per month.

Is there a per-message charge?

No. Billing is per active number per month, prepaid.

How do I start?

Follow the quickstart guide: create the instance, scan the QR code and send your first message.

Pick your case and start

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.