Can someone please explain what is breaking?

👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!

Hi Garrett, thanks for reaching out. Can you add some context on what you're facing issues with here? Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1728057600&signature=54a5105f9b669e530925a49af588657307d6dc6df0cd0ee2a04d94384f626554&req=dSEgF85%2FmohWX%2FMW1HO4zYTywCP8A5AQ2BKsam%2FhVPvt2A%3D%3D%0A

https://app.clay.com/workspaces/362911/tables/t_UhjKJFp5zjxv/views/gv_zmE4o55czYEU

Would you mind if we hop on a live video/huddle? I think it would be much easier to explain

Unfortunately we don't have the capabilities to do that at the moment. You can send through a recording of your issue (f.e. Loom) or book a call with our support team here- https://meetings.hubspot.com/meet-clay/cx-support-call

Okay I'll quickly make a loom

Please let me know if you have any questions

Taking a look at the loom now, thanks Garret.

Okay, let me know what you think please

Hey Bruno any update here?

Hi Garret, still investigating this - will be able to give you an update soon.

The issue here seems to be related to the search parameters you're using. You're liming your search for CEOs - which can be a tricky profile to target, depending on what companies fit your ICP. Results from the people search typically get impacted by the following instances: 1. Inputting semantic search parameter instead of syntactic search: A limited set of job title keywords applied to the role being targeted. Our search algorithms are based on syntactic search which means you must put every variation of the keywords you're looking for (ie CEO and Chief Executive Officer). When this happens, some matching profiles may be missed because they were not included in the search query. Can you share a bit more info job titles you're searching for? It'll help to include a variety of keywords related to those titles. For example, including other keywords related to sustainability such as ESG, CSR, Corporate Social Responsibility. For Digital Product Passport, it could be keywords like Product compliance or digital asset management. ​ ​2. Mapping the wrong inputs in the people filters. For example, not mapping LinkedIn urls from the company table to run the search. ​ 3. Search limits applied to the people search. This reduces the number of records that can be imported from a search. ​ 4. Private profiles: Our data providers use a multitude of ways to access people and company data. For the most part though, we don't use your cookie/login data. This means that we could miss some information here and there, especially if there are privacy restrictions in place for certain profiles. This would mean that your logged in profile has access to it, but our data providers may not. However, we're continuously working on improving our search algorithm to provide more coverage. I'd suggest adjusting your people search parameters following the guidelines I have provided above, possibly keeping a broader breadth of seniorities into consideration.

Thanks but this didn't really answer my question. The core of it is around why they aren't automatically populating in the find people sheet when I put in a new domain in the company sheet

In other words, even when I CAN find the CEO, it doesn't populate across tables automatically

Does that make sense?

Hi Garret, I do see what you mean here. It looks like we've got a bug on our hands - I've escalated this over to our engineering team and we'll let you know as soon as we know more!

I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To provide insight on expectations, issues like this may not be actioned for some weeks. This timeline is based on the team's current existing log of issues and upcoming feature releases which is subject to change. So what happens now? Now that your issue has been logged, I will wrap up this conversation. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?

Nope! Thanks