Home > DupeBlocker for the End User

DupeBlocker for the End User

Now that DupeBlocker has been installed and configured, end users need to be notified of the changes that will be seen in Salesforce as Accounts, Contacts and or Leads are inserted or updated.

In an effort to facilitate user adoption of this new software, a sample introduction letter has been developed that can be customized based on the specific configuration choices, and ultimately sent to the Salesforce end users.

The Sample Introduction Letter can be found in Sample Introduction Letter.

Things to consider when customizing the letter:

• Will Tasks be generated for warnings?  And who will the Tasks be assigned to?

• Private or public sharing model?  And, if private is "Bypass Security" checked?

If "Bypass Security" is checked, but Salesforce sharing is implemented, it is recommended that warning tasks be assigned to the "Scenario Owner" as the user may not be able to merge potential duplicates based on their specific sharing rules.

• Will duplicates be blocked, redirected or just reported?  Will the action vary by scenario?

• Will users be allowed to delete Warnings?

If a warning is generated and the user does not wish to merge/convert the potential duplicates, only the DupeBlocker Administrator will be able to delete the warning.  Access can be granted to users to delete warnings, but this could defeat the purpose of DupeBlocker (user chooses to ignore the warning, but the record is in fact a duplicate and should be merged/converted).  Since this can be done based on the specific profile, this option could be enabled for managers but not for general users.

See also