WhatsApp broadcast console for planning and launching campaigns

Build me a WhatsApp broadcast console where my marketing team plans, launches and compares campaigns without living in the Kapso dashboard. It uses Kapso for everything broadcast related and Google Sheets as the source of the audience list.

The home view is a list of every broadcast, most recent first, from the Kapso List Broadcasts operation. Each row shows the campaign name, the template it used, when it went out, and sent, delivered, read and failed counts side by side so the team can compare templates head to head. Show delivered and read as both raw counts and a percentage of sent, and make a high failed count visually obvious. Anything currently sending should show live progress in its row.

Clicking a broadcast opens a detail view built from Get Broadcast for the campaign level numbers and List Recipients for recipient level delivery status. Show a table of recipients with phone number, their merge field values, current status and any error. Above that table, group the failures by reason with a count for each, so the team can tell at a glance whether they hit bad numbers, an opt out, or a template problem. Sending is asynchronous, so poll Get Broadcast while a campaign is in a sending state and update the counts in place, then stop polling once it finishes.

A launcher page walks through a new send. First pick a template from List Message Templates, showing name, language and approval status, and only allow approved templates to be selected. Then point at the audience and read it with the Google Sheets Get Values operation, letting the user choose the spreadsheet, tab and range, and map sheet columns to the phone number and to each template variable. Render a live preview of the message exactly as it will arrive for the first few rows so they can see the merge fields filled in and catch a bad mapping before anything sends.

Launching runs the Kapso sequence in order: Create Broadcast to make the campaign in draft, Add Recipients to load the audience, then Schedule Broadcast for a future time or Send Broadcast to start immediately. Add Recipients accepts at most 1000 recipients per call, so batch larger Sheet audiences into successive calls and show upload progress. Broadcasts stay in draft until the send or schedule call, so the user can build one up and confirm before committing.

Every in flight campaign needs a stop button that is always one click away, on the detail view and on the home view row. Stopping calls Update Broadcast Status with status set to stopped, which starts no new sends and leaves pending recipients pending. For a campaign that has not gone out yet, offer Cancel Scheduled Broadcast to pull it back to draft. Confirm before either action, then show clearly what state the campaign ended in.

Add a review before send button, on the launcher and on any draft or scheduled campaign, that kicks off a background agent. The agent reads how similar past broadcasts performed using List Broadcasts, Get Broadcast and List Recipients, comparing the chosen template against past sends with similar content or audience. It checks the chosen template and the Sheet audience for problems such as malformed or duplicate numbers, missing merge values, or a template that has underperformed before. It then drafts one or two stronger copy variants and submits them with Create or Update Message Template so WhatsApp approval can start early, since templates must be approved before they can be used. Finally it writes a go or no go note back into the app with its reasoning, the past campaigns it compared against, and the variants it drafted.

Persist the review notes in the app so each one shows on the campaign it belongs to and stays readable later, with the time it ran and its outcome. The team can launch without a review, but when a review came back no go, surface that warning next to the send button. The Kapso broadcasts API is marked alpha, so handle its errors gracefully and show a clear message rather than failing silently.