Clay Icon

Best Practices for CRM Deduplication Using Clay and AI

·
·

Hi all! What’s the best practices regarding CRM deduplication using Clay? Have there been tests done to deduplicate using AI / Claygent on top of the CRM database? Thanks!

  • Avatar of Paddy O.
    Paddy O.
    ·
    ·

    following

  • Avatar of Julius H.
    Julius H.
    ·
    ·
    1. 1.

      Clay as middleware, i.e. inbounds, lead lists are first pushed to Clay to enrich on key data points (incl. enrichment data points like domain)

    2. 2.

      SFDC instance has many 50k+ records, that I’ll also enrich on the given data points.

    3. 3.

      Pre-SFDC upload, I’d ideally want to deduplicate on the existing SF data in order to not create duplicate accounts/leads.

    What are the ways how this has been solved? I imagine this is a good AI-use-case, and wondering whether that has been tried?

  • Avatar of Julius H.
    Julius H.
    ·
    ·

    Maybe the answer isn’t Claygent but some other tool/integration?

  • Avatar of Julius H.
    Julius H.
    ·
    ·

    Or the answer is reworking the SF-internal deduplication logic?

  • Avatar of Channeled
    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!

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Hi Julius H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Thank you so much for sharing your feedback Julius H.!

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Hi Julius H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Thank you so much for sharing your feedback Julius H.!