• Customer voice survey ID conventional number sequence

    Wish we future feature the option to visualize a survey conventional ID e.g. CS-01, CS-02, etc.. not easily visualizing conventional number sequence when a survey master record has been created, user may not have master data consistency record creation.
  • Customer voice survey design pipe data for product transactions

    Currently there is Pipe data for variables for (product, customer, service, location, date and time, user, other1, other2), however there is no option to potentially easily insert and identify from product transaction number, customer transaction or customer facilities visit date, transaction type.
  • Customer voice enhanced answer to include tip text message

    Future featuring the option to include answer tip text message with the option to be disclose-display to the end user maybe helpful (e.g. technical questions or technical service references). Not featuring answer tip text message either at mouse pointer or as additional tip text message section, user may potentially compose long answers on certain type of level questions.
  • Customer voice design enroute action option to redirect to a specific survey question or range of questions

    Currently there is the option to enroute a question to an alternative question or answer through the different actions and conditions, HOWEVER, there is no option to enroute (Skip to, go to question number, continue survey questions from to). Featuring additional flexibility conditions and actions on enrouted questions, user may potentially have alternative options when designing the customer survey.
  • Customer voice design option to visualize deleted designed questions and answers

    Wish there is the option to easily visualize designed deleted questions and/or answers. Not having the option to easily visualized potential deleted survey designed questions and/or answers, user may not easily identify, track back, review, re-plan, re-assess questionnaire design before publishing. Featuring the option to visualize deleted survey design questions and/or answers, user may potentially save time from composing survey questionnaire.
  • Customer survey pipe data for age

    Future featuring the age from pipe data available variables, maybe potentially nice to future feature. Not featuring age as a pipe data, user may not potentially easily generate dashboard (based on race and age). Note: Potential rage and age, may not be a compliance collection type of data, however, in some statistic type of questionnaire events, or type of data, maybe nice to feature.
  • Customer voice design pipe data for gender

    Future featuring the inclusion of gender, maybe nice to include and potentially collect or anonymously collect for the purpose to visualize statistical dashboard generation. Not featuring gender, the user could potentially alternative use the "other1" or "other2" pipe data collection variable. Featuring a specified pipe data for gender, maybe nice to feature for statistical purposes across all surveys.
  • Customer voice system dashboard for survey submission date and time

    Featuring a system dashboard based on survey submission date and time, maybe nice to feature, for purpose to potentially better future distribution planning. Not featuring a system dashboard by survey submission date and time, user may not easily improve survey distributions for scheduled time and date (s).
  • Customer voice distribution with allocation schedule by date and time

    Future featuring customer voice distribution with allocation targets by scheduled date and time, maybe nice to feature. Not featuring survey distribution of allocating records-targets by date and time within a certain period time range. user may not easily visualize and/or control potential statistics of submission by date or times, or days of the week or the month.
  • Customer voice survey content search filtering by questions and answers

    Future featuring the option to easily search survey content (composed questions, answers), maybe helpful after having multiple questionnaires, the content search maybe potentially difficult to search, filter or find for purpose of advanced planning, comparison or to easily visualize charts.. Currently the user has to conventionally locate the question, go to the survey and identify the chart, INSTEAD of searching content, and easily visualizing chart associated with that question or survey.