Reports provide users with real-time data about their application(s). Report data is based on the usage of a single, or multiple phone numbers over a given period of time.
Fuse provides users with several different ways to filter their reporting data.
For quick, visual reference Fuse displays call data in line charts. Users can switch between the following types of charts:
In addition to the charts, Fuse presents call data in a table format that includes aggregate totals for each category at the bottom of the table.
Fuse allows users to share report data with other users or stakeholders.
To share a Fuse report, click on the yellow button. This opens a window where users enter the email address of the person they want to share the report with; click the ( ) plus button to add the user. After adding another user, application owners can use the drop-down menu to select the specific phone number(s) that shared users have access to in the reporting section.
Sharing a phone number with another user gives that user the ability to see the reports for that phone number as well as granting access to the phone number's VoiceTrends data.
VoiceTrends is a data and analytics tool kit that provides additional, more granular data than what is provided in Fuse+ reports.
VoiceTrends also provides you with a breakdown of your app's common call paths and usage statistics on a per module basis.
You can use VoiceTrends data to track application performance, test changes, and optimize your applications to improve customer experiences and call automation rates.
To access Voice Trends for your applications, press the button.
For Fuse+ applicatons. VoiceTrends will automatically use the module name as part of the report on showing the statics on the common call path. It is important to name each module with unique names so that they can be better identified in the VoiceTrends diagnostic flow reports.
In addition, VoiceTrends will only differentiate between the type of response that the caller (filled, no input, no match) but not the actual value of the response (such as 1 for yes vs 2 for no). If the value of the response is not private and is needed to be shown in VoiceTrends, then each differing response should branch out to a different module (such as a log module), so that the separate paths can be separated out in the report.
Please refer to the Voice Trends documentation for more information.