🔍 Number जलाने से पहle dead base कैसे पहचानें

Agency ने 10,000 purchased numbers पर blast। 40 messages - 18 failed delivery। Message 41 पर 2-year high-trust account permanent ban। Cause: list - 15-min pre-audit में दिख सकता था।

Guides text/timing/warm-up cover - list rarely। List decides day-two survival। Dead list = age + source + mobile % + activity - mostly visible pre-send।

Dead base - 5 problems

Type	Meaning	Detect
Invalid	no WA JID	validator/Cloud API
Inactive	account unused	Meta binary only
Duplicate	repeat	dedup
Landline/fax	can't be WA	HLR
Format	not E.164	length check

5 toxic signs

>6 months old - ~3–5% decay/month heuristic।
Purchased/scraped unfiltered - cold vs warm।
<70% mobile - landlines can't register।
Dupes - Excel segmentation।
No activity - legal risks।

15-min express audit

E.164 + dedup।
Validator - WABA or Baileys; cloud 10k in 5–15min - migration।
HLR - mobile vs landline।
Carrier/region slice - chaotic mix = purchased junk heuristic।

Metrics

Quality Rating ≥0.80; Bounce ≤2%; Complaint ≤0.1%; test Failed <5%; stop >30% on 50 - A/B, ban, antispam। Test 50 - first cold।

Fail vs success, checklist, multi-account

10k no audit → ban msg 41; audited 2600 clean → 98% delivery। Multi-account doesn't fix - economics।

Meta: registered yes/no only।

🎯 अगला कदम

Validator run - invalid % + landline share record।

निष्कर्ष

व्यावहारिक नियम:

Message rewrite after complaint possible। Dead-list ban not - audit before launch।