WhatsApp में एक grey tick: block या नहीं, base में क्या करें
AndySendy academy
← सभी पोस्ट

🚫 WhatsApp में एक grey tick - हमेशा block नहीं। पर इन contacts से काम करना ज़रूरी

कई operators मानते हैं: एक grey tick = block। Automatic BlackList filters इसी पर - analytics टूटती है, false control। इस लेख के बाद «blocked» vs «undelivered» अलग, list cleanup logic clear।


Block पर delivery कैसे काम करती है

User ने block किया तो आगे messages «server पर sent» रहते हैं, आगे नहीं। Recipient device नहीं पाता - Meta chain one-way काटता।

Sender view: message हमेशा एक grey tick। दो grey (device delivered) या blue (read) technically impossible। Block notification नहीं - कोई system message नहीं।

Block के दौरान भेजे messages unblock के बाद «deliver» नहीं - permanently gone।


Myth fix: एक tick ≠ block

Automation से पहले lock in करें।

एक grey tick = message WhatsApp servers तक पहुँचा, recipient device तक नहीं। कई reasons:

Cause One tick Avatar gone No Last Seen
Blocked Likely Likely
Phone off
No internet
WhatsApp removed
Privacy
Abandoned number

Block diagnosis combined signals - single marker नहीं:

100% proof नहीं - privacy settings। Meta official API «blocked you» directly नहीं देता।


Problem contacts tag कैसे करें

Straight «BlackList» की जगह tiered status:

Undelivered - one tick 12–24+ hours। Watch; current wave से auto-drop नहीं।

Suspected Blocked - one tick 48–72+ hours, no avatar, no activity। Next waves skip, list से delete नहीं।

BlackList - spaced checks के बाद confirmed non-delivery, indirect signs match। All campaigns exclude।

Why tiers: कुछ Suspected Blocked वापस आते - charge, internet, reinstall। तुरंत delete = reachable contacts lost।

Mini-case। Agency: 12h बाद one tick + no avatar → CRM WA_Blocked, trigger chains exclude। 6 months no ban। List self-cleaned before systemic risk।


Undeliverable numbers पर send account risk

Operator observations (official Meta statement नहीं), delivered vs undelivered ratio track। Normal user <5% one-tick daily। Old/low-quality lists → 30–50%।

Forum benchmark: one session में >15–20% undelivered risky। Official Meta limit नहीं। Logic: dead sessions पर monotone no-reply = Blind Spamming। Outreach metrics overlap।

Mini-case। Marketer weekly blasts; ~50 had blocked early। No filter - every wave। Week 3: permanent ban first 5 min of 200 sends। Low volume, critical undelivery ratio।


WABA: different mechanics

Official API - Webhooks, JSON। Blocked number पर template → Undeliverable etc।

Black List logic error codes पर, browser visual cues नहीं। Webhook error → Suspected Blocked → recheck/exclude।

Undelivered template billing - integrators disagree। Reseller/Meta Developer Docs confirm - policies change।


Disputed: avatar check without send

Unofficial tools (Baileys, whatsapp-web.js) avatar URL without message claim। Server error → instant BlackList।

Opponents: 2026 Meta frequent avatar requests unknown numbers = parsing, ban faster than outreach। Disputed - standard practice नहीं।


Undeliverable contacts algorithm

  1. Send → wait status।
  2. 12–24 h → one tick → Undelivered, keep, skip next wave।
  3. 48–72 h → one tick + no avatar + no activity → Suspected Blocked, drop triggers।
  4. 7–14 days recheck → one tick again → BlackList
  5. BlackList → full exclude। Delete नहीं - historical data।

Single marker logic न बनाओ। Combined signals = fewer false positives।


🎯 अगला कदम

Check tool undelivered handling। Undelivered, Suspected Blocked, BlackList separate नहीं - risk। Basic filter: 72+ h one tick → next waves से auto-drop।

निष्कर्ष

Practical rule:

One tick watch signal, verdict नहीं। Silent undeliverables ignore - account reports से fast kill।