Meta-compliant messaging at scale

WhatsApp is not an open channel. Meta applies per-second rate limits, daily conversation caps, opt-in requirements, and a quality rating that degrades a number until it is throttled or blocked outright. Template sends are checked against approval status and variable structure before delivery.

A send path that approximates these rules rather than implementing them will work in testing and fail in production, and the failure mode is not a dropped message. It is a business account whose rating falls far enough that the number stops reaching customers at all.

The broadcast engine is built around those constraints: rate limiting matched to Meta’s published limits, batching, scheduled sends, and retry logic tuned against observed failures rather than assumed ones.

It broadcasts 100,000 template messages in under thirty minutes at maximum viable delivery, and the campaign dashboard reports sent, delivered, read and failed per message, so a client can see where a campaign lost people instead of guessing.

Contact import takes real spreadsheets with arbitrary columns and custom fields, with retry and scheduling behind it, handling 500,000 contacts in under ten minutes.

Meta webhook payloads are captured in full and reconciled against each portfolio’s ad campaigns, which is what makes Click-to-WhatsApp attribution possible: the platform can say which advertisement a given customer came from. Conversation labels sync additively rather than overwriting, and agents filter by campaign, template, agent or label.

Templates are created and previewed inside the platform, with dynamic variables resolved per client. Deployment runs on separated environments with Docker images and volumes under version control.