How to find and verify work emails with Icypeas

You find a work email with Icypeas by giving it enough to identify the person and their employer, and then letting it work out and check the address. The basic input is a first name, a last name, and the company, and the company's website domain gives Icypeas a more precise target than the company name, because it tells Icypeas which mail server to test. Icypeas returns the address it found along with how certain it is about that address. If it can't find one, it says so instead of handing you a guess.

Verifying is the second half of the job, and Icypeas offers it as a separate search. You give it an email address you already have, such as one from an old export, a trade-show scan, or a CRM that hasn't been touched in a year, and Icypeas checks whether that mailbox exists and can receive mail. This matters because a list goes stale quickly. People change jobs, companies change domains, and every message that bounces makes the next one from your domain a little less likely to reach an inbox.

You can do all of this in Icypeas on your own. Its web app runs a single search or a bulk search on a file you upload, and it also offers a domain scan, which lists the shared role addresses at a company, such as the ones for sales or support. Icypeas has a public API as well, so other tools can send it searches and read the results. Every found address uses credits from your Icypeas plan.

Those routes find and check addresses well, but they leave the decisions with you. Before a run, someone has to add the company websites that are missing, drop the people who left months ago, and fix rows that Icypeas can't work from. After a run, someone has to read each result and decide which addresses go straight into a campaign, which ones need care, and which ones stay out. A good result is a list in which every person either has a work address with its verification result beside it or is plainly marked as not found, and in which the people you're about to email still hold the job you're writing to them about.

Kite handles both sides. It prepares the list, runs it through your Icypeas account, and sorts the results before anything reaches your outreach tool.

Start by telling Kite who you want work emails for. You can share the list in the conversation:

"Find work emails for everyone in this spreadsheet with my Icypeas account, verify the ones we already have, and add the good ones to our outbound sheet."

Or you can point Kite at people it found for you earlier:

"Run the prospects you pulled this morning through Icypeas and tell me who's ready to email."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. You can work with it in the Kite web app or in Slack. It reads a CSV or spreadsheet you share in the conversation, works from a list it built earlier, or reads contacts from a spreadsheet or CRM you've connected.

To use Icypeas, connect your Icypeas account to Kite by adding your Icypeas API key. Kite then runs every search on your own plan, so the credits come from your account.

Before it spends anything, Kite tells you its plan. It says how many people are on the list, how many need an address found, how many already have one to verify, which rows it is setting aside and why, and how many credits your Icypeas account has left. Confirm the plan, and Kite starts.

Kite gives Icypeas the strongest starting point it has for every row, because the input decides how many good addresses come back. It reads your list first and works out what each row holds.

When a row has a name and a company name but no website, Kite looks up the company and adds its domain. When a company sends email from a different domain than its website uses, Kite notes the email domain so Icypeas tests the right one. When a row has a LinkedIn profile URL but no name, Kite reads the name and current employer from the profile before it searches. When a row has a name and job title but no company, Kite can ask Icypeas to find the person's LinkedIn profile URL from their name and title, and then fill in the company from there.

Rows that still can't be searched, such as a first name with nothing else, go into a separate group. Kite lists them in its report so you can fill them in, rather than spending credits on searches that can't succeed.

Kite confirms that each person still works at the company on your list before it asks Icypeas for an address. It checks their public professional profile or the company's own pages and updates the row when someone has moved. A verified address doesn't help you if the person who used it left last spring. Icypeas can confirm that a mailbox accepts mail, but it can't tell you whether the right person still reads it.

When someone has changed jobs, Kite tells you and asks whether to look them up at their new company instead. That person is often the better contact, because a new role is a natural reason to get in touch.

Kite sends finding and checking to Icypeas as two separate kinds of search, because they answer different questions. People without an address go to Icypeas's email search with their first name, last name, and company domain or name. People who already have an address go to Icypeas's email verification, which checks that address instead of looking for a new one.

For a single person, Kite runs one search. For a list, it starts a bulk email search, which Icypeas processes in the background. Kite checks the progress of each search and collects the results as they finish, so a long list keeps moving without you watching it.

Kite reads your credit balance from your Icypeas account before a large run, and it stops to tell you if the run would use up what's left rather than running out halfway through. When you've asked Kite to find new prospects in Icypeas's own people database, it can count how many people match your filters first, which costs no credits, so you can see the size of the list before you pay for it.

Kite sorts every result by what Icypeas returned, because each outcome calls for a different next step. It keeps Icypeas's own result exactly as Icypeas gave it and adds a plain note about what to do with the address:

• Found and certain. Icypeas found an address and is confident in it. Kite marks these as ready for outreach.
• Found but less certain. Icypeas found a likely address but couldn't fully confirm it, which often happens when a company's mail server accepts every message. Kite keeps these on the list and flags them, so you can send to them in a smaller batch and watch for bounces.
• An existing address that failed verification. Kite marks the old address as one to stop using and runs a fresh email search for the person, using their current company.
• Not found. The person stays on the list marked as not found, along with the reason, such as no company domain or no result from Icypeas. Kite never fills the gap with a guessed address.

Kite doesn't promote a less certain result to a certain one, and it doesn't add personal email addresses, because the job is reaching people at work.

When Icypeas has no address for someone, Kite can try its own built-in work-email finder, which checks several sources in turn and verifies every address it finds. It labels which source each address came from, so you always know whether Icypeas or another source supplied it.

When you need to reach a company rather than a particular person, Kite can run Icypeas's domain scan on that company's domain to find its role addresses, such as the shared inbox for sales. It keeps those addresses apart from your personal outreach, because a message written to one person reads oddly in a shared inbox.

When the run finishes, Kite saves the list where you asked and reports what happened in the conversation. It can add the results to a connected spreadsheet, update the contacts in your connected CRM, or add them to your connected outreach tool. It matches rows by name and company, so each address lands on the right record.

The report gives the number of addresses Icypeas found, how many existing addresses passed or failed verification, and how many fall into each group above. It lists who is still missing and why, who changed jobs, and which rows Kite set aside before the run. The full list comes with it as a table you can scan in the conversation.

From there, Kite can write a personalized outreach email for each contact marked ready, using research on their company to give it something relevant to say, and it shows you the emails before anything is sent. If new people join your list every week, ask Kite to run the same job on a schedule, and it will report each run in the same place.

When Kite finishes, you have one list in which every person either has a work address with Icypeas's result beside it or is clearly marked as not found.