I cant speak for Nick, but I do have some answers to your questions, Toby.  I also have a strong opinion on one of them as well, but I promise to be as delicate as I can with delivering it.  You know I have nothing but love for you, so forgive me if any of this comes across like a sledgehammer... First, the quick and easy response to the question about 'frequency'.  To wit, who do you serve the survey to (authenticated users only or all Visitors), when do you serve it, and where do you serve it?  I am a big believer in serving the survey to all Visitors (both anonymous and those who are authenticated / logged-in).  I have come across some customers that are extremely stringent and conservative when calculating the value of a deflection, and so they demand that anybody who gets a satisfied answer on the community and does not have to open a ticket has to be authenticated on the community before they count the deflection.  I think this sort of demand is a bit short-sighted (and it is certainly a thumb in the eye to what Richard Nixon called the 'silent majority' of people out there), but it may be just a cultural artifact within the business on how to measure things.   Regarding where the survey is served, I think a Community Manager should be both prudent and surgical with the survey's deployment.  Meaning, it should only pop on boards where there are people potentially solving problems / getting answers.  I will admit to getting flustered when I see the survey popping in the 'watercooler' area of a Community, or even in the 'getting started' or 'welcome' area of the Community.  It just seems like a lack of attention to detail on the Community Manager's part when thinking about the digital customer experience. Now, onto the crux of your specific question around 'when' the survey is served.  The frequency should be no earlier than 2 minutes and no more than 5 minutes.  Considering that a person is most likely coming from a search engine and landing right on the thread with their solution (or, at the very least, a discussion around their problem), 2-3 minutes should be all that they need to discover the solution to their problem.  However, if it is a B2B high-tech community where the answers tend to be a bit more complicated (and the conversations a bit more detailed), I think 4-5 minutes is the proper time.  There are always exceptions to these suggestions (i.e. - people who read more slowly than the national average, people that are distracted by other things on the page, people that are being distracted at home while trying to research this stuff, etc), and so no frequency rate is perfect.  But those are the best practices we have around frequency. In regards to changing the template and/or the Customer Experience questions.  There is very little room for change.  I think there are some unorthodox hacks and also maybe some slight adjustments around industry / product wording, but by and large, there is little flexibility to alter the questions.  And I am extremely happy about this! ....Ok, let me clarify that last provocative sentence above with the strong opinion I mentioned at the beginning. I'll start by quoting Mr. Spock from Star Trek II: The Wrath of Khan.  "The needs of the many outweigh the needs of the few....or the one".  As a red-blooded American, that sounds like commie malarkey to me, but as somebody who has worked with our customers for 13+ years and lived neck-deep in the data, Spock's philosophy really does need to be applied here.  The larger Khoros team needs to be able to tell customers, with confidence, what they should aspire to when it comes to performance.  The only way you get there is by having an unflinching and inflexible survey methodology.  Sad but true.  Doctors must struggle with a similar thing when patients want to be cleared too early from an injury or want to be discharged from a hospital too early.  There is an instinct to make people happy as well as an urge to satisfy them.  However, there is also a standard to keep in order for the science, data, and message to cleanly flourish.  I have written before about the inflexibility around our Value Analytics survey elsewhere in this community and have spoken about it with many Khoros customers, on-site, at their offices.  Nobody likes being limited with what the questions and choices for answers can be, but everybody LOVES the confidence we have when it comes to telling them what the Resolution Rate of their Community should approximately be in Year 2 if they are a B2C High Tech company (or Year 1 if they are a Retail Community, or Year 3 if they are a B2B High Tech Community, etc).  If we allow everybody to change the questions and/or answers, now we no longer have that confidence....much less the data to speak with any real level of insight. It may be a gigantic letdown to have to accept this, but I believe it would be worse to be stumbling around in the dark not knowing how your Community 'should be' performing against similar Communities in the same industry (B2C high tech, B2B high tech, CSP, Retail, Financial Services, etc) with the same audience (B2B, B2C, Internal, etc), and a similar age (Year 1, Year 2, Year 3, etc).  So the ability to modify both questions and answers in the survey is hampered only by the needs of the many outweighing the needs of the few. ... View more

And     ^ THIS ^    is why KrisS leads the league in Accepted Solutions, ladies and gentlemen!   A stunning repository of knowledge!  Wow. ... View more

A perfectly legitimate request / question, but I do not recall ever coming across it before. As most people now the feature to 'close' one's account is found in the My Setting section: Personal > Close Account > [hit the 'close account' button] If you have single-sign-on (SSO) for your community, I am not sure how this behaves at all.  But if you do not have single-sign-on, I do not even know how this really works anyway (are you banning yourself, etc?).  If it is a ban, then 'yes', you can run reports on that.  But because I am not precisely sure what happens, then I do not know if you can run a report on it. Sending up a bat-signal for some of the old-guard that might know the details about what happens...and if you can run a report on it (which I doubt). @MarkS  @AdamN  @AubreyL @LarryI @KrisS  ... View more