What is it?
Within CRM Export Settings, we can configure how net new records should sync to your CRM.
Record Sync Settings
Always create Lead
After identifying a new record, you can choose to have UserGems always create a Lead. We would then leave it to your team or automation to decide whether to convert the Lead into a Contact and relate it to an Account.
This option is common for LeanData / RingLead customers, or those who already have advanced routing & conversion rules in place that they would like UserGems to sit on top of.
Create Contact & Account
This option relies on UserGems to match a new Contact that we deliver to an existing Account if we detect one in your Salesforce based on things like domain matching and fuzzy-logic company name matching.
This option is common for customers without advanced routing tools in place who do not want to use Leads for new UserGems Contacts. If no existing Account is matched, UserGems would create a new Account in your Salesforce and assign it to a default user that you can configure within UserGems.
Create Contact if Account exists, otherwise Lead
This hybrid option is common for customers without advanced routing & conversion rules in place who would like to rely on UserGems to match a new Contact to an existing Account if one is detected in your Salesforce based on UserGems' matching rules. If no existing Account is matched, instead of creating a new Account, UserGems would instead create a new Lead for your team or automation to review/qualify and convert.
We will only create records after scanning your database and assuring we will not be creating a duplicate record. If you already have this lead/contact in your Salesforce at their new company, we will just enrich that record instead of creating a new one.
If you are utilizing either "Always create Contact & Account" or "Create Contact if Account exists, otherwise Lead", you will be relying on UserGems for the account matching in Salesforce. Here is the logic that UserGems uses for that matching:
Default Ownership
Decide who should own net new leads and contacts at the moment they are created. Most of the time, UG workflows or a routing solution you may already have in place would pick these up after creation to do the more intentional and final routing.
- Default Owner - This user would own all new leads/contacts where we cannot match an existing account owner (or if ownership alignment setting below is left unchecked).
- If Account Exists, assign Account [Owner] as Lead/Contact Owner - if checked, we will assign the new lead/contact to the owner field selected in the drop down. If this user is inactive or unassigned, we will fall back to the Default Owner.
- If current Lead or Contact already exists, reassign Owner - if checked, we will follow the ownership rules defined here for job changes you may have already captured at their new company
Custom Field Mappings
Based on your record creation settings, mappings will be suggested for each relevant object. Some important notes:
- You can add/change/remove mappings any time.
- The "CRM Field" column shows the fields we will update in your Salesforce, while the "Header Title" column on the right displays the data we will populate that with from UserGems
- There are 2 types of updates; referenced by the middle column:
- Static: same update on all records (i.e. checkbox or lead source)
- Dynamic: custom data for each record
- There are 3 checkbox settings for each mapping:
- Create: we would update this field only if/when creating a new record of this object
- Update: we would update this field upon sending a job change if the record already exists (overwriting any value in the field)
- Only if Empty: we would update this field upon sending a job change if the record already exists and the field is blank previously