Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aquantreleasenotes_254/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aquantreleasenotes_254/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aquantreleasenotes_254/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aquantreleasenotes_254/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aquantreleasenotes_254/public/wp-includes/functions.php on line 6121

Warning: Undefined array key "options" in /www/aquantreleasenotes_254/public/wp-content/plugins/elementor-pro/modules/theme-builder/widgets/site-logo.php on line 192
Customer Hierarchy, Next Potential Symptom, CPS Widget Update, and More

Service Insights

Customer Hierarchy, Next Potential Symptom, CPS Widget Update, and More

Aquant is proud to present the newest release of Service Insights. This release brings beneficial features, including incorporating Customer Hierarchy, the Next Potential Symptom widget, the Cost Per Success breakdown widget, and additional reference table column options. You can find more details about these exciting new features below.

Customer Hierarchy 

With the introduction of Customer Hierarchy, users can now view up to three levels of their customer's hierarchy in various places in the dashboard: through global filters and in the reference tables. It is worth noting that the additional customer hierarchy information will only appear if there are customer tiers established in the data tables. These global filters are located at the bottom right section of every page.     

Customer Hierarchy In Table

"Next Potential Symptom" Widget

This widget, located in the Assets tab, shows the next possible issue and its probability of happening within the next 90 days for each asset. Service Insights leverages the power of historical data to surface potential problems so that the user can keep an eye on specific assets and avoid customer escalation.

New CPS Widget Capabilities

With the newly expanded Cost Per Success widget in the KPI expanded tab, users can see their Cost Per Success broken down by parts cost and labor cost in an easy-to-read stacked bar graph and accompanying table.

Additional Optional Reference Table Selections

Users may now add labor duration and parent event id fields to reference tables throughout Service Insights.

Scroll to Top