Hunter

Your assistant can run each address through Hunter's verifier and report back what came out: valid, invalid, or one of the two uncertain states Hunter uses. Those two matter more than the pass rate. An accept-all domain answers yes to everything, and a risky result is a coin flip, so a list that looks clean can still be half guesswork. It can check your remaining verification allowance first so a long list does not stop halfway.

What you end up with. Every address sorted into valid, invalid, and uncertain, with the uncertain ones named individually rather than folded into the good pile.

Start with it bringing you the information and you deciding.

Never without. Never treat accept-all or risky as valid. Hunter says so in its own response and it is the difference between a clean send and a domain reputation problem you find out about three campaigns later.

Built on: Email Verifier / Account Information

Give it the person and the domain and it returns the most likely address with a confidence score attached. If the guess is weak, it can widen out and pull the public addresses Hunter holds for that domain, which usually reveals the pattern the company uses and lets you check the guess against a colleague whose address is already known. Each finder call spends credits, so it is worth asking for the free count first when you are working through a long list.

What you end up with. A single address with its confidence score, plus the naming pattern the company appears to use so you can judge the guess yourself.

Start with it bringing you the information and you deciding.

Never without. Read the confidence score before you send anything. A low-confidence result is a pattern-matched guess at a real person's address, and sending to it is how you land in a spam trap or in a stranger's inbox.

Built on: Email Finder / Domain Search / Email Count

It can pull the public addresses Hunter holds for a domain along with the job titles, departments, and seniority attached to them, and it can get the counts broken down the same way without spending credits. That turns a company name into a short list of the people who plausibly own the thing you are calling about, rather than a guess at whoever answers.

What you end up with. A named list of contacts at the company with title, department, and seniority, and a count of how many more exist that you have not pulled.

Start with it bringing you the information and you deciding.

Never without. Treat every title as the date Hunter last saw it, not as today. People change jobs and the record does not, so check the person still works there before you write anything that assumes it.

Built on: Domain Search / Email Count / Company Enrichment

From the address alone it can return the person's name, job title, location, and social handles, and the company's industry, size, and description, either separately or in one combined lookup. Useful before a first call, and useful for the reply where you are trying to work out whether this is a buyer, a vendor, or a student. It reads and saves nothing.

What you end up with. A short written profile of the person and the company behind an address, ready to skim before you reply or dial.

Start with it bringing you the information and you deciding.

Never without. Keep this to the business question in front of you. Enriching an address is a normal commercial check, and building a standing file on a person from repeated lookups is a different activity with different obligations.

Built on: People Enrichment / Company Enrichment / Combined Enrichment

Hunter carries a company dataset you can query by industry, location, headcount, and other characteristics, or describe in plain language. Give it the shape of the accounts that already work for you and it returns matching companies, and it can enrich each one so you see the detail before deciding anything. This is a research pass, so nothing enters your account until you say so.

What you end up with. A candidate account list with industry, size, and location on each row, ready for you to cut before anyone gets contacted.

Start with it doing the work and checking with you.

Never without. Say out loud what makes your good customers good before you ask. A filter set built from headcount and industry alone returns companies that resemble your customers on paper and not in any way that predicts a sale.

Built on: Discover Companies / Company Enrichment / Domain Search

It can create a leads list, then add each prospect to it with the fields Hunter carries, and update a record that is already there. There is a single call that creates or updates by email address, which is the one to use on a repeat import, because it keeps one record per person instead of quietly stacking near-duplicates. If you track something Hunter has no field for, it can create a custom attribute first and fill it in on the way through.

What you end up with. A named leads list holding one record per person, with your own fields populated and no duplicate entries from an earlier import.

Start with it doing the work and checking with you.

Never without. Confirm which list it is writing into by name, and prefer the create-or-update call on any import you might run twice. Plain create has no idea the person is already in there.

Built on: Create Leads List / List Leads Lists / Create Lead / Upsert Lead / Update Lead / Create custom lead attribute / List Custom Attributes

It can. Hunter exposes deletion for a single lead, for a whole leads list, and for a custom attribute, and none of the three comes back. Run it in two moves rather than one. Have it list the leads matching your rule and show you that list, read it, then approve deletion of exactly those records. Deleting a list removes the container, so confirm what is inside before you point it at one.

What you end up with. The dead records gone, and a saved list of every lead removed with the email address and the reason it qualified.

Start with it doing the work and checking with you.

Never without. Never approve a deletion described only as a rule, and never delete a leads list without reading what is in it first. A deleted lead takes its notes, its custom attributes, and its history with it, and the connection offers no way to bring any of that back.

Built on: List Leads / Get Lead / Delete Lead / Get Leads List / Delete Leads List

It can read your account and report the searches and verifications you have left, and it can get the volume of addresses on a domain for free before you commit any credits to pulling them. Ask this before a bulk run rather than after, since the failure mode is a half-verified list that reads as if it were fully checked.

What you end up with. Your remaining search and verification allowance, next to the size of the job you were about to run.

Start with it bringing you the information and you deciding.

Never without. Check the number before the bulk run, not during it. A list that stopped partway through verification looks identical to one that finished.

Built on: Account Information / Email Count / List Campaigns