Home/Changelog/Broadcasts v3: pacing, daily-limit budget, auto-park, A/B tests and send-time optimisation

Release

Broadcasts v3: pacing, daily-limit budget, auto-park, A/B tests and send-time optimisation

The sending engine moved to a dedicated worker with a per-number pacer, a portfolio-level daily budget, automatic parking with a stated reason, an explicit recipient stat

Updated 19 Aug 2026 · 1 min read

Broadcast campaigns in VGraple CRM showing sent, delivered, read, replied, failed and suppressed counts for each campaign

The sending engine moved to a dedicated worker with a per-number pacer, a portfolio-level daily budget, automatic parking with a stated reason, an explicit recipient state machine, A/B testing with a statistical winner and send-time optimisation.

What changed

  • Suppressed recipients (opted out, blocked, capped, unreachable) are never attempted, billed or retried.
  • Campaigns survive deploys and resume from the pending rows.
  • Retarget cohorts by read, replied, clicked or ignored; link clicks are tracked per recipient.
  • Marketing sends route through Meta's Marketing Messages API when the account is onboarded.

What to do

Nothing is required. The change applies to every workspace. If you notice a behaviour that differs from a help article, the article date tells you whether it predates this release; write to [email protected] and we will correct it.

Composing a WhatsApp broadcast in VGraple CRM: template, audience, schedule, quiet hours and estimated cost before sending

Run your WhatsApp on VGraple CRM

Free forever plan, official Meta WhatsApp Business API, set up in 15 minutes. No card needed.