Your last Ramadan blast may have been silently paused. Here's how to stop the next one.
Meta's Business Portfolio Pacing batches your WhatsApp campaigns and can pause mid-blast on quality signals you can't see in your BSP dashboard. Monitor watches Meta's quality signals in real time, predicts pace-pauses before they fire, auto-throttles your sends, and swaps to pre-approved fallback templates. Built for Ramadan, Eid, and National Day waves.
What's at stake
- A pacing-pause in the middle of a Ramadan iftar campaign is catastrophic and invisible. Your BSP dashboard shows messages queued; Meta has silently halted further releases. You find out the next morning when revenue numbers come in below model.
- MENA campaign volume is spiky. 4–10× your baseline during Ramadan, Eid, National Day, Black Friday. Exactly the spike profile that triggers pacing.
- BSP dashboards are post-hoc. They show you the quality drop after it happens. You need a predictor that fires 30–90 minutes before the pause.
- BSPs' incentives don't align with yours. BSPs are paid per message. An auto-throttle that reduces sends reduces their revenue. The throttling SaaS doesn't get built inside BSPs structurally.
What we do
A real-time monitoring SaaS:
- 1. Webhook ingestion. We listen to Meta's quality-rating, template-flagging, and account-update webhooks for every WhatsApp Business Account you operate. Latency under 5 seconds from Meta event to ingestion.
- 2. Pacing-risk scoring. Composite 0–100 score combining quality-rating transitions, template flagging velocity, current-tier-usage, and block-rate delta. Tuned against MENA campaign data.
- 3. Auto-throttle. When the pacing-risk score crosses 70, we reduce send-rate by a configurable factor through your BSP's send API (where supported) or your outbound dispatcher (where not).
- 4. Template rotation. When specific templates drive the signal, we swap to pre-approved fallback alternates configured during onboarding.
- 5. Alerting. WhatsApp + email alert to your on-call contact with current score, signals, action taken, and one-click override / escalation.
- 6. Dashboard. Live risk score, recent signals, throttle history, template swap history.
End-to-end latency from Meta event to throttle action: 8–15 seconds in production.
Pricing
| Tier | Price | What's included |
|---|---|---|
| Monitor SaaS | $99/month per WABA | Real-time webhook ingestion, pacing-risk scoring, alerting, dashboard. Auto-throttle and template rotation are configurable add-ons at no extra cost. 14-day free trial. |
| Enterprise | $499/month for 10+ numbers | Multi-WABA aggregation across BSPs, custom threshold tuning, priority alerting, quarterly campaign-pattern review. Auto-throttle enabled by default. |
Why us
- Predictive, not post-hoc. BSP dashboards show current state. We predict the next 30–90 minutes.
- Aligned incentives. We make money when your campaigns deliver. BSPs make money per message — opposite incentive structure.
- Multi-BSP aggregation. If you run redundancy across 360Dialog + Twilio + your direct Cloud API, you have three dashboards and no consolidated view. We consolidate.
- Tuned for MENA campaign patterns. Ramadan / Eid / National Day spike profiles drove our threshold defaults.
Frequently asked questions
How is this different from my BSP dashboard?
BSP dashboards show current state and recent history. We predict the next 30–90 minutes and act before Meta does. Thermometer vs thermostat.
Will it work across multiple BSPs?
Yes. Multi-WABA aggregation is the Enterprise tier's primary differentiator and exists because no single BSP can see the full picture.
Does auto-throttle hurt deliverability?
Auto-throttle reduces send-rate temporarily, in exchange for avoiding 30–60% delivery loss from a Meta-initiated pause. The arithmetic is unambiguously favourable. ~1–2% of messages get delayed 30–90 minutes during a protective action.
Can I keep auto-throttle off and just use monitoring?
Yes. Many customers run monitor-only for the first 30 days, validate the signal quality, then enable auto-throttle for the next high-volume campaign.
How do I know if Portfolio Pacing actually paused my last campaign?
Three diagnostics. We provide a free "did Portfolio Pacing hit you?" diagnostic on any campaign window from the last 90 days as part of trial onboarding.
What about template fallback approval?
Fallback templates are pre-approved with Meta during onboarding — typically 2–3 alternates per promotional template family. Standard 2–7 day Meta review.
Don't lose another Ramadan campaign to a silent pause.
Start the free 14-day trial. We'll show you which signals matter, and you'll see at least one quality-rating fluctuation in real time before the trial expires.
Start the free 14-day trialSix products. One studio.
Each product solves a specific Meta change. Pick the next one that applies to your stack.