A piece of customer feedback or support ticket. Each piece of feedback or ticket entry is considered one data point, regardless of length. The below is an example of a data point:
I find the boards feature to be extremely helpful in organizing my time throughout my day. It saves me time and makes daily tasks much more manageable.
A data point ingested into Viable from one of the integrated apps that’s been labeled and segmented. It’s ready for analysis in Viable.
In our documentation and tutorials we’ll mostly refer to the data available in Viable; we’ll use data point to refer to a processed data point unless otherwise specified.
Customer feedback tools or channels that have been integrated or are being considered for integration into Viable in the future. Intercom and Zendesk are examples of such apps. An integrated app is one that is set up to send data to Viable for processing.
This is where the magic happens! A lot of it anyway. This field appears at the top of the Feedback section. Type a question into this box in plain language and a response will be generated beneath it.
Last Updated: 12/02/20
Viable adheres to best practice standards for ingesting, handling and protecting data as well as responding to vulnerabilities or incidents. Our goal is to ensure a high level of security for our customer data as well as our own. PostgreSQL, with AES-256 at rest encryption. Hasura is what we use to …
Typeform Zap for Viable
You can analyze customer feedback collected via Typeform by connecting Typeform to Viable via Zapier. Under Set up action choose the fields you want to analyze. We recommend you set up a separate Zap for each free text question/response. (We do not recommend setting up a Zap for multiple choice or …
Twitter Zap for Viable
You can analyze customer feedback from tweets by connecting Twitter to Viable via Zapier. Under Set up action choose the fields you want to analyze: You should be ready to turn on the Zap.