Skip to main content
Redhat has two instances of Gainsight now -- Support (Primary, and is the first instance) and Sales (Secondary, and is the second instance.. They will be running CS out of both, with some overlap of accounts in each. 



There is one specific requirement to run all survey communication out of the primary instance (was decided by RH tech team) but comes down to having already spent lots of time implementing surveys in primary only. They want the ability to nominate contacts in Secondary and have that write back to primary (either creating the contact if it doesn't exist, or update a field if it does) to show that a survey needs to be sent to that contact. Currently they plan to write a web service that does this as a one way sync from Secondary -> Primary. We could use bionic rules to do this, and have less work for the team (it seems like it would be simpler too). As an additional req, the would like to pass account information for these nominated contacts which is out of scope for their tech team and they don't want to do it as of now. Bionic rules also seems to be able to solve this. 



As a higher level idea, being able to have a "bi directional" sync between the two orgs, allowing them to pass data between the two would solve lots of the heavy lifting that we have had to do to. Even if it is not real time, being able to schedule a daily sync would be great.
Very curious in the future how a Gainsight "person" record in MDA could play into a scenario like this.

Could we become the primary for any contact related records fed from multiple instances with a GSpersonID and simplify mapping/duplicates/etc.?

Reply