Verify the contact emails in your Close leads
Close has no SimpleVerifier connector. Export contacts, verify the CSV, then use Close's importer to update existing leads. Close lets you undo any import from its History tab, which makes it a forgiving CRM for a first cleaning run.
The workflow
- In Close open Leads, apply filters if you want part of the list, then open the ... menu at the top right > Export. Set Type to Contacts, choose CSV and the fields (Common fields or All fields), and start the export. Contacts are exported from the Leads page, not the Contacts page. Download from the link Close emails you; it expires after 7 days.
- Upload the CSV on the verify page, signed in; the first 100 checks are free. The email column is found by its header or contents and every other column is kept.
- When the job finishes, download the valid, risky and invalid files. Each keeps all of your original columns.
- Create a Close custom field on contacts or leads called Email status (a choice or text field).
- Go to Import Data and upload the verified file. Assign each column to a Close field, and on the Options page pick Lead ID or another unique field as the comparison field. Choose Only add missing information, and Skip the Lead if nothing matches, so the importer only updates.
- Check the result under the History tab. If something looks wrong, undo that import from there. Then create a Smart View with Email status is not invalid for your sequences.
Menu names follow Close’s own help articles, checked 12 Nov 2026: exporting data, updating existing leads and contacts. Vendors rename menus, so trust what you see on screen if it differs. SimpleVerifier is not a Close partner and has no Close connector.
Columns to map
- Lead ID, or another unique field, as the comparison field that decides which lead is updated.
- Contact email, with several addresses separated by a semicolon if one contact has more than one.
- Email status, your custom field mapped to the result. Choice fields must already exist before the import.
What to do with risky and catch-all results
Do not delete risky leads. Set their Email status to risky, keep calls and SMS going, and move their email into a separate Smart View so you can send in small batches. If a risky address bounces, Close shows it; mark that contact invalid then.
What people use it for
- Clean a lead export before loading it into a Close sequence.
- Remove bad addresses from a Smart View that a team sends from every day.
- Check a list from a lead-data vendor before it goes into Close.
Using the result
Each address comes back valid (the mail server confirmed the mailbox), risky (delivery could not be confirmed: a catch-all domain, a role address such as info@, or a provider that hides mailbox status) or invalid (it will bounce, or it is a throwaway address).
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Comparing tools? See email verifiers for Close compared, with prices checked on each vendor’s site.
Run your 100 free checks on one list before you switch anything
Export one list’s addresses as a CSV and upload it: the first 100 are checked free in the dashboard, no card needed. Compare the results with what you use now, then decide. Nothing in Close changes until you import a file back.
Common questions
- Which plans include API access for Close?
- API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- Can I reverse the import if I get the mapping wrong?
- Yes. Close lets you undo an import, including an update-only one, from the History tab on the Import Data page.
- Is SimpleVerifier in Close's integrations list?
- No. There is no listing or connector; this page is the CSV workflow.