Flow Builder
Build the cart recovery journey and the post-sale sequence with no code: event trigger, delay, message with checkout link, and branching based on the customer's reply.
For online stores
Your customer buys and then goes silent until delivery, while the abandoned cart goes cold and "where is my order?" floods support. WhatsApp solves all three, but doing it by hand doesn't scale.
Abandoned carts with no recovery: the customer reaches checkout, stalls on shipping or payment, and nobody pulls them back through the channel they open the most
The "where is my order?" anxiety: every purchase becomes a manual tracking ticket because customers don't trust email and prefer to ask on WhatsApp
Payments stalled with no warning: the PIX (Brazil's instant payment) expires or the boleto (bank slip) comes due and the sale dies because nobody reminded the customer in time
Repeat purchases that never happen: the sale is done, the customer disappears, and you have no post-sale flow to bring them back
Support drowning in repeated questions: delivery time, exchanges, sizes, status, all landing on the same number while the team can't keep up at peak hours
Sending offers from a personal number drops the chip in the middle of the campaign and you lose the entire channel
Your platform (Shopify, Nuvemshop, WooCommerce, custom checkout) fires order, payment and shipping events to the ZapZap REST API. Every status change becomes an automatic message on the customer's WhatsApp.
Order confirmed, payment approved, product shipped and tracking code go out automatically the moment the event happens. Customers follow everything without opening a ticket and support gets room to breathe.
A cart idle for X minutes or a PIX about to expire enters a recovery Flow with a reminder and a direct link to finish the purchase. No sale lost to forgetfulness.
The per-instance AI answers delivery time, exchanges and status instantly, qualifies who wants to buy again, and hands off to a human only what needs one. Marketer schedules the repurchase offer to the right customer.
What to use
The ZapZap modules that solve exactly the pain points of this scenario.
Build the cart recovery journey and the post-sale sequence with no code: event trigger, delay, message with checkout link, and branching based on the customer's reply.
Answers the repetitive e-commerce questions (delivery time, tracking, exchanges, sizes) around the clock and qualifies who is ready to buy again, taking volume off human support at peak.
Sends repurchase offers, reactivation coupons and collection launches on a schedule, segmenting past buyers without depending on a personal number.
Warms up the chip in a community and sends with automatic typing indicator, delays and a non-robotic pattern, which lowers the risk of a drop in the middle of a campaign or high-volume notifications.
Examples to get started. Personalize them with the customer's name and your business details.
Hi, {nome}! I saw you left {produto} in your cart and there's still time to get it. I set it aside for you, just finish checkout here: {link_checkout}
Good news, {nome}! Your order #{numero} has shipped and is on its way. Track it anytime here: {codigo_rastreio}. If you have any questions, just message me.
{nome}, your PIX payment for order #{numero} expires in 1 hour. If you still want to secure it, just pay through this link: {link_pagamento}. After that the stock goes back on sale for everyone.
Transactional notifications are well accepted, but offers and repurchase messages must respect opt-out. Offer an easy exit ("reply STOP to stop receiving offers") and handle customer data in line with the LGPD (Brazil's data protection law), using the contact only for the purpose they authorized at purchase.
Yes. ZapZap is a REST API with webhooks: any platform that fires order, payment and shipping events can trigger the messages. You connect your store's events and every status change becomes an automatic notification on the customer's WhatsApp.
No. The price is R$15 per active number per month, prepaid, with no per-message charge. You can send order confirmations, payment and tracking messages at whatever volume your store needs with no cost per send.
No, it is the unofficial API through managed instances. You don't go through template approval or the official API's categories: you write whatever message you want and send it. In exchange, the number is managed like a regular WhatsApp, so care with volume and warm-up is on you, and the platform helps with that.
The risk exists in any mass sending on WhatsApp. That is why ZapZap has chip warm-up in a community (Family) and anti-block with automatic typing indicator, delays and sending outside a robotic pattern, which lowers the risk. There is no guarantee it will never drop, so the recommendation is to warm up the number first and spread out the volume.
Yes. With Flow Builder you create the idle cart trigger (by time) and build the sequence: reminder, checkout link and branching on the customer's reply. You can do the same for a PIX or boleto about to expire, all with no code.
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.