Announcement

Collapse

Information Needed

See more
See less

Temporary Contact question

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Temporary Contact question

    I am wondering if you have advice on getting a specific result from the contact matching options that exist currently in SF.
    I understand that Fully automatic will either create a new contact or match to an existing IF all match fields are an exact match.
    And Manual will always create a Temp Contact even if fields DO match exactly.
    And Semi will create a Temp UNLESS it matches perfectly to an existing contact.

    I have a client who is looking for a setup where:
    -If there is an exact match to the matching criteria, match to that existing contact,
    - if there is NO match to ANY matching field, create a new contact,
    -and if there is a match to SOME but not ALL matching criteria, create a Temp contact. So every Temp would have at least one potential match to choose from

    Is this possible either through your existing options or some workaround in SF? And if not, could this be a potential option for the future? Thanks for any advice on this.

  • #2
    Good day @chad@percolatorconsulting.com

    That is how it works with the current system. At temporary contacts, you will see the existing potential contact list based on "LastName AND Email" or "LastName" OR "Email", the maximum records display is 20 records.

    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      Thank you for your response. But currently, what I'm also seeing besides the scenario you described is: if there is no match on any field, a temporary contact is created. What I'm hoping the system will do is: if there is no match on any field, I want the system to automatically create a new contact, not create a temporary contact. I only want to see a temporary contact when there is a partial match. But currently I'm seeing temporary contacts with no list of potential matches.

      Comment


      • #4
        What mode are you currently using?

        Are you available to join Live Support today? Actually seeing the specifics in cases like this is helpful in explaining why a match failed or not.

        http://help.clickandpledge.com/custo...n-live-support

        ~ Amanda
        Customer Advocate, Live Support
        Regards,
        Click & Pledge Support Department

        On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          Amanda, thanks for your help yesterday! I don't know where the best place for feature requests is, but i'd like to offer up my use case as a feature request: A fourth mode for contact matching that creates a temporary contact if some but not all match fields are matched to an existing contact, but creates a new contact automatically if NO fields match. I realize this has cons like creating dups unnecessarily, and possibly other things I haven't thought through. But considering that the other modes have cons as well (fully automatic creating dups) it still seems a worthy option for clients to choose from, depending on their unique situation, as long as the consequences are explained for each option. It's a good potential compromise between fully and semi. No need to respond, just wanted to put it out there. thanks again.

          Comment

          Working...
          X