100%!
This was one of the potential problems we flagged during onboarding.
Going one step further, it would be great if we can have a view with all insights associated with more than one record (Company person >1) where we can either “confirm” the entry as valid to that customer or reparent to the correct one
FYI @Molly.McQ
@heather_hansen are you able to do that by editing the domain settings for the customer account? We also work with partners/distributors and have had that issue.
Because of the fact that they can work with multiple customers, we’ve removed their email domains from each customer record and will be treating each as their own company.
I could imagine benefits one way or the other with this though.
@ajprince yes - but they just get added back because they are still associated as Related Contacts in SFDC (and thus the company in Gainsight).
Heather beat me to it! It’s the same for us
Hi team, my recommendation would be to run through the data hygiene on CRM/CSP so that insight aren’t incorrectly assigned - let’s solve for the root of the issue rather than the symptom! :)
@StairKate Could you please elaborate on what you mean?
Hi team, my recommendation would be to run through the data hygiene on CRM/CSP so that insight aren’t incorrectly assigned - let’s solve for the root of the issue rather than the symptom! :)
In case it wasn’t clear, the issue isn't a misalignment of contacts with the wrong Company; rather, the same contact is (correctly) associated with multiple Company records; a many-to-one relationship between Company Person and Person.
Ah, I see. Yes, in those cases, you may see some comms mis-routed if there aren’t enough unique stakeholders on the comm for Staircase to match with certainty to the right parent account. Where ever possible, try to ensure at least 1-2 unique stakeholders are on the comm for better routing.
Typically, we recommend rolling up just to the parent for these types of accounts but if you need the child level breakdown, we’ll have to have some level of acceptance for mis-routed comms. We don’t currently have a mechanism to re-route them in the UI.
Appreciate the clarification!