WhatsApp Fallback Messaging

Fallback messaging keeps communication running when the primary WhatsApp delivery path fails, hits a limit, or needs a backup channel.

Fallback Scenarios

API Failures

  • WhatsApp or the omnichannel partner is degraded.
  • Rate limits are reached.
  • Credentials expired or the session is inactive.
  • The account is temporarily restricted.

Delivery Issues

  • The user's number is invalid or changed.
  • The user blocked the message.
  • A template is rejected.
  • The 24-hour conversation window has expired.

Business Rule Issues

  • Automation rules are misconfigured.
  • Agent or rotator mapping does not match.
  • Lead status does not satisfy the rule condition.

Fallback Strategy

Use a channel order that matches message priority:

  1. Primary WhatsApp for normal communication.
  2. WhatsApp retry with exponential backoff for temporary failures.
  3. Email or internal notification for non-urgent messages.
  4. Manual sales/support follow-up for high-value leads.

Message Priority

Critical Messages

  • Payment confirmations.
  • Onboarding instructions.
  • High-intent leads.
  • Support escalations.

Critical messages should trigger fallback faster and notify the internal team.

Standard Messages

  • Marketing broadcasts.
  • Non-urgent reminders.
  • General updates.

For standard messages, gradual retry is usually enough before fallback.

Technical Retry Example

async function sendWhatsAppMessage(message, retryCount = 0) {
  try {
    await whatsappApi.send(message)
  } catch (error) {
    if (retryCount < 3) {
      await delay(Math.pow(2, retryCount) * 1000)
      return sendWhatsAppMessage(message, retryCount + 1)
    }

    await sendFallbackNotification(message)
  }
}

Best Practices

  • Retry temporary errors before switching channels.
  • Keep an audit trail for every retry and fallback.
  • Avoid logging PII-heavy message bodies unless needed.
  • Separate fallback logic for sales leads, support tickets, and broadcast campaigns.
  • Respect user consent across every channel.

Monitoring

Track:

  • Retry volume per partner.
  • Fallback ratio per campaign or rule.
  • Template errors.
  • Average time until successful delivery.
  • High-value leads requiring manual follow-up.

Need More Help?

Our team is ready to help you maximize ad tracking and business attribution.

Wulan answers your questions and sends tutorial videos. Session scheduling is available through Wulan if you still need it.

© 2026 Konektor. All rights reserved.