🛱 Case Study 01 · Lead Quality & Outreach

Mystery Shopping AI Automation System

A quality-assurance outreach engine: every prospect address is verified at the DNS + SMTP protocol level before a single email is spent, then campaigns fire from four inboxes on a human-paced schedule.

📸 Built running live

$ build_optimized_mystery_verifier.py

[DNS] resolving MX records ... cached per domain
[SMTP] RCPT TO probe → catch-all detection
[RESULT] 5,000 raw → 2,847 verified → 1,9xx deliverable-whales

Verification waterfall — this run happens for every lead

$ SCHEDULE_MYSTERYSHOPPING_CAMPAIGN.bat

Inboxes : owais@ · hirabaig@ · wes@unseenresearch · wes@wesms
Leads   : 22 / 22 / 22 / 21
Stagger : ~11 min between sends per inbox
Window  : Mon 18:30–22:30 IST

4-inbox staggered send that looks human, because it is paced like a human

⚙️ How the pipeline runs

Lead Pool
CSV → master DB

→

DNS Layer
MX records · provider detect · catch-all flag

→

SMTP Layer
toxic-domain kill · RCPT probe · domain cache

→

Verifier
concurrent workers, cached domains

→

Zoho Scheduler
4 inboxes · 11-min stagger · time-windowed

→

Campaign Status Monitor
per-account progress

🧗 The engineering moat

Protocol-level truth, not API guesses: verification reads MX records directly, identifies the mailbox provider, flags catch-all domains, then probes with SMTP — the same checks premium verification services charge per-credit for.
Domain cache: every domain is resolved once, then reused — so 20K sends don't mean 20K DNS lookups.
Human-shaped delivery: sends are staggered ~11 minutes per inbox inside an evening window, spread across 4 warm sender identities — protecting every domain's reputation.
Concurrent workers with clean output: thread-pooled verification keeps throughput high without hammering mail servers.

📊 Client-facing outcome

4inboxes orchestrated

~11 minhuman-paced stagger

100%of sends verified pre-flight

0paid verification APIs

Drop a raw list in. Get back a campaign that only emails real, deliverable, human-operated inboxes — deliverable-checked recipients — from multiple sender identities, on a schedule that mimics manual outreach.