Why are WhatsApp Status notifications failing for 35% of contacts?

Introduction

WhatsApp Status notifications failing for 35% of contacts presents a significant product issue that could impact user engagement and overall satisfaction. I'll approach this problem systematically, focusing on identifying the root cause, validating hypotheses, and developing both short-term fixes and long-term solutions.

Step 1

Clarifying Questions (3 minutes)

• Looking at the scope, I'm thinking this might be a recent issue. Has this 35% failure rate emerged suddenly or gradually over time?

Why it matters: Helps determine if it's a new bug or a growing problem. Expected answer: Sudden increase in the past week. Impact on approach: Sudden change suggests recent code or infrastructure changes.

• Considering user segments, I'm wondering if this affects all types of users equally. Are we seeing any patterns in terms of device types, operating systems, or geographical regions?

Why it matters: Identifies if it's a universal issue or specific to certain user groups. Expected answer: More prevalent on Android devices in certain regions. Impact on approach: Narrows focus to specific platforms or regional infrastructure.

• Thinking about the notification system, I'm curious if this is isolated to Status notifications or if other types of WhatsApp notifications are affected?

Why it matters: Determines if it's a Status-specific problem or a broader notification issue. Expected answer: Only Status notifications are affected. Impact on approach: Focuses investigation on Status feature and its notification mechanism.

• Considering recent changes, have there been any updates to the Status feature or the notification system in the past month?

Why it matters: Identifies potential triggers for the issue. Expected answer: Recent backend changes to optimize Status delivery. Impact on approach: Directs attention to recent code changes and their impact.