.png){kind=logo}
Possible to help fix this AI prompt for checking duplicates?
Possible to help fix this AI prompt for checking duplicates?
Possible to help fix this AI prompt for checking duplicates?
To optimize your AI prompt for checking duplicates, use the "Help me" button (metaprompter) in the AI enrichment configuration. Click "Generate with prompt" in the Use AI enrichment, enter your desired outcome in the Task description field, and it will generate a tailored prompt for duplicate checking. You can also browse pre-built templates by clicking "Browse Templates" for common duplicate detection use cases. If you need further help, request human assistance by clicking on Talk to a person.
Won't return anything other than insufficient data, but the prompt is fairly straightforward
Hi Umer I., thanks or jumping in - Duplicate/exact email address matches are not a problem for us. We're running into scenarios where multiple data sources feed in contacts to our CRM and they either have slightly different email addresses (jdoe@companyname.com or john@companyname.com) or one contact has an email address and one does not (but it's the same contact).
Tried to use Formula Generator as well and this is what the sample output looks like - Blank fields even though the data in entered into the table
Hello Ben! Thanks for reaching out! To confirm we are on the same page, you have multiple data sources feeding into your CRM (Clay being one of them) and you only want to search for/update the email in your CRM if the email field is blank. And you want to do that to avoid duplicates or multiple emails for the same contact in your CRM. Or is it that you want to check for duplicates within this Clay table? Your table suggests the latter but I am not entirely sure. For the slight variations that you mentioned, it could be difficult to identify that since Clay does not compare row wise. We can try finding a workaround here however. For the second issue, it seems to me a UI bug which I have gone ahead and filed a report for. However it should not affect your action since the column will run for all the rows. I will keep you updated on the bug. However looking at the intensity of it, not sure of the timeline here. When it comes to the formula column, this is very unusual and have not seen anything like it before. Do you mind saving this formula column so that I can take a look?
Sayli G. thank you so much for reaching out! Please see my responses below. "You have multiple data sources feeding into your CRM (Clay being one of them)" - No, we are populating data into our CRM (DealCloud) from other sources and then manually importing the contact information from our CRM directly into Clay for enrichment and processing. Clay is not connected to our CRM currently. "Or is it that you want to check for duplicates within this Clay table? Your table suggests the latter but I am not entirely sure." Yes, the latter is correct. "it could be difficult to identify that since Clay does not compare row wise. We can try finding a workaround here however." - Really appreciate any help or guidance you can offer. Was not aware that Clay does not have the ability to compare/cross reference data across multiple rows. If this task might be better suited to do directly in ChatGPT or Claude please let me know. Open to any ideas. "When it comes to the formula column, this is very unusual and have not seen anything like it before. Do you mind saving this formula column so that I can take a look?" - The formula column has now been saved in the table.
Thanks for the additional context Ben! When it comes to identifying aliases or emails that are similar and belong to the same person, our best bet would be using a unique identifier like LI Url which would be associated with these email ids. I am assuming if they are duplicates, the associated LI Profile would be the same. Or any other identifier like Account ID or Object ID could also work. Do keep in mind though, once we do de dupe, it will remove whatever comes second in the table. What I basically mean is you won't be able to choose which email id to keep on de duping. Taking a look at the formula column!
For the formula column I can see you have not referenced the columns properly:
Doing so for all inputs should solve the issue. Let me know if it persists even after that!
Thanks so much for the guided walkthrough - I converted the inputs and the preview is still the same. Column is saved within the table.
Hey Ben! Thanks for flagging this. It looks like a UI bug to me. Good thing is the column formula is successfully being applied to all the rows. I am going to file a bug report for this and will keep you posted!
Thanks Sayli - Re: "our best bet would be using a unique identifier like LI Url which would be associated with these email ids." - Great idea. I wouldn't want to run a de dupe though since the action removes things from our table. Could I just create a formula to tell me any duplicate or similar values that exist in a particular column?
