This feature is in active development and is currently only available to beta testers. This page may not reflect the latest changes.
Golden Records represent the best information you have about an individual, pulled from multiple data sources. This data can be synced into your CRM so that the best data is available where you need it most.
To configure or review CRM Sync, open the Golden Record Management tab, then click the "Sync to CRM" step at the top. Once CRM Sync is enabled, it runs nightly (following the nightly update of Golden Records).
Warning: If you edit a contact record directly in your CRM, your changes may be overwritten during the next Golden Record sync. To avoid this, ensure that your Helix data sources include your CRM and that your tiebreaker rules prioritize "Received On" (Descending) or "Source" (CRM).
The Sync to CRM page provides several settings you can configure, described below. Click the Save button when finished.
Caution: Once data is synced into the CRM, it won't be removed or undone if you change these settings later. All Golden Record data previously synced to your CRM will remain there until overwritten during a future sync or changed directly in the CRM (either manually or by other software you use).
Choose CRM Data Source
Select the Helix display name of the data source which is your CRM. Helix will use the associated record IDs to identify which records to sync. The data source names are customizable and some organizations have more than one CRM (for example, a decommissioned one that still contains historical data) so Helix doesn't attempt to guess which data source to use.
Sync Golden Records
You can select a specific audience to sync data for. If this is left blank, Helix will sync all Golden Records into CRM—however, depending on your data, this could create a large number of incomplete contacts and use an excessive amount of CRM system storage. We strongly recommend configuring an audience for this purpose.
Note: If Enable Sync is turned on and you change the selected audience, a sync will begin immediately after saving the change. You won't have to wait for the overnight sync.
Because an organization can have multiple ticketing systems, Helix needs to know which specific source a ticketing ID number is tied to. In the first box, select the Helix display name of the data source that is your ticketing database. In the second box, select the database name as used in your CRM's KORE Ticketing module.
If you have more than one ticketing system—even if they are provided by the same vendor—use the + (plus) icon to add another line. Use the trashcan icon to remove a line if necessary.
Sync Data Elements to CRM
Here, map Golden Record fields to their corresponding CRM fields. You can choose which Golden Record fields to sync into CRM; it doesn't have to be all of them. You can also map Tags and Attributes to custom fields in your CRM—the name of the Tag or Attribute will be copied into the CRM field. Use the + (plus sign) to add additional lines or the trash icon to remove a line.
You can change these mappings later. However, deleting a mapping will not remove data already synced to the associated CRM field.
Only use this slider when you're certain that you're ready to begin syncing. We strongly recommend reviewing many Golden Records and the list of audience members before enabling the sync. Although you can turn the sync off later, syncing cannot be undone.
CRM Sync History (logs)
Once the sync is configured, you can view a log of transactions. Click the CRM Sync History button.
Use the tools in the top right to choose which transactions to see. The dropdown list allows you to filter it by successful or failed transactions. Use the search box to find a specific Golden Record ID or source CRM ID to investigate a particular record.
If there have been any failures, use the Bulk Re-Sync button to retry. If you continue to see failures, use the copy icon to copy the details to your clipboard. This may help you identify the problem. If you need to open a support ticket, be sure to include these details.
Merge Review (duplicate CRM contacts)
During a sync, Helix may discover cases where an individual has more than one contact record in your CRM. Helix cannot identify which one of the CRM contacts should be considered the "main" one. (Helix tiebreakers can identify the best contact information, but there could be active sales opportunities open for the CRM contact which has less in common with the Golden Record, for example.)
Helix can help you manually merge these CRM contacts. Click the Merge Review button to view a list of Golden Records with more than one source record from your CRM. Click a row to view the CRM IDs connected to the Golden Record. Here, you can select which (if any) of the CRM records to merge together. You can also click the column layout icon to choose which fields to display in this view.
Select a merge target to identify which CRM ID will be kept; data from the others will be merged into it. (The Golden Record sync will update the contact details after merging.) Once you've selected a merge target and at least one other record, the Merge button will be available. When you click it, Helix will use the CRM's merge functionality for you. (CRMs only allow merging two records at a time; if you chose more than one record to merge into the target, Helix will perform multiple merge operations for you.)
Note: When you merge CRM contacts, Helix immediately copies the Golden Record details into the merge target CRM record instead of waiting for the next sync.
If for any reason you don't want to merge one of the records, you can mark it and click the Ignore button to prevent it from being flagged again (starting with the next sync). After doing so, it will not show up in the Merge Center again unless there is another duplicate record. (In that case, this record will have an "Ignore" status to indicate you've already handled it.)
Note: When Helix finds duplicate CRM contacts, it will only sync the Golden Record to the merge target. If no merge target has been selected, that Golden Record will not be synced to CRM during that sync.