CustomerGauge v5.82 Release Notes - Released 12 March 2025

13 New Features

  • Integrating CG’s Gaugie AI recommendation into your organization's business flow.

    • CustomerGauge would like to announce a massive advancement of our AI ecosystem. We now enable organizations to easily leverage and integrate our Gaugie AI’s Close the Loop Recommendations (for your front-line teams) into your wider organization’s business flow.

      • Suggested follow-up email, bullet-point summary, or phone call script format, depending on your platform-wide setting 

    • For organizations that are using our Close the Loop AI Assistant capability, our REST APIs (GET Response API & GET Close the Loop API) now allow you to extract the AI’s Follow-up Text Recommendations to integrate to your system example CRM which contains the universe of information that is specific to that of your organization.

    • Once integrated, you can then use this information in combination with the other key organization insights to create the specific action(s) for the front line staff. 


  • Enhanced Metrics in Response Reporting

    • We have expanded our response analytics with powerful new metrics! These insights will help you optimize your survey strategy, identify improvement areas, and maximize your response quality.

    • What’s New?

      • Responses with Drivers: Number of responses completed with at least one Driver selected.

      • Responses with Drivers Rate: Percentage of responses that included at least one Driver selection.

      • Response Quality Index: Measure the quality of responses received.

      • First Reminder Delivered: Number of survey invitations that received their first reminder.

      • First Reminder Delivered %: Percentage of survey invitations that got their first reminder.

      • Second Reminder Delivered: Number of survey invitations that received their second reminder.

      • Second Reminder Delivered %: Percentage of survey invitations that got their second reminder.

      • First Reminder Responses: Number of responses received after the first reminder.

      • First Reminder Response Rate: Percentage of invitations answered after the first reminder.

      • Second Reminder Responses: Number of responses received after the second reminder.

      • Second Reminder Response Rate: Percentage of invitations answered after the second reminder.

    • These new metrics are now available in the following widgets:

      • Responses Trend

      • Responses Combo

      • Responses Stacked Column

      • Responses Table

      • Responses Map


  • New System Language: Vietnamese

    • Xin chào! Vietnamese has been added as a system language. You can now switch to Vietnamese in My Profile for a more localized experience.


5 Feature Improvements

  • Reporting Enhancements

    • The Action Menu of reporting widgets now has a clearer design, making it easier to see and use available options.

 

  • Drill-down capabilities have been enabled on the following metrics:

    • First Reminder Delivered

    • First Reminder Responses

    • Second Reminder Delivered

    • Second Reminder Responses


  • Survey Suite Enhancements

    • Pop-up and Direct Link surveys now use the same contact identification logic as import processes, ensuring consistent behavior across different features. Previously, these surveys were more likely to create new contacts unnecessarily.


  • Enterprise User Management

    • You can now create SSO-only users, ensuring they log in exclusively via Single Sign-On (SSO) without needing direct access credentials.

    • SSO-only users will no longer receive "Welcome" or "Set Up Password" emails, reducing unnecessary or potentially confusing notifications.


2 Feature Fixes

  • Workflow Rules

    • Fixed an issue where the Change Status and Update Case buttons in New Response and Case Not Closed workflow rules would disappear when toggling between “Quick Status Change On-the-Go” and “Update Case on Response Page.”


  • API Playground

    • Resolved an issue where the "Updated At" parameter was not correctly applied in API requests in the API Playground. This issue was limited to the API Playground and did not happen in the actual API.