• Customer voice survey distribution by visual state map selection for within zip code ranges

    Future featuring survey distribution by a dynamic state map selection within state or city zip code ranges, maybe ideal. Not featuring distribution by visual state or city map, user may potentially conventionally process distribution by each location or each location conventional range or range of zip codes that may compose the city or state.
  • Enhanced customer voice survey distribution by register allocated email domain

    Future featuring an enhanced customer survey distribution per email domain registered allocation, maybe helpful for the purpose to future potentially identify dashboard of recipients per email domain.
  • Customer voice survey distribution warnings display setup

    Future featuring potential customer voice survey distribution warnings setup in the event a survey has already been transmitted maybe helpful from setup. Not featuring a recipient survey distribution validation, user may potentially not easily identify whether a survey may have already been transmitted to the same recipient. Featuring a configuration within the survey setting to prevent duplicates of survey transmissions to the same recipient and/or popup warn or list to the end user when a survey may have already been transmitted maybe valuable to prevent survey duplications or duplications within a period range.
  • Customer voice survey content design and distribution registered restrictions

    Future featuring the option to register listing of potential restrictions before composing a survey design and/or before distribution maybe helpful (e.g. branding name, un-natural word, recipients, city or location or zip code, age, race, etc...
  • Customer voice survey design version control

    Future featuring customer voice survey design version control, maybe nice to feature, for the purpose to visualize potential revision history and visualize transitions or evolutions of outcomes.
  • Customer survey design setting to allow number of distributions allowed

    Future featuring a customer survey design setting to specify number of distributions allowed maybe helpful, sometimes potential marketing strategist may have preference to only use the survey once, visualize collected feedback and auto-deactivate the survey after a number of distribution or after first distribution to recipients.
  • Customer voice design and distribution survey option to import from yammer

    Future featuring customer voice distribution import from yammer social media platform, for purpose to test survey image and content impact from polls maybe ideal. Not featuring a customer survey voice design and distribution from yammer, user may potentially conventionally do a content or distribution test of image from social platform before any publishing or releases to the public.
  • Customer voice distribution option to easily visualize courtesies or samples from sales orders

    Future featuring the option to easily visualize customer sales orders FROM customer voice surveys, after a user-consumer may have already submitted a survey, listing of courtesies or samples customer sales orders. Some customer voice surveys maybe eligible for a customer sales order courtesies or samples on certain eligible outcome response criteria. Not easily visualizing customer sales orders sourced from customer voice distribution, user may potentially not easily visualize dashboard as source to support potential eligibility of attempt to keep efforts of attempt to maintain customer satisfactions.
  • Customer voice distribution option to easily visualize courtesies or samples from sales orders

    Future featuring the option to easily visualize customer sales orders auto-generated FROM customer voice surveys, after a user-consumer may have already submitted a survey, listing of courtesies or samples customer sales orders. Some customer voice surveys maybe eligible for a customer sales order courtesies or samples on certain eligible outcome response criteria. Not easily visualizing customer sales orders sourced from customer voice distribution, user may potentially not easily visualize dashboard as source to support potential eligibility of attempt to keep efforts of attempt to maintain customer satisfactions.
  • Power automate sentiment analysis link to Microsoft Dynamics 365 action registered list

    Future featuring power automate sentiment analysis to Microsoft Dynamics 365 registered action list for purpose to visualize authorized sentiment analysis action for purpose to generate a potential auto-system generated customer voice survey courtesy sales order or for purpose to potentially issue an inconvenience reimbursement maybe nice. Not featuring a listing of authorized registered listing of sentiment analysis actions, legal entity may potentially not easily future budget, limit sentiment analysis actions per number of actions, records, or per phrases or words in order to issue a potential eligible customer satisfaction courtesy sales order.