Where
Leads→Prospects
Your role needs
Read access to Prospects
read-leads. Admin, Member and Viewer have it by default.To create or change
create-leads to add one, update-leads to change one, on top of the permission above.If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.
Before you begin
- You need permission to update leads. Without it you still see the verified badge and the failed icon, but there is nothing to press and clicking the failed icon does nothing.
- The row only ever checks the lead’s first email address. A lead with more shows a ”(+1 others)” line underneath, and those addresses are not part of this check.
- The list shows leads that already have an email or a phone, so a lead with nothing on file is not on it. A lead reachable only by phone is, and its row has no address to check.
Steps
1
Find the address
Go to . Each lead’s first email address sits in the Email / Phone
column, and the mark beside it says where that address stands. A red × (1) means it failed verification;
its tooltip reads “Email verification failed. Click to verify again.” A small blue badge with a white tick
(2) means verified, and hovering it reads “Email verified”. An outlined Verify button (3) means the
address has no answer against it yet; hovering it reads Validate email.
2
Click Verify, or the red × to try again
Both run the same check, and both run it inside the request rather than queueing a job: nothing to wait
on, nothing to poll. The button reads “Verifying…” while the answer comes back.
3
Read the result
A notification reports one of three outcomes, and the row updates to match:
- “Email verification result: verified” means the row now shows the blue badge.
- “Email verification result: failed” means the row shows the red ×; click it any time to try again.
- “Email verification was inconclusive” means nothing on the row changes, and the Verify button is still there.
What happens next
A verified or a failed result is written against the address and the row redraws with the new mark. An
inconclusive one writes nothing, so the row is exactly as you left it and the Verify button is still
there the next time you look.
Troubleshooting
It comes back inconclusive every time
It comes back inconclusive every time
Only a verified or a failed result is written to the address. An inconclusive one leaves nothing behind,
so the next click runs the same check again with the same odds of the same answer. A catch-all domain,
which accepts mail for any address, lands here; so does a mailbox that reports itself full, and so does one
that stalls the check (greylisting, a blocked connection, a timeout). See
Email verification was inconclusive for what to do
about an address stuck this way.
It fails with an error instead of a result
It fails with an error instead of a result
A notification reading “Error verifying email” means the request itself did not complete, so no answer was
recorded either way. Click Verify again; if it keeps failing, email
support@pipelime.ai.
Related
Email Verification: verdicts and what they mean
The five internal verdicts behind the three words you see here, and everywhere else in the product they show up.
Email verification was inconclusive
Why a catch-all or greylisting domain can’t give a straight answer, and what outreach does with an address stuck there.
Working the Prospects list
Every other column and row action on the same table this page lives in.
Leads troubleshooting
Symptom-first answers for the rest of what can go sideways with a lead.