Colin G.

Any Lemlist users having major deliverability issues in the last week? And has anyone uncovered the root cause / fix? (not looking to be pitched on another product)

Hi guys, I’m facing a repeated issue. The most common “no” response we get from our cold outbound is consistently “I no longer work at this company”. No matter whether I use Clay, Apollo, or Linkedin enrichment as my data source, this is without a doubt our most common error. I’m even using additional meta-data fields like “is current” in their most recent job to verify that it’s legit, still - this “I no longer work here” response makes up >50% of my negative responses. The only way I can think to solve for this problem would be to have clay to manually scrape their LinkedIn profile and confirm that this is the most up-to-date position. However, we will need to run this on every row, and it would be extremely expensive. Has anyone else faced this issue, and come up with a better workaround?

Does anyone have ideas on how to find the emails of people who aren’t on LinkedIn without using Clay credits? Context: We have a csv of 15k physiotherapists, including their name, clinic name, and address. Obviously I don’t want to use a Clay waterfall on 15K rows. So far, we’ve tried

So far, we haven’t had promising results. Not looking to pay for services, Just looking for suggestions! Any and all appreciated.