Every once in a while, RingLead is asked to do something it is unaccustomed to; create duplicates. This can be for various reasons. A customer may have a specific product where they consider every single hit an opportunity. In these cases, they usually want these records forced through their sales pipeline.
Recently, a RingLead customer wanted to create duplicates in some cases, and dedupe in others. They needed any incoming web form with the Lead Source “EULFC” to only dedupe against Leads from other sources. If another Lead already existed in Salesforce with the Lead Source “EULFC,” they wanted to create a duplicate. If RingLead found a match and the Lead status was not “EULFC”, they wanted to overwrite the Lead Status with “EULFC”.
Using the allow duplicates feature developed by RingLead, we were able to do this using a formula field. The allow duplicates feature is very simple, but can be powerful when combined with Salesforce logic.
This Declone Web-to-Lead feature allows customers to choose a single field to determine if a duplicate should be created or not. If the field value submitted in the web form DOES NOT match the value in Salesforce for this field, a duplicate WILL be created. To set this up, the user just needs to enter the field’s API name into their Declone Web-to-Lead configuration page.
In this customer’s case, the formula field’s name was “RingLead Create Duplicate,” with an API field name of RL_Create_Duplicate__c, and they only wanted it triggered for Leads. This field is only visible to his RingLead user, and not added to any page layouts, so his users aren’t even aware of it. The formula was:
CASE(LeadSource, "EULFC", "TRUE", "FALSE")
This means that if the value of LeadSource is EULFC, this field is equal to TRUE. Otherwise, this field is false.
Next, we had him add a hidden field to his website:
<input name=”RL_Create_Duplicate__c” value=”FALSE”>
When a user submits a form, we only dedupe against records that have a value of “FALSE” for the field “RL Create Duplicate.” Any other record is ignored. The end result is we will dedupe as normal unless the Lead source of a record is EULFC, in which case we’ll create a record.
Comments