Deliverability · 7 min read
Verify before you enroll: credits, MX, and million-row jobs
Enrollment without verification is how domains get burned. BharatGuru AI treats verify, enrich, finder, and import as the same family of jobs — cursor-paged, file-backed, built to survive million-row nights.
Single lookups belong in the product UI. Volume belongs in Job Center. Dumping two million rows into a table is not a product; paging members and streaming status is.
Credits exist so accuracy is not free-for-all. Fifty credits on signup are enough to prove the agent on your book. After that, plans and packs are the meter.
When a job returns catch-all or unknown, do not auto-enroll. Catch-all is a maybe. Unknown is a retry. Valid is the only green light for a sequence.
Keep reading
Find, don’t invent: why guessed mailboxes poison your sequences
info@ and first.last@ look complete in a CRM. They are not leads. How BharatGuru AI refuses filler when the public web is silent.
Read playbookGoogle-style lead search: “VP Sales at BharatGuru AI in Bengaluru”
One line of intent, not twelve filters. How title, company, and location parse into a public-web fan-out.
Read playbookCompany pages are gold: /about, /team, /contact
Directories lie. Careers pages age. The team page is still the highest-signal public source for org mailboxes.
Read playbook