SummaryWhat is the best way to configure and test CoBrowse before going to production?
My agency management has licensed CoBrowse but has not decided to implement it yet. They want to see a test site configured with CoBrowse so it can be demonstrated to them and a group of our agents. Then if it is approved, we will deploy it to production. I noticed in the documentation that we are supposed to create instances in Production then clone production to a test site to get coBrowse on the test site. I also saw other documentation that said I could file an SR to have CoBrowse activated on a test environment when it isn't in