8. Reports and Statuses: Analysis and Database Cleaning

Table Of Contents
  1. 🎯 About This Guide
  2. 📊 WhatsApp Statuses: Complete List
  3. 🔍 Status Combinations: What They Mean
  4. ⚠️ CRITICAL: Sent But NOT Delivered
  5. 🤔 CONSIDER: Delivered But NOT Read
  6. ✅ GOOD: Delivered and Read
  7. 📈 Database Segmentation by Statuses
  8. 🛠️ Practical Guide: Database Cleaning
  9. ⏱️ Time Frames and Risks
  10. 💡 Practical Tips
  11. 🎯 Report Analysis Examples
  12. 🚨 Signs of Imminent Blocking
  13. 📚 Related Documents
  14. ⚠️ Main Rules

🎯 About This Guide

How to read statuses after mailing, analyze results and clean database from dead contacts to avoid account blocking.

Important: Basic information about statuses and retries is described in <a href=”https://androidsender.com/whatsapp-web-sender-message-status/”>Sending Statuses →</a>

📊 WhatsApp Statuses: Complete List

Basic Statuses (Quick Overview)

StatusMeaningColorpendingWaiting to send⚪ GraysentSent🟢 GreendeliveredDelivered to recipient🟢 GreenreadRead by recipient🟢 GreenerrorSending error🔴 Red

Details on basic statuses: <a href=”https://androidsender.com/whatsapp-web-sender-message-status/#sending-statuses”>Sending Statuses →</a>

🔍 Status Combinations: What They Mean

Format: current:previous

After retry mailing, status is recorded with colon:

  • First (before colon) — current status
  • Second (after colon) — previous status

⚠️ CRITICAL: Sent But NOT Delivered

Status: sent:pending or sent:sent

What this means:

  • Message sent from your side
  • BUT not delivered to recipient
  • WhatsApp did not confirm delivery

Why this happens:

  1. You are blocked by recipient — most likely
  2. Number doesn’t exist or deleted
  3. Recipient has internet off for long time
  4. WhatsApp technical issues (rare)

❌ ACTION: CATEGORICALLY EXCLUDE FROM DATABASE

Why this is dangerous:

  • Retry sending to such recipients sharply increases blocking risk
  • WhatsApp tracks that you send messages to those who blocked you
  • Each new attempt = +10% to ban risk
  • Daily/hourly retries = guaranteed blocking

How to clean database:

  1. Export mailing results
  2. Filter Excel: find all sent:pending and sent:sent
  3. DELETE these rows from database forever
  4. Save cleaned database
  5. Use only it for next mailings

Details on export: <a href=”https://androidsender.com/whatsapp-web-sender-excel-lookups/#save-mailing-results”>Saving Results →</a>

🤔 CONSIDER: Delivered But NOT Read

Status: delivered:pending or delivered:delivered

What this means:

  • Message delivered to recipient
  • BUT they didn’t open/read it
  • Can be long time (days/weeks)

Why this happens:

  1. Recipient not interested in your mailing — main reason
  2. Recipient doesn’t check WhatsApp regularly
  3. Message lost among others
  4. Recipient ignores unknown numbers

⚠️ ACTION: PUT UNDER QUESTION

Why this is a problem:

  • Low recipient engagement = spam signal for WhatsApp
  • Repeated mailings to such people gradually increase blocking risk
  • Not critical like sent:pending, but accumulates over time

What to do:

Option 1: Give Second Chance

  • Wait 3-7 days after first mailing
  • Send ONE retry with different text
  • If again delivered:pending — delete from database

Option 2: Segment Database

  • Create separate list “cold contacts”
  • Send them rarely (once a month)
  • Use maximum text variations
  • Monitor reaction

Option 3: Delete Immediately (safe)

  • If database is large and you can afford loss
  • Keep only active readers
  • Minimize risks

✅ GOOD: Delivered and Read

Status: read:delivered or delivered:read

What this means:

  • Message delivered AND read
  • Recipient opened chat and saw your message

Why this is valuable:

  • Live recipient — real person
  • Interest in messages (at least minimal)
  • Low blocking risk on repeated mailings
  • May not be interested in product, but does NOT ignore

✅ ACTION: KEEP IN DATABASE

How to work with this group:

  • This is your main audience for mailings
  • Can send more often (but with reasonable intervals)
  • Use personalization and variations
  • Monitor reaction — if stop reading, reconsider strategy

📈 Database Segmentation by Statuses

Category 1: DEAD (delete immediately)

Statuses:

  • sent:pending
  • sent:sent
  • error:error (repeating errors)

Action: ❌ DELETE from database

Risk on retry: 🔴 CRITICAL

Category 2: COLD (consider)

Statuses:

  • delivered:pending
  • delivered:delivered (not reading long time)

Action: ⚠️ Give 1 chance or delete

Risk on retry: 🟡 MEDIUM (accumulates)

Category 3: WARM (main database)

Statuses:

  • delivered:read
  • read:delivered
  • read:read

Action: ✅ Keep and work

Risk on retry: 🟢 LOW

Category 4: HOT (if replies exist)

Signs:

  • Read
  • Received reply in personal chat
  • Asked questions

Action: ✅ Priority group

Risk on retry: 🟢 MINIMAL

🛠️ Practical Guide: Database Cleaning

Step 1: Export Results

  1. After mailing click “Export”
  2. Open Excel file
  3. Find column “Sending Status”

Details: <a href=”https://androidsender.com/whatsapp-web-sender-excel-lookups/#data-export”>Data Export →</a>

Step 2: Filter DEAD Contacts

In Excel:

  1. Select “Sending Status” column
  2. Enable Filter (Data → Filter)
  3. Filter by values:
    • sent:pending
    • sent:sent
    • error:error
  4. Select all filtered rows
  5. DELETE them

Step 3: Analyze COLD Contacts

  1. Filter by:
    • delivered:pending
    • delivered:delivered
  2. Decide: give second chance or delete
  3. If keeping — mark as “cold” in separate column

Step 4: Highlight WARM Contacts

  1. Filter by:
    • read:delivered
    • delivered:read
    • read:read
  2. This is your main database — save separately
  3. Use for regular mailings

Step 5: Save Cleaned Database

  1. Save file with only active contacts
  2. Use it for next mailings
  3. Dead contacts can save to archive (just in case)

⏱️ Time Frames and Risks

Retry Sending Risk Table

Recipient Status1st attempt2nd attempt3rd attempt4th+ attemptssent:pending (not delivered)🟡 Medium🔴 High🔴 CRITICAL🔴 BANdelivered:pending (not reading)🟢 Low🟡 Medium🟡 High🔴 Criticalread:delivered (reading)🟢 Low🟢 Low🟢 Medium🟡 Medium

Recommended Intervals Between Mailings

For WARM (reading):

  • Minimum: 3-7 days between mailings
  • Optimal: 1-2 weeks
  • Safe: once a month

For COLD (not reading):

  • Give 1 chance after 7-14 days
  • If not read again — delete
  • DO NOT send more than once a month

For DEAD (not delivered):

  • ❌ DO NOT RETRY
  • Delete from database immediately

💡 Practical Tips

Tip 1: Regular Database Hygiene

After each mailing:

  1. Export results
  2. Delete dead contacts (sent:pending)
  3. Analyze cold ones (delivered:pending)
  4. Update main database

Tip 2: Keep History

  • Don’t delete old exports
  • Keep archive with dead contacts
  • Analyze dynamics (how many contacts losing)

Tip 3: Test on Small Groups

  • Before large mailing test on 50-100 contacts
  • Look at status ratio
  • If many sent:pending — check database quality

Tip 4: Don’t Be Greedy

  • Better fewer contacts but live ones
  • 100 readers better than 1000 dead
  • Database quality > contact quantity

Tip 5: Monitor Trends

If you see growth of:

  • sent:pending — database outdated, needs cleaning
  • delivered:pending — content uninteresting, change approach
  • error — technical problems, check settings

🎯 Report Analysis Examples

Example 1: Successful Mailing

Results after 1000 contacts:

  • read:delivered — 600 (60%)
  • delivered:pending — 250 (25%)
  • sent:pending — 100 (10%)
  • error — 50 (5%)

Analysis:

  • ✅ 60% reading — excellent result
  • ⚠️ 25% not reading — give second chance
  • ❌ 10% not delivered — DELETE
  • 🔧 5% errors — check numbers

Actions:

  1. Delete 100 sent:pending → database 900 contacts
  2. Retry for 250 delivered:pending after week
  3. If don’t read — delete → database 600-700 contacts
  4. Work with 600-700 active recipients

Example 2: Problem Mailing

Results after 1000 contacts:

  • read:delivered — 150 (15%)
  • delivered:pending — 200 (20%)
  • sent:pending — 500 (50%)
  • error — 150 (15%)

Analysis:

  • ❌ 50% not delivered — CRITICAL
  • ❌ Database outdated or bought
  • ⚠️ High blocking risk on retries

Actions:

  1. IMMEDIATELY delete 500 sent:pending
  2. Delete 150 error
  3. Database shrinks to 350 contacts
  4. Check source — where database from?
  5. Don’t buy such databases anymore

🚨 Signs of Imminent Blocking

If you see:

  • More than 30% sent:pending after mailing
  • Repeated mailings to same sent:pending contacts
  • Growing number of error from mailing to mailing
  • Recipient complaints (if any)

ACTIONS:

  1. Stop mailings for 3-7 days
  2. Immediately clean database from dead
  3. Reconsider strategy and content
  4. Resume with small volumes (50-100 per day)

📚 Related Documents

⚠️ Main Rules

  1. sent:pending = DELETE FOREVER — blocking risk is critical
  2. delivered:pending = CONSIDER — give 1 chance or delete
  3. read:delivered = KEEP — your main audience
  4. Clean database after EVERY mailing — not optional, but necessary
  5. Quality > Quantity — better 100 live than 1000 dead
Scroll to Top