A bounced email usually means one of three things: the contact left, the email format changed when their company rebranded, or the address was wrong from the start. Guessing a new format — trying firstname.lastname@ instead of f.lastname@ — is unreliable and risks sending to the wrong person or hitting a spam trap. Repeated hard bounces also damage sender reputation, and that outlasts the campaign that caused it.
Validating the whole list before a campaign goes out prevents the bounce rather than fixing it.
Lusha in Claude skips the guesswork. One call returns the verified current address, confirms the contact is still at the company, and flags any title change that should change how the re-send is written. The whole check takes under a minute and 2 credits, and the result is either a confirmed address or a clear reason why it can’t be confirmed.
Data drawn from 290M+ verified contacts, sourced and processed under GDPR, CCPA, SOC 2 Type II, ISO 27001, ISO 27701, and TRUSTe Responsible AI. Full detail in the Trust Center and privacy notice.
FAQ
Why did my email bounce if the contact is still at the company?
Two common causes. The address was pattern-guessed rather than verified — firstname.lastname@ when the company uses f.lastname@ — or the company changed its email format during a rebrand or migration and old addresses were retired. A verified lookup distinguishes both from the third case, which is that the person left. If they’re still there, you get the current working address; if they’ve gone, you get that instead of another bounce.
How many credits does fixing a bounced email cost?
2 credits. One for the contact lookup, one to reveal the verified email. Revealing a phone number instead would cost 5, since phone reveal is 5 credits per contact against 1 for email. For a bounce fix you want the email, so the prompt on this page asks for email only.
What if the contact has left the company?
The prompt returns DEPARTED and looks for the likely replacement in the same function, with their verified email and title. That’s usually more valuable than the original fix — a departure means your CRM record was stale, and the replacement is the person who now owns whatever you were writing about. Update the record before resending, or the same bounce recurs next quarter.
What if Lusha returns NOT FOUND?
Treat it as a prompt to check your input rather than a dead end. Confirm the company name and spelling first, since a misspelled name can match a different organisation entirely and return the wrong record with no warning. If the input is right and the result is still NOT FOUND, the contact isn’t verifiable and the honest next step is a manual check rather than sending to an unverified address.
Should I update the CRM before resending?
Yes, and this is the part people skip. A bounce is a symptom of a stale record, and fixing only the address leaves the stale title and seniority in place, which breaks personalization tokens on the next campaign. If the prompt flags a title change, update that too — it changes how the re-send should be framed as well as who it should go to.
