Implementing a Do Not Contact List in Clay for Lead Sourcing

Noor S. · 2024-09-23 11:26:05.620172+00

Is there a way we can include a do not contact list of companies/contacts that/companies who are already our clients in our Clay so when we source leads, those contacts are excluded?

Implementing a Do Not Contact List in Clay for Lead Sourcing | Clay

9 comments

· Sorted by Oldest

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Muhammad S.
·
·
You can create a centralized DB in google sheets or a faster DB like xano and when you are sourcing leads you can do a lookup record in your DB and if it exists it means they are your client and you do not proceed with that specific company/lead. You can control your runs via run conditions i.e do not proceed if the record is found via a lookup in your DB
Stefan F.
·
·
Just asked a similiar question. Maybe it works with the "exclude companies" beta function, but still waiting for a repl from the support :9
🙌1
Noor S.
·
·
Hmmm. Just read your question. Lets wait on their response. Thanks 🙂!
Noor S.
·
·
Can you share a loom on this?
Noor S.
·
·
Muhammad S.
Bo (.
·
·
Hey, thanks for reaching out! To handle this, you’ll want to create an exclusion table. Here’s an example: • Table 1: Your “do-not-contact” list. • Table 2: Upload your newly found data, then use the ClayLookup to cross-reference that data and remove any with a match. You can do this either through table filters or by selecting and deleting the matching rows. As for the exclusion in the Find People/Companies search, it only works for previous searches. The exclusion is calculated based on the results of those specific searches. Let me know if you need any further clarification! 😊
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Noor S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Muhammad S.
·
·
You can create a centralized DB in google sheets or a faster DB like xano and when you are sourcing leads you can do a lookup record in your DB and if it exists it means they are your client and you do not proceed with that specific company/lead. You can control your runs via run conditions i.e do not proceed if the record is found via a lookup in your DB
Stefan F.
·
·
Just asked a similiar question. Maybe it works with the "exclude companies" beta function, but still waiting for a repl from the support :9
🙌1
Noor S.
·
·
Hmmm. Just read your question. Lets wait on their response. Thanks 🙂!
Noor S.
·
·
Can you share a loom on this?
Noor S.
·
·
Muhammad S.
Bo (.
·
·
Hey, thanks for reaching out! To handle this, you’ll want to create an exclusion table. Here’s an example: • Table 1: Your “do-not-contact” list. • Table 2: Upload your newly found data, then use the ClayLookup to cross-reference that data and remove any with a match. You can do this either through table filters or by selecting and deleting the matching rows. As for the exclusion in the Find People/Companies search, it only works for previous searches. The exclusion is calculated based on the results of those specific searches. Let me know if you need any further clarification! 😊
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Noor S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: