Skip to main content
andrew_cummins
andrew_cummins
Helper ⭐️
August 19, 2016
New Idea

Ability to survey randomly

  • August 19, 2016
  • 7 replies
  • 80 views
It would be awesome to tell a powerlist to select 75% of the users and contacts randomly and survey them. This helps to prevent Gaming of the system for some surveys. Right now we have to set up a few powerlists based off an account attribute like account name starts with A-M survey the primary contact and account name starts with N-Z survey the secondary contact. Then we have to go in and change this on a quarterly basis if we want to adjust the "random" nature of the survey. 

      7 replies

      andrew_cummins
      andrew_cumminsAuthor
      Helper ⭐️
      August 19, 2016
      It doesn't have to be 75% it can be any percent but the ability to choose how many to randomly survey is the idea. 
      karl_rumelhart
      karl_rumelhart
      Expert ⭐️
      August 19, 2016
      This is a very cool idea, Andrew.  Will think about it. 
      andy_sackley
      andy_sackley
      Helper ⭐️
      August 22, 2016
      Added my vote. Would be especially useful for support surveys - particularly as case volume grows and you do not need to hit every case closed to get a valid sample size!
      gaurav_kotak
      gaurav_kotak
      Expert ⭐️
      August 25, 2016
      Great idea Andrew. Instead of relying on alphabets, do you think you can create a SFDC formulae field to capture the randomness? 
      andrew_cummins
      andrew_cumminsAuthor
      Helper ⭐️
      August 26, 2016
      Have not explored that but if
      requires a SF Admin I am unable to do it and would have submit it to my SD
      admin team. It would be great if we could have this flexibility in Gainsight so
      I do not need my SF Admins

        gaurav_kotak
        gaurav_kotak
        Expert ⭐️
        August 26, 2016
        Got it. Yes you'd require SF admin to do it. This is currently planned functionality at least for Q4. Next year we'd want to look at A/B testing more broadly and that should have tenets of randomization so we'll look to directly address this use case as part of that initiative. 
        alizee
        alizee
        VIP ⭐️⭐️⭐️⭐️⭐️
        March 28, 2023

        @anirbandutta Can you shed some light on this one? I see that’s 6 years old with a mention that it was planned for Q4 six years ago? Where are we with this and who can we talk to about it?

        The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
        Terms & ConditionsAccessibility statement