Kendali Blast

WA BATCH SENDER
not connected

Quick add contact

Press Enter to submit — focus automatically jumps back to the name field so you can add contacts back-to-back.

NameWhatsApp NumberTagBatch statusAdded

Auto-split unbatched contacts

Automatically splits all contacts not yet in any batch into new batches.

00:00
Checking cooldown status... Connecting to Supabase.

Message content

{name} is automatically replaced with each contact's name when sending. Draft is saved automatically.

If filled in, each contact gets a random version — reducing the "identical mass message" pattern that signals spam.

Click to upload main image
Click to upload follow-up image

Sent as a separate message a few seconds after the main message (WhatsApp only allows 1 media per message).

Anti-block safeguards

A WA number can get limited/banned if the pattern looks like a bot, or if too many people report/block it. These settings help reduce that risk.

-

Batches ready to send

Saved campaigns

Delivery report

TimeNameWhatsApp NumberBatchSend statusWA status

1. Create tables in Supabase

Run this SQL once in the Supabase SQL Editor.

Schema

      
    

2. Storage bucket for images

Create a public bucket named wa-blast-media in the Supabase Storage menu, then set public policies for SELECT (read) and INSERT for the anon role.

3. Delivery status webhook (optional)

Deploy the following Edge Function so that Fonnte's "delivered / read / failed" status automatically updates the reports table. This file is provided separately: supabase-webhook-function.ts. After deploying, set the function's URL as the webhook URL in your Fonnte dashboard.


      
    

Connection status