13-Day Heartbeat Safety Margin

How Meta's approximate 14-day inactivity threshold relates to Dualhook's 13-day safety timer.

Looking for the high-level overview first? Start with WhatsApp Coexistence and then return here for the implementation details.

Requirement

In coexistence setups, Meta may disconnect the partner connection after approximately 14 days of primary-device inactivity (PRIMARY_INACTIVITY). Dualhook's 13-day heartbeat is a conservative safety threshold designed to warn before Meta's approximate window, not a literal Meta requirement.

Why Dualhook Cannot Auto-Detect App Opens

Because message-path webhooks are routed directly to your endpoint via Webhook Override, and Dualhook does not retain conversation content, Dualhook cannot infer mobile app usage from message traffic. Heartbeat acknowledgment is intentionally manual.

Heartbeat States

Dualhook computes status from the last acknowledged app-open time:

  • OK — heartbeat is current
  • DUE_SOON — deadline approaching
  • OVERDUE — Dualhook's 13-day safety window has lapsed
  • UNKNOWN — no heartbeat has been recorded yet

Reminder Behavior

Dualhook sends reminder emails for due and overdue states. Reminder events are deduplicated — at most once per 24 hours per connection.

Recommended Routine

  1. Assign a primary and backup heartbeat owner.
  2. Open the WhatsApp Business App on a weekly schedule.
  3. Acknowledge heartbeat in Dualhook immediately after opening.
  4. Treat OVERDUE as an operational incident.

Related

  • WhatsApp CoexistenceHow Coexistence mode works: using WhatsApp Business App and Cloud API on the same number.
  • WhatsApp Webhook OverrideHow Dualhook uses WhatsApp Webhook Override to route supported customer-path webhooks directly from Meta to your server.
  • Messaging Health StatusMonitor phone number health: AVAILABLE, LIMITED, BLOCKED states and quality rating.
Browse more docsStart Free Trial