If you are adding contacts to the Person section of C360, you need to set up a rule to load to SFDC to make this happen, it is not automatic. If you are logging in via SFDC and adding contacts to a related list based on native SFDC Contact data, you’re actually already creating them in Salesforce and no sync is needed. Hope that makes sense.

@MelissaC , good question.

The answer is No, a Person created in Gainsight will not automatically be written to SFDC as a Contact. Many GS Admins handle that via a Bionic rule. 

Here’s a robust thread on how some GS Admins handle this, and also some of the caveats to navigate as you go.

@matthew_lind Would it create a duplicate if a CSM added contact in GS first, then decided to add to SFDC?

Thanks!

@TMaier What would the rule look like if I decided to set it up that way?  Could you send me snaps of what the actual rule itself would look like built?

Thanks!

This is a very real possibility that should be accounted for in your processes, and then subsequently in your Gainsight/SFDC configuration. Some instances update Contacts in SFDC (syncing to Gainsight) and some teams update Persons in Gainsight (syncing to SFDC), with more teams likely updating in SFDC with a sync into Gainsight.

Of importance when it comes to duplicates is configuring the identifiers well. The identifiers signal when a new record should be created (because the identifier(s) aren’t found in the destination dataset) or when an existing record should be updated (because the identifier(s) are found in the destination dataset). In that latter case, you configure the system not to create a new and potentially duplicate record, but instead to update an existing record that’s already there.

More here on how to write to SFDC, and this article happens to use Person / Contact as its example.

https://support.gainsight.com/Gainsight_NXT/03Rules_Engine/03Set_Up_Rule_Action_Types/Configure_Load_to_SFDC_Objects_Action_Type