Hi!
I got an interesting use case (at least it is interesting to me) because I have 2 different call centers that want to keep their own Salesforce orgs, but work each others cases. My first thought was Salesforce 2 Salesforce, but that seems to be headed towards sunset if not there already.
My question is with Salesforce Connect and Org Adapter aspect of things does my use case fit for Salesforce Connect or should I be looking elsewhere? The call centers are high volume and 24/7 based so I ideally want to figure out if I'm barking up the right tree here.
Appreciate any input or validation to this.
Thanks.
Jeff
There will be latency with the connect, and I'd still be worried that there would be duplicated work or confusion.
From an architects perspective, just because they want to keep their orgs, isn't a good enough reason to build out a process like you're trying.
Dig into why they want to keep their orgs and why they need to work each others cases. I suspect there is a middle ground to either bring them into the same org with same processes OR they work as individual orgs (unless there is a huge difference in processes OR data residency issues, I'd be leaning towards same org)
