v5.5 Survey Text Analytics - only for NPS comments?

Only for NPS comments at this time.  Clearly we will want to extend it for other surveys with heavy text response but this is our 'crawl' stage. 

We use a separate question to gather NPS comments -- not the NPS question's Comments field -- because we are not able to set that Comments field to Required. In order to get those comments to be visible in the C360, I use DataLoader after the survey is closed to insert them into JBCXM__SurveyResponse__c.JBCXM__NPSComment__c.

It was not clear to me from the text analytics support article whether those comments would be captured by text analytics. Does the once-every-24-hours text analytics process [i]only look at records that were [i]created in JBCXM__SurveyResponse__c within the past 24 hours, or would the text analytics pick up the comments that I had [i]inserted into [i]existing records created more than 24 hours ago?

Hey Seth, 

We turned on NPS Text Analysis and I noticed it went back and did the analysis on some past surveys.

I think the big disconnect here is that while NPS is really one question, when many of us run an NPS Survey there are other questions included.

We were very excited to use the Text Analysis, and then we realized it was limited to one field.

Maybe we can concatenate the text fields and push them into the NPS Comment field to bypass this, but that is not ideal.

Killa! Thanks for the heads up.

Although I guess my question is, now that it's turned on, if you were to edit the text in those records in the future, would they be [i]re-analyzed... :-/ [i]That's [i]really unfortunately the crux of my use case. But it's great to know that historical data gets pulled in when it's turned on for the first time.

Hi Gainsight Product, Since text analytics is currently only available on NPS question comments (and back to one of Seth & Lane's original request), can we please provide an option to set the NPS question comments field to required?  Thanks!  

My only concern with that approach is whether or not making the NPS text comments mandatory will reduce the number of responses you'll get. 

I think having the ability to make it mandatory is what Seth is asking for. We're not asking for it to by default be mandatory.

I understand that distinction in the request. Makes sense to have options. It just comes with the understanding that if you make text fields mandatory, you'll almost surely be sacrificing the number of responses you'll get.

Here's a good blog post on that topic: https://zapier.com/blog/nps-net-promoter-score/
"With each added click or question, your chances of someone opting out of a survey drop 50%."