Hey, what's the best practice to ensure the same company is used to fill information for all columns in the original finding companies? For example, my initial search found the company Peacocks, the provided description and LinkedIn url match the company whose url would be peacocks.co.uk but the domain field is populated by peacocks.com.bd and when I use a claygent to find more information using the company name and domain it finds information but for a company whose website is peacocks.net so quite inconsistent across the board and not following instructions
💤 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!
No I want to make sure that the original information input by clay when I pull a list is consistent across all columns so that the company described in the description matches the company in the LinkedIn URL and is the same company referenced in the domain column. Right now, they don't match
If you look at my TEST workspace, row 3 in the companies table
I see the issue here, thanks for clarifying this. Could you add a few examples from this table where the retrieved domain does not match the company you're performing the search on? I'll report this internally. In the meantime, as a workaround, I suggest running Claygent to retrieve company domains, by inputting the company name and description - I set up an example prompt in your workspace to address this.
Thanks! Row 16 is also exhibiting the same issues
Row 19 as well
Great - reporting this over to the team. I set up a Claygent column to help fill those domains in in the meantime. We'll let you know as soon as we know more!
Hello there! Happy to report that we heard back from the team and this issue should be fixed. The domain quality issues should be resolved if you kick off a people or company search with the same parameters as your previous search. Thank you for your patience, feel free to try again and let us know if the problem has been resolved on your end.
