When WhatsApp fails, we don’t.

WhatsApp’s edge cases, handled.

Automatic retries

Exponential backoff per error type. Rate limits, network blips, Meta hiccups — all retried until they succeed or fail meaningfully.

Per-error policy

Define what to do per failure code: retry, fall back to email, fall back to SMS, queue for human review, or fail loudly.

Multi-channel fallback

WhatsApp blocked? Number invalid? Auto-fall-back to email or SMS using the same template. Don’t lose the touchpoint.

Recovery inbox

Failures that need human eyes land in a dedicated inbox. Bulk-resolve. Bulk-retry. Bulk-acknowledge.

Failure analytics

Real-time dashboard of error rates by type, market, template, and time. Anomaly alerts before it gets bad.

Replay & rebroadcast

Any campaign or chunk can be replayed against just the failed contacts — never the successes. No double-sends.

Reliability tooling, not a "we’ll try our best" disclaimer.

WhatsApp Business API has 14 documented failure modes — Meta rate limits, expired templates, blocked numbers, opt-out collisions, and more. We handle each one explicitly with a configurable policy.

• Exponential backoff with jitter per failure code
• Rate-limit-aware send pacing
• Health monitor with proactive alerts

WhatsApp first. Anything that works second.

When WhatsApp says no, we’ll try the same message on SMS or email if you have those configured. Same template, same merge tags, same audit trail.

• One-click SMS provider connect (Twilio, MessageBird)
• Same template body across channels
• Per-recipient channel preference learning