CallCabinet User Guide

Installation

CallCabinet is simple to install and, in the majority of cases, is integrated with a PBX, switch or network. All that is required is for it to be activated. To activate CallCabinet, a Customer ID and Site ID is required, which will be created through the registration process. CallCabinet seamlessly integrates with all major unified communications (UC), IP-PBX and telephony platforms. Please speak to your distributor or reseller about the options available, or contact CallCabinet directly at support.callcabinet.com.

Registering on CallCabinet is simple. You should have received an email directly from CallCabinet or your certified CallCabinet partner. Open this email and then click on the provided link which will direct you to CallCabinet’s account registration page, newaccount.callcabinet.com/Account/Register. Once you land on this page, it will look similar to Figure – Register Account. Continue with the registration by entering information into the blank fields:

Login Page

The Homepage

When a user successfully logs in to their account, they will be presented with a home screen similar to that illustrated in Figure – Default Homepage. This is the default screen and is a convenience dashboard exposing certain metrics of the user’s account. This page may be changed or disabled to meet the user’s preferences.

The Menu

The CallCabinet menu is always available on the left-hand side of the application’s screen and is abbreviated with icons. All the user’s options are illustrated in Figure – CallCabinet’s User’s Menu Options.

Call Listing Page

Symbols and other meta-data

Call Details Page

Call details with Manual Transcription and AI Summary

NOTE: For storage-based accounts, in order to access the Call Details page an Advanced User or QA License is required.

The numbers in the description below relate to the image in Figure – Call Details Basic:

1. The Back button returns the user back to the Call Listing page. NOTE: It is recommended to use this button and not the browser’s back button or call listing menu item button. Doing so maintains any filters the user may have set on the Call Listing page. Using the browser’s back button or Call Listing menu item will refresh the Call Listing page and reset all the filters to default.
2. Tag allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item.
3. Legal Hold provides the ability to retain the call’s recording for legal or training purposes. This action will store the call’s recording and associated metadata, regardless of the system’s retention policy. The call will never be deleted while in a legal hold status. NOTE: Retention policies can be specified by clicking on the Settings > Retention Policy menu item.
4. Notes allow a user to apply a general note to a call’s recording. The user has 15 minutes in which to amend or delete the applied note after which the note will become a permanent record and cannot be deleted.
5. Flag allows a user to flag a specific call recording as an additional filtering parameter that may be applied on the Call Listing Page. Flag symbols are entirely up to a company and its users’ interpretation. Any description that makes sense to the user may be assigned to each symbol. It is up to the company and users to ensure no ambiguity exists.
6. Share allows a user to compliantly share a call recording and the associated information regarding the call recording, to an email address, using an encrypted share function. The compliant call share function allows the user to select what information is shared, such as audio, screen captures and notes on the call. The compliant call share function provides an email link to the recipient. When clicked, the link will direct the recipient to a hosted copy of the call recording where the recipient can playback the call. The link only provides temporary access to listen to the call, and the user can define how long that call will be available once shared. The user can set permissions to allow the recipient to add notes to the call and get notified if the recipient adds a note.
7. Email enables a user to send the call’s details via email.
8. Download allows a user to download the call in a non-encrypted audio format. An Admin User may configure which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section. When a user clicks on the Download
   item, a dialog will appear in which the logged in user may select as to where the call should be saved. Once the destination has been selected, the call downloads in the format as determined by the setting Select Download Format.
9. Download Part allows a user to select a segment within the call. Once the segment has been determined the user may download this segment in a non-encrypted audio format by clicking the ‘standalone’ download icon that appears. Should the user decide not to download part of the call, they may press the Cancel button. Once the call segment has been downloaded, to clear the selected segment the logged in user should click the Cancel button. An Admin User may config which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section.
10. The Assigned To section displays the agent’s name the call recording is assigned to, their extension number, and email address. The user may reassign the call recording to another agent by clicking (RE-ASSIGN) . Doing so, will open a dialog pane in which the user may select the desired agent they wish to become associated with the call. Once reassigned, there will be no change to any historical records, except for the call recording the user has just reassigned. An example of this dialog is:
11. The Call Info section describes information regarding the call’s recording, including the caller’s phone number, call duration and whether the call was incoming or outgoing. The Access Log section, illustrated by the icon is a complete audit trail describing which users have interacted with a call’s recording, and what interaction occurred. By clicking this icon, the user’s name is displayed, as well as the date and time each user used the playback feature, made a note, shared the call, or downloaded the call.
12. The Call Playback section allows a user to navigate directly to a portion of the call they would like to hear by clicking locations within the oscillogram.
13. The recorded call’s oscillogram which is a graphical representation of the call’s audio
14. The user may pause the playback, select to ‘rewind’ 15 seconds by pressing the rewind icon or select to ‘fast forward’ 15 seconds by pressing the forward icon . The user may select the x2 icon to play the recording at twice the recorded speed.
15. When the call is being played, this vertical bar indicates the relative position of the audio being heard.
16. Single Notes allows the user to add numerous single notes pinned to a specific point in time in the call by clicking in the single notes bar. The point at which the note is added is indicated by the icon.
17. The Notes Over Time section allows a user to add a note over a specific time period by clicking on the notes over time bar. The resulting icon indicating the ‘note over time’ is .
18. The Screenshots section is where the user is able to view any screenshots associated with the call.
    NOTE: Screenshots are only available with CallCabinet’s Agent Client Installation and associated licensing.
19. The AI Generated Summary section displays a summary of the call after the user clicks the Summarize this Call button, indicated by 19. There are two ways in which this summary may be generated. A) Clicking the Call Transcription icon in the Call Listing page (See Call Listing page section for details on this) or B) clicking the Summarize this Call, indicated by 19. When the user does this a call summary is generated, and displayed in the Call details page. An example of this is illustrated below:
    NOTE: The AI-generated summaries are designed to be longer and more comprehensive by default, providing richer context and deeper insight into the conversation.
20. The transcript section displays a transcript of the call after the user clicks on the Transcript this Call button indicated by 20. There are two ways in which this transcript may be generated. A) Clicking the Call Transcription icon in the Call Listing page (See Call Listing page section for details on this) or B) clicking the Transcribe this Call, indicated by 20. When the user does this a call transcript is generated, and displayed in the Call details page. An example of this is illustrated below:

NOTE: AI Summary and Transcription are a complimentary manual service offered by CallCabinet.

NOTE: Transcription requires the extension the call accesses have the “Transcription Type” selected from the dropdown list that appears when clicked. The current options are;

1. Transcription
2. Standard Analytics
3. Advanced Analytics

NOTE: Video and Screen Share recording requires that the agent participating in the call has permission to do so by ensuring that the “Enable Screen Capture/Video” checkbox is checked under their profile.

Call details with PCI DSS Redaction with Video, Screenshots and Share Screen

NOTE: In order to access the Call Details page an Advanced User or QA License is required if the account is storage based.

The numbers in the description below relate to the image in Figure – Call Details with PCI DSS Redaction, video and screenshot:

1. The Back button returns the user back to the Call Listing page. NOTE: It is recommended to use this button and not the browser’s back button or call listing menu item button. Doing so maintains any filters the user may have set on the allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item. page. Using the browser’s back button or Call Listing menu item will refresh the Call Listing page and reset all the filters to default.
2. Tag allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item.
3. Legal Hold provides the ability to retain the call’s recording for legal or training purposes. This action will store the call’s recording and associated metadata, regardless of the system’s retention policy. The call will never be deleted while in a legal hold status.
   NOTE: Retention policies can be specified by clicking on the Settings > Retention Policy menu item.
4. Notes allow a user to apply a general note to a call’s recording. The user has 15 minutes in which to amend or delete the applied note after which the note will become a permanent record and cannot be deleted.
5. Flag allows a user to flag a specific call recording as an additional filtering parameter that may be applied on the Call Listing Page. Flag symbols are entirely up to a company and its users’ interpretation. Any description that makes sense to the user may be assigned to each symbol. It is up to the company and users to ensure no ambiguity exists.
6. Share allows a user to compliantly share a call recording and the associated information regarding the call recording, to an email address, using an encrypted share function. The compliant call share function allows the user to select what information is shared, such as audio, screen captures and notes on the call. The compliant call share function provides an email link to the recipient. When clicked, the link will direct the recipient to a hosted copy of the call recording where the recipient can playback the call. The link only provides temporary access to listen to the call, and the user can define how long that call will be available once shared. The user can set permissions to allow the recipient to add notes to the call and get notified if the recipient adds a note.
7. Email enables a user to send the call’s details via email.
8. Download allows a user to download the call in a non-encrypted audio format. An admin user may configure which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section. When a user clicks on the Download
   item, a dialog will appear in which the logged in user may select as to where the call should be saved. Once the destination has been selected, the call downloads in the format as determined by the setting Select Download Format.
9. Download Part that appears. Should the user decide not to download part of the call, they may press the Cancel button. Once the call segment has been downloaded, to clear the selected segment the logged in user should click the Cancel button. An admin user may config which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section.
10. The Assigned To section displays the agent’s name the call recording is assigned to, their extension number, and email address. The user may reassign the call recording to another agent by clicking (RE-ASSIGN) . Doing so, will open a dialog pane in which the user may select the desired agent they wish to become associated with the call. Once reassigned, there will be no change to any historical records, except for the call recording the user has just reassigned. An example of this dialog is:
11. The Call Info section describes information regarding the call’s recording, including the caller’s phone number, call duration and whether the call was incoming or outgoing.
12. The Access Log illustrated by the icon is a complete audit trail describing which users have interacted with a call’s recording, and what interaction occurred. By clicking this icon, the user’s name is displayed, as well as the date and time each user used the playback feature, made a note, shared the call, or downloaded the call.
13. The Call Playback section allows a user to navigate directly to a portion of the call they would like to hear by clicking locations within the oscillogram.
14. The recorded call’s oscillogram. The ‘top-half audio’ represents the first speaker, whilst the ‘bottom-half audio’ represents the second speaker.
15. The user may pause the playback, select to ‘rewind’ 15 seconds by pressing the rewind icon or select to ‘fast forward’ 15 seconds by pressing the forward icon . The user may select the x2 icon to play the recording at twice the recorded speed.
16. Shows an example of PCI DSS Redaction of personal and private information within the call’s oscillogram. This is where an agent received sensitive client information that has been redacted. It will not be available in the call’s playback. PCI DSS Compliance Redaction is used for personal Information such as Credit Cards, Social Security Numbers, etc. Manual redaction of personal and private information is only possible with the CallCabinet Agent Client Installation and associated licensing.
17. Speaker indicates when there is a change in speaker. Notice that the ‘bar’ takes on a darker color when the recording is in stereo.
18. Single Notes allows the user to add numerous single notes pinned to a specific point in time in the call by clicking in the single notes bar. The point at which the note is added is indicated by the icon.
19. The Notes Over Time section allows a user to add a note over a specific time period by clicking on the notes over time bar. The resulting icon indicating the ‘note over time’ is .
20. The Screenshots section is where the user is able to view any screenshots associated with the call.
    NOTE: Screenshots are only available with CallCabinet’s Agent Client Installation and associated licensing.
21. The Screenshots display area is where the user may view and enlarge videos, shares and screenshots accordingly.
22. The AI Generated Summary section displays a summary of the call after the user clicks the Summarize this Call button, indicated by 19. There are two ways in which this summary may be generated. A) Clicking the Call Transcription icon in the Call Listing page (See Call Listing page section for details on this) or B) clicking the Summarize this Call, indicated by 19. When the user does this a call summary is generated, and displayed in the Call details page. An example of this is illustrated below:
23. The transcript section displays a transcript of the call after the user clicks on the Transcript this Call button indicated by 20. There are two ways in which this transcript may be generated. A) Clicking the Call Transcription icon in the Call Listing page (See Call Listing page section for details on this) or B) clicking the Transcribe this Call, indicated by 20. When the user does this a call transcript is generated, and displayed in the Call details page. An example of this is illustrated below:

NOTE: AI Summary and Transcription are a complimentary manual service offered by CallCabinet.

NOTE: Transcription requires the extension the call accesses have the “Transcription Type” selected from the dropdown list that appears when clicked. The current options are;

1. Transcription
2. Standard Analytics
3. Advanced Analytics

NOTE: Manual PCI DSS redaction requires that the agent participating in the call has permission to do so by ensuring that the “Manual PCI” checkbox is checked in their agent’s profile and the “Redaction Automated” checkbox in the extension associated with this is unchecked.

NOTE: Automatic PCI DSS redaction requires that the extension the call accesses has the “Redaction Automated” checkbox checked in its profile, and the agent associated with this extension has the “Manual PCI” checkbox unchecked in its profile.

NOTE: Video and Screen Share recording requires that the agent participating in the call has permission to do so by ensuring that the “Enable Screen Capture/Video” checkbox is checked under their profile.

Call details with Speech-to-Text Transcription

The numbers in the description below relate to the image in Figure – Call Details with Speech-to Text Translation:

1. The Back button returns the user back to the Call Listing page.
   NOTE: It is recommended to use this button and not the browser’s back button or call listing menu item button. Doing so maintains any filters the user may have set on the Call Listing page. Using the browser’s back button or Call Listing menu item will refresh the Call Listing page and reset all the filters to default.
2. Tag allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item.
3. Legal Hold provides the ability to retain the call’s recording for legal or training purposes. This action will store the call’s recording and associated metadata, regardless of the system’s retention policy. The call will never be deleted while in a legal hold status.
   NOTE: Retention policies can be specified by clicking on the Settings > Retention Policy menu item.
4. Notes allow a user to apply a general note to a call’s recording. The user has 15 minutes in which to amend or delete the applied note after which the note will become a permanent record and cannot be deleted.
5. Flag allows a user to flag a specific call recording as an additional filtering parameter that may be applied on the Call Listing Page. Flag symbols are entirely up to a company and its users’ interpretation. Any description that makes sense to the user may be assigned to each symbol. It is up to the company and users to ensure no ambiguity exists.
6. Share allows a user to compliantly share a call recording and the associated information regarding the call recording, to an email address, using an encrypted share function. The compliant call share function allows the user to select what information is shared, such as audio, screen captures and notes on the call. The compliant call share function provides an email link to the recipient. When clicked, the link will direct the recipient to a hosted copy of the call recording where the recipient can playback the call. The link only provides temporary access to listen to the call, and the user can define how long that call will be available once shared. The user can set permissions to allow the recipient to add notes to the call and notify the user if the recipient adds a note.
7. Email enables a user to send the call’s details via email.
8. Download allows a user to download the call in a non-encrypted audio format. An Admin User may configure which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section. When a user clicks on the Download item, a dialog will appear in which the logged in user may select as to where the call should be saved. Once the destination has been selected, the call downloads in the format as determined by the setting Select Download Format
9. Download Part allows a user to select a segment within the call. Once the segment has been determined the user may download this segment in a non-encrypted audio format by clicking the ‘standalone’ download icon that appears. Should the user decide not to download part of the call, they may press the Cancel button. Once the call segment has been downloaded, to clear the selected segment the logged in user should click the Cancel button. An Admin user may config which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section.
10. The Assigned To section displays the agent’s name the call recording is assigned to, their extension number, and email address. The user may reassign the call recording to another agent by clicking (RE-ASSIGN) . Doing so, will open a dialog pane in which the user may select the desired agent they wish to become associated with the call. Once reassigned, there will be no change to any historical records, except for the call recording the user has just reassigned. An example of this dialog is:
11. The Call Info section describes information regarding the call’s recording, including the caller’s phone number, call duration and whether the call was incoming or outgoing.
12. The Access Log illustrated by the icon is a complete audit trail describing which users have interacted with a call’s recording, and what interaction occurred. By clicking this icon, the user’s name is displayed, as well as the date and time each user used the playback feature, made a note, shared the call, or downloaded the call.
13. The Call Playback section allows a user to navigate directly to a portion of the call they would like to hear by clicking locations within the oscillogram.
14. The recorded call’s oscillogram. The ‘top-half audio’ represents the first speaker, whilst the ‘bottom-half audio’ represents the second speaker.
15. The user may pause the playback, select to ‘rewind’ 15 seconds by pressing the rewind icon or select to ‘fast forward’ 15 seconds by pressing the forward icon . The user may select the x2 icon to play the recording at twice the recorded speed.
16. Speaker indicates when there is a change in speaker. Notice that the ‘bar’ takes on a darker color when the recording is in stereo.
17. Single Notes allows the user to add numerous single notes pinned to a specific point in time in the call by clicking in the single notes bar. The point at which the note is added is indicated by the icon.
18. The Notes Over Time section allows a user to add a note over a specific time period by clicking on the notes over time bar. The resulting icon indicating the ‘note over time’ is .
19. The Screenshots section is where users are able to view any screenshots associated with the call.
    NOTE: Screenshots are only available with CallCabinet’s Agent Client Installation and associated licensing.
20. The Machine Transcription section is where speech-to-text transcription will appear. Speech-to-text transcription is only available with CallCabinet’s analytics or transcription licensing. The Call Transcription provides a full speech-to-text transcription of the recorded (stereo) call. This area will highlight and synchronize showing the portion of the call the caller or the agent is speaking during playback. It is possible to export the transcription. NOTE: The Call Transcription function requires CallCabinet’s Voice Analytics
21. Categories and Keywords provide the function of the call transcription to search for keywords or phrases throughout the entire call transcript. The words and phrases are then highlighted in the transcript.
    NOTE: This function requires CallCabinet’s Voice Analytics.

NOTE: Transcription requires the extension the call accesses have the “Transcription Type” selected from the dropdown list that appears when clicked. The current options are;

1. Transcription
2. Standard Analytics
3. Advanced Analytics

Call details page with Quality Assurance (QA)

The numbers in the description below relate to the image in Figure – Call Details with Quality Assurance:

1. The Back button returns the user back to the Call Listing page.  NOTE:  It is recommended to use this button and not the browser’s back button or call listing menu item button. Doing so maintains any filters the user may have set on the Call Listing page. Using the browser’s back button or Call Listing menu item will refresh the Call Listing page and reset all the filters to default.
2. Tag allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item.
3. Legal Hold provides the ability to retain the call’s recording for legal or training purposes. This action will store the call’s recording and associated metadata, regardless of the system’s retention policy. The call will never be deleted while in a legal hold status.
   NOTE: Retention policies can be specified by clicking on the Settings > Retention Policy menu item.
4. Notes allow a user to apply a general note to a call’s recording. The user has 15 minutes in which to amend or delete the applied note after which the note will become a permanent record and cannot be deleted.
5. Flag allows a user to flag a specific call recording as an additional filtering parameter that may be applied on the Call Listing Page. Flag symbols are entirely up to a company and its users’ interpretation. Any description that makes sense to the user may be assigned to each symbol. It is up to the company and users to ensure no ambiguity exists.
6. Share allows a user to compliantly share a call recording and the associated information regarding the call recording, to an email address, using an encrypted share function. The compliant call share function allows the user to select what information is shared, such as audio, screen captures and notes on the call. The compliant call share function provides an email link to the recipient. When clicked, the link will direct the recipient to a hosted copy of the call recording where the recipient can playback the call. The link only provides temporary access to listen to the call, and the user can define how long that call will be available once shared. The user can set permissions to allow the recipient to add notes to the call and get notified if the recipient adds a note.
7. Email enables a user to send the call’s details via email.
8. Download allows a user to download the call in a non-encrypted audio format. An Admin User may configure which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section. When a user clicks on the Download item, a dialog will appear in which the logged in user may select as to where the call should be saved. Once the destination has been selected, the call downloads in the format as determined by the setting Select Download Format.
9. Download Part allows a user to select a segment within the call. Once the segment has been determined the user may download this segment in a non-encrypted audio format by clicking the ‘standalone’ download icon that appears. Should the user decide not to download part of the call, they may press the Cancel button. Once the call segment has been downloaded, to clear the selected segment the logged in user should click the Cancel button. An Admin User may config which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section.
10. The Assigned To section displays the agent’s name the call recording is assigned to, their extension number, and email address. The user may reassign the call recording to another agent by clicking (RE-ASSIGN) . Doing so, will open a dialog pane in which the user may select the desired agent they wish to become associated with the call. Once reassigned, there will be no change to any historical records, except for the call recording the user has just reassigned. An example of this dialog is:
11. The Call Info section describes information regarding the call’s recording, including the caller’s phone number, call duration and whether the call was incoming or outgoing.
12. The Access Log illustrated by the icon is a complete audit trail describing which users have interacted with a call’s recording, and what interaction occurred. By clicking this icon, the user’s name is displayed, as well as the date and time each user used the playback feature, made a note, shared the call, or downloaded the call.
13. The Call Playback section allows a user to navigate directly to a portion of the call they would like to hear by clicking locations within the oscillogram.
14. The recorded call’s oscillogram. The ‘top-half audio’ represents the first speaker, whilst the ‘bottom-half audio’ represents the second speaker.
15. The user may pause the playback, select to ‘rewind’ 15 seconds by pressing the rewind icon or select to ‘fast forward’ 15 seconds by pressing the forward icon . The user may select the x2 icon to play the recording at twice the recorded speed.
16. Single Notes allows the user to add numerous single notes pinned to a specific point in time in the call by clicking in the single notes bar. The point at which the note is added is indicated by the icon.
17. The Notes Over Time section allows a user to add a note over a specific time period by clicking on the notes over time bar. The resulting icon indicating the ‘note over time’ is .
18. The Screenshots section is where users are able to view any screenshots associated with the call.
    NOTE: Screenshots are only available with CallCabinet’s Agent Client Installation and associated licensing.
19. The Quality Assurance card.
20. The Available Evaluation Forms section. All the evaluation forms (scorecards) that are available for use in performing an evaluation are listed here. These evaluation forms would have been previously created using the scorecard editor. Within each form, users can manually respond to a series of questions. Once completed, they can add detailed notes and share the evaluation with the relevant agents for review and action.
21. All the completed evaluations are listed in the Completed Evaluation section. It does not matter whether the evaluation has been performed automatically by CallCabinet’s analytics tool or manually, all of them are listed here. The user may view these evaluations by clicking on the ‘eye’ icon
    . Should the logged in user not agree with the automated evaluation, they ‘override’ it by performing a manual evaluation. To do so the user clicks the edit icon associated with the evaluation they want to override. By adjusting specific answers, the user may believe to be inaccurate or incomplete, allowing for a more nuanced and fastidious evaluation of performance.
22. To perform an evaluation manually, the logged in user will select the evaluation form they would like to use by checking the checkbox associated with the desired evaluation form.
23. Once the logged in user selects the evaluation form, they would like to use from those available in the Available Evaluation Form list as indicated by 22, by checking the checkbox associated with the required evaluation form, they would then click the Begin Quality Assurance button. This will result in the evaluation form’s questions becoming rendered in the view. The logged in user may now proceed with the manual evaluation. An example of the questions being rendered once this button (23) is clicked is;
    

NOTE: The icon that is rendered under the QA Status column in the Call Listing page indicates whether the QA performed was a manual, automatic or both .

NOTE: Quality Assurance evaluations are only available with CallCabinet’s Quality Assurance licensing.

Call details page with Analytics

The numbers in the description below relate to the image in Figure – Call Details with Quality Assurance and Analytics: By having an analytics license the quality assurance, visual analytics and transcription cards are enabled. Note too that quality assurance, call summary and call transcription will happen automatically for every call when an Analytics license is purchased.

1. The Back button returns the user back to the Call Listing page. NOTE: It is recommended to use this button and not the browser’s back button or call listing menu item button. Doing so maintains any filters the user may have set on the Call Listings page. Using the browser’s back button or Call Listing menu item will refresh the Call Listings page and reset all the filters to default.
2. Tag allows a user to assign custom identifiers, called tags, to the call. Tags can be created or deleted by clicking on the Settings > Call Tags menu item.
3. Legal Hold provides the ability to retain the call’s recording for legal or training purposes. This action will store the call’s recording and associated metadata, regardless of the system’s retention policy. The call will never be deleted while in a legal hold status.
   NOTE: Retention policies can be specified by clicking on the Settings > Retention Policy menu item.
4. Notes allow a user to apply a general note to a call’s recording. The user has 15 minutes in which to amend or delete the applied note after which the note will become a permanent record and cannot be deleted.
5. Flag allows a user to flag a specific call recording as an additional filtering parameter that may be applied on the Call Listing Page. Flag symbols are entirely up to a company and its users’ interpretation. Any description that makes sense to the user may be assigned to each symbol. It is up to the company and users to ensure no ambiguity exists.
6. Share allows a user to compliantly share a call recording and the associated information regarding the call recording, to an email address, using an encrypted share function. The compliant call share function allows the user to select what information is shared, such as audio, screen captures and notes on the call. The compliant call share function provides an email link to the recipient. When clicked, the link will direct the recipient to a hosted copy of the call recording where the recipient can playback the call. The link only provides temporary access to listen to the call, and the user can define how long that call will be available once shared. The user can set permissions to allow the recipient to add notes to the call and get notified if the recipient adds a note.
7. Email enables a user to send the call’s details via email.
8. Download allows a user to download the call in a non-encrypted audio format. An Admin User may configure which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section. When a user clicks on the Download item, a dialog will appear in which the logged in user may select as to where the call should be saved. Once the destination has been selected, the call downloads in the format as determined by the setting Select Download Format
9. Download Part allows a user to select a segment within the call. Once the segment has been determined the user may download this segment in a non-encrypted audio format by clicking the ‘standalone’ download icon that appears. Should the user decide not to download part of the call, they may press the Cancel button. Once the call segment has been downloaded, to clear the selected segment the logged in user should click the Cancel button. An Admin User may config which file format by clicking on the Settings > General Settings menu item and viewing the Company Settings -> Select Download Format section.
10. The Assigned To section displays the agent’s name the call recording is assigned to, their extension number, and email address. The user may reassign the call recording to another agent by clicking (RE-ASSIGN) . Doing so, will open a dialog pane in which the user may select the desired agent they wish to become associated with the call. Once reassigned, there will be no change to any historical records, except for the call recording the user has just reassigned. An example of this dialog is:
11. The Call Info section describes information regarding the call’s recording, including the caller’s phone number, call duration and whether the call was incoming or outgoing.
12. The Access Log illustrated by the icon is a complete audit trail describing which users have interacted with a call’s recording, and what interaction occurred. By clicking this icon, the user’s name is displayed, as well as the date and time each user used the playback feature, made a note, shared the call, or downloaded the call
13. The Call Playback section allows a user to navigate directly to a portion of the call they would like to hear by clicking locations within the oscillogram.
14. The recorded call’s oscillogram. The ‘top-half audio’ represents the first speaker, whilst the ‘bottom-half audio’ represents the second speaker.
15. The user may pause the playback, select to ‘rewind’ 15 seconds by pressing the rewind icon or select to ‘fast forward’ 15 seconds by pressing the forward icon . The user may select the x2 icon to play the recording at twice the recorded speed.
16. Speaker indicates when there is a change in speaker. Notice that the ‘bar’ takes on a darker color when the recording is in stereo.
17. Single Notes allows the user to add numerous single notes pinned to a specific point in time in the call by clicking in the single notes bar. The point at which the note is added is indicated by the icon.
18. The Notes Over Time section allows a user to add a note over a specific time period by clicking on the notes over time bar. The resulting icon indicating the ‘note over time’ is .
19. The Screenshots section is where users are able to view any screenshots associated with the call.
    NOTE: Screenshots are only available with CallCabinet’s Agent Client Installation and associated licensing.
20. The Quality Assurance section allows the user to view and perform a quality assurance evaluation whilst listening to the call. Quality Assurance evaluations are created under QA Scorecards in the Main Menu. If the user has an analytics license, then automatic QA is performed by CallCabinet, after the completion of the call. The report that is generated will appear under the Completed Evaluations as indicated by 22. The icon that is rendered under the QA Status column indicates whether the QA performed was a manual
    , automatic or both . The user may view these evaluations by clicking on the ‘eye’ icon as indicated by 25. Should the logged in user not agree with the automated evaluation, they ‘override’ it by performing a manual evaluation. To do so the user clicks the edit icon associated with the evaluation they want to override, as indicated by 24. Quality Assurance evaluations are only available with CallCabinet’s Quality Assurance licensing, which incidentally is included in the Analytics License.
21. All available evaluation forms that may be selected for the current call to perform manual QA
22. A list of all the completed evaluations, whether performed manually, and/or automatically.
23. An indicator informing the user whether the evaluation form was generated automatically or manually .
24. Edit the generated report.
25. View the generated report.
26. Once the logged in user selects the evaluation form, they would like to use from those available in the Available Evaluation Form list as indicated by 21, by checking the checkbox associated with the required evaluation form, they would then click the Begin Quality Assurance button. This will result in the evaluation form’s questions becoming rendered in the view. The logged in user may now proceed with the manual evaluation. An example of the questions being rendered once this button (26) is clicked is;
    
27. The Visual Analytics card. This card visually displays a dashboard providing four metrics associated with the call currently being viewed. These are the Call Sentiment, Average Cadence, Interaction Word Cloud and Call Silence. Currently these are not customizable on this view.
28. Call Sentiment. This graph displays changes in sentiment throughout the call highlighting both peaks and drops in sentiment, along with an average sentiment score for the call which in our example is 8%. Depending on the conversation, the overall sentiment of the call may be positive, neutral or negative. The sentiment scale ranges from -100 to +100, providing a clear overview of emotional trends during the conversation. Should the user hover their cursor over the line in the graph a ‘popup’ will appear rendering information associated with that datapoint.
    • • If the sentiment is in a pending state, the label Pending approval is displayed next to the Call Sentiment graph in the Visual Analytics section. Additionally, Pending approval appears beside the Show Sentiment checkbox in the Analysis Tools panel, and you can review the sentiments and analyze if the sentiments are positive or negative.
      • If the sentiment is rejected, the graph is not displayed, and the Not approved is displayed instead. The Show Sentiment checkbox is disabled, and a Not approved message is displayed beside it. If the sentiment is approved, the graph is displayed in the Call Sentiment section, the Show Sentiment checkbox is enabled, and you can view the sentiment analysis.
        If the sentiment is in a pending state, the label Pending approval is displayed next to Call Sentiment graph in the Visual Analytics section. Additionally, Pending approval appears beside the Show Sentiment checkbox in the Analysis Tools panel, and you can view the sentiments.
        
29. Average Cadence: This graph illustrates the ‘speed of the conversation’ or ‘words per minute’ (wpm) at various intervals of the call. The average call cadence is also illustrated in the graph. There are three variations in speech rate (https://www.prezent.ai/zenpedia/words-per-minutespeech):
    1. 1. slow pace (around 100-120 wpm),
       2. normal pace (around 130-160 wpm), and
       3. fast pace (around 170-200 wpm).

    According to the National Center for Voice and Speech, the average conversation rate for English speakers in the United States is about 150 wpm.
    The average speaking rate will vary depending on the activity, for example: (https://virtualspeech.com/blog/average-speaking-ratewords-per-minute)

• Presentations: between 100-150 wpm for a comfortable pace
• Conversational: between 120-150 wpm
• Radio hosts and podcasters: between 150-160 wpm

Word cadence should be from 140 to 180 words per minute. High words per minute usually indicates poor communication, whereas low words per minute indicates a possible issue, for instance unable to answer a customer’s question. This card also displays the average words per minute. In our example it is 155 wpm.

30. Interaction Word Cloud: This provides a visual representation of words contained within the conversation. The larger and bolder a word appears in the visual, implies that it is used more often in the conversation and therefore likely to be more important than the other words in the cluster of words.
31. Call Silence: This visual provides insight into the silence periods within a call, which includes placing a customer on hold. This helps identify moments of inactivity and their potential impact on the flow of the conversation. Monitoring silence is important as it can reveal important insights into communication dynamics, emotional undertones, and the quality of interactions. An example would be identifying a high level of silence during a conversation. This is unproductive and could potentially lead to low customer satisfaction and increased customer frustration. Additionally, high levels of silence should trigger the need for a supervisor to explore the root causes, which could be:
    1. Poor agent knowledge which requires training.
    2. Slow and inefficient systems resulting in agents waiting for system response, for example poor network quality, lag, or dropped signals.
    3. Agents need to navigate between multiple applications to find the desired answers.
    4. Agents are not supplied with a Single Pane of Glass view to the information or systems they require information from to conduct their roles efficiently.
    5. Silence may arise from emotional reactions like anxiety, tension, or discomfort. For example, if the conversation covers sensitive or contentious topics, one party may hesitate or refrain from speaking due to unease or fear of conflict.
    6. When a conversation involves complex information, problem-solving, or decision-making, a participant may need time to process information, think critically, or decide how to respond, which leads to prolonged periods of silence.

This card also displays the average call silence. In our example it is 2%.

32. The AI Generated Summary section is automatically generated and displays a summary of the call. See the explanation below.
33. The transcript section is automatically generated and displays a transcript. See the explanation below.

The explanation following relates to the image Figure – Transcription and Analytics. The AI generated Summary and Automated Analytics Tools is probably the most important part of this view.

The AI generated summary provides a succinct summary of the conversation that occurred. This is very useful in providing the context of the conversation.

The user may read the actual transcript under the Interaction Transcript section. Here the conversation is divided up between two parties; the team member/customer(s) and the agent.

A Copy Transcription button allows users to copy the full call transcript to their clipboard with a single click, making it easy to share or document the entire conversation.

The user is able to search the call by typing the word or phrase they are wanting to locate in the conversation in the search box illustrated in the Analysis Tools card. For example, should the user type thank you, then all occurrences of this will be ‘highlighted’ in the transcript as well as how many occurrences were discovered. This is illustrated below with blue boxes. The arrows facilitate navigation between occurrences of the searched term, with the view automatically scrolling to each instance.

Should the user want to look at the sentiment of the conversation, they may check the Show Sentiment checkbox found in the Analysis Tools card. This will result in the highlighting of both positive and negative sentiments that may have occurred during the conversation. This is illustrated in the image below. The red highlighted text amplifies the negative sentiment whereas the green text the positive sentiment.

In a similar fashion should the user want to view any detected topics or Intents that have been mentioned in the conversation, all they need to do is check the respective checkbox in the Analytics Tools card. For example; Here the detected topics are underlined in purple, whereas the detected Intents, or action points are underlined in blue.

Should the user hover their cursor over any of the underlined topics or intents, then the actual topic or intent is ‘popped up’. For Example, when hovering over the detected topic ‘fault connection to the server’ the topic this relates to is ‘Product Fault’;

NOTE: For some calls only few Analytics Tools checkboxes are available. For instance, only Show Detected Topics and Show Detected Intentions and not Show Sentiment. The reason for this is: If there is insufficient sentiment data, the Show Sentiment checkbox will not be available as there is nothing to display. The same applies to the other two Analytics tools checkboxes (Show Detected Topics and Show Detected Intentions) as well as any Analytics features on the Call Details page.

Referring to Figure – Transcription and Analytics, the Quality Control card will render the scorecard that is selected (highlighted) under the Completed Evaluations card, indicated by 22 in Figure – Call Details with Quality Assurance and Analytics once selected the user will immediately be able to see what the result for the question is as related to this conversation. If the user discovers that the question was marked wrong, when in fact it is correct as the words used in the transcript do not appear in the current word pack, the user may add the words to the word pack associated with the question. To do this the user would go to the Scorecard Phrases card and enter the phrase in the word phrase text field. Once done the user would click the add button, thereby applying the new phase to the pack for the question. Notice that in the Scorecard Phrases card, a percentage of average hit rate of all the question’s word phrases across all calls that have been evaluated. This gives feedback as to how effective the various phrases are. A high average hit rate suggests the phrase is valuable and may be beneficial to incorporate into the scorecard configuration for future evaluations.

NOTE: The hit rate calculation considers phrases entered from the time of input onwards.

Using the AI Agent in the Call Listing and Call Details pages

When, in the Call Listing page as illustrated in Figure – Activate AI Agent, the user may interact with the AI Agent, via the Agent Chat dialog asking the AI Agent any question relating to the user’s CallCabinet account they wish. In the ‘Ask AI Agent’ field, illustrated by 4, the user would enter the question, for example: ‘What is the sentiment’ or ‘Did the agent introduce themselves in a friendly manner’, and then click the Send button, illustrated by 5. The AI Agent, after a few moments, will respond with the answer in the text area illustrated by 6. The user may continue asking any questions relating to their calls and CallCabinet account and the AI Agent will respond by appending the answers in the text area illustrated by 6. Should the user want to re-start the conversation, they may clear all previous interactions, by clicking on the ‘Start New Conversation’ button illustrated by 7. This will result in the text area, illustrated by 6, being reset and cleared.

It is possible for the user to ask questions about a specific call or calls. To do this, the user would click the checkbox associated with the call or calls, illustrated by 8, they would like the AI Agent to use as its source when answering any questions the user asks. A maximum of 10 calls may be selected. The answers will appear in the text area, illustrated by 6.

Figure – Activate AI Agent illustrates the agent in the Call Listing page. Should a user decide to apply any filters in the Call Listing page, then the AI Agent will ‘honor’ these filters by taking them into account when answering a user’s questions. The user is therefore able to ‘narrow’ down the calls the AI Agent interrogates by not only allotting any call or calls the user may have selected by means of the ‘bulk check-box’, but by also applying the filters and associated criteria the user may have applied.

When a user views a call in its Call Details page, then any questions the user asks the AI Agent will be specific to that call itself. The process of asking the AI Agent questions is the same as described when the user is in the Call Listing page. If the agent has been ‘activated’ in the Call Listing page, then it will be automatically available in the Call Details page. If it is not activated, then the user must ‘activate’ the AI Agent by clicking on the AI Agent icon, located in the top right-hand side, illustrated by 1 in Figure – AI Agent Call Details. When the user does this, a ‘floating button’ appears, illustrated by 2, and a Chat Dialog appears, as illustrated by 3, in which they are able to ‘chat with the AI Agent’ asking questions in connection with the call in the current Call Details page.

The user may interact with the AI Agent, via the Agent Chat dialog asking the AI Agent any question relating to the call. In the ‘Ask AI Agent’ field, illustrated by 4 in Figure – AI Agent Call Details, the user enters the question, for example: ‘What is the sentiment for this call’ or ‘Did the agent introduce themselves in a friendly manner’, and then click the Send button, illustrated by 5. The AI Agent, after a few moments, will respond with the answer in the text area illustrated by 7. The user may continue asking any questions relating to the call and the AI Agent will respond by appending the answers in the text area illustrated by 7. Should the user want to re-start the conversation, they may clear all previous interactions, by clicking on the ‘Start New Conversation’ button illustrated by 6. This will result in the text area, illustrated by 7, being reset and cleared.

In summary, the AI Agent is applied to a single call when in the Call Details page, however, when in the Call Listing page, the AI Agent is applied to all calls (or selected calls) and filters when answering user queries.

NOTE: A user may interact with the AI Agent on any page the ‘floating button’ appears.

Chat Listing

The Chat Listing page displays the following columns in the table:

• View Chat: Opens the selected chat conversation for detailed viewing.
• Date: Indicates the timestamp when the chat occurred.
• Chat Name: Indicates the title or identifier of the chat session.
• ChatRecord Id: Indicates a unique system-generated ID for the chat record.
• Chat Type: Indicates the chat format, such as Channel, Group, or One-on-One.
• Site Name: Indicates the location or site associated with the chat.
• Participants: Indicates the list of all users who took part in the chat.
• Chat Owner: Indicates the user responsible for or who initiated the chat.
• Actions (Icons): Provides quick access to options such as adding notes and downloading a chat conversation. The following options are displayed:
  • Is Internal Chat: Indicates whether the chat is internal.
  • Has Attachment: Displays if the chat contains any attachments.
  • Notes: Allows you to add or view notes related to the chat.
  • Download: Enables you to download the chat conversation.

Each column in the data table can be sorted by clicking its column name. To filter a column, click the ‘filter icon’  next to the column header.

NOTE: The default column filter option is Starts With, which helps users quickly narrow down results based on values that begin with the entered characters. This filter is applicable only to text-based columns. For non-text columns such as dates or durations, the default filter does not apply.

The following bulk action options are available on the Chat Listing page:

• Email Chats: Allows you to email multiple chat conversations to selected users.
• Download: Allows you to download multiple chat conversations at once.
• Export List Results: Allows you to export the list of chat conversations to an Excel file.

Searching Chats

Viewing a Chat

Performing Actions on a Chat Conversation

Reporting

The numbers in the discussion below relate to the image in Figure – Reporting Default Page:

1. The Calls Summary section displays the number of Calls This Week, the Total Calls number of recorded calls to date, and the percentage number of calls This Month as compared to the same period last month.
2. The Calls Volume section renders a bar chart displaying the call volume over the past six months. To see this chart, click on the   icon. An example of this graph being rendered is;
3. The Choose report template button renders a list of previously saved report templates, when clicked. When generating a report users have the option to save the report’s template that they may reuse. Once saved, it will appear in a dropdown list. If a user is going to continually generate a report based on the same parameters/criteria, they may create their own template based on one of the five reports. To run a saved report a user would click Choose report template button and then select the report template’s name visible in the list. An example of this dropdown template report list is;

Incidentally, the user may search for a saved template by typing their request in the Search Reports search field. For example;

• A Call Duration Report allows a user to pull data associated with call durations. For example, if the user wishes to evaluate how much time agents are spending on calls daily, the user would pull a Call Duration Report using the criteria: by agent, by day.
• A Call Volume Report pulls data associated with call volumes. For example, if the user wishes to evaluate how many incoming calls occurred on a particular extension each day, the user would pull a Call Volume Report using the criteria: extension by day.
• An Evaluation Counts Report allows a user to generate reports based on quality assurance evaluations. Quality assurance evaluation reporting is only possible with CallCabinet’s Quality Assurance (QA) license.
• An Evaluation Scores Report will pull reports based on quality assurance evaluation scores. Quality assurance evaluation reporting is only possible with CallCabinet’s Quality Assurance (QA) license.
• A Speech Analytics Report will create reports based on call insights, such as call sentiment. Speech Analytics Reporting is only possible with CallCabinet’s Analytics (QA) license.

Settings

When clicking on the settings item in the menu, a submenu is revealed. Each of these submenu items are discussed in detail in the following sections.  The settings section of CallCabinet may be viewed as the admin section of the application.

NOTE:  An Admin, Super Admin or a Support User Role is required to access the various Settings pages. A support user has limited access to the Settings pages.

General Settings

NOTE: An Admin, Super Admin or Support User Role is required to access the General page.

The General Settings page allows Admin, Super Admin and Support users to manage the overall settings that govern the entirety of CallCabinet for your organization. Settings that are edited will be reflected for all users, regardless of user role or licensing permissions. This view is made up of five tabulated views, as illustrated by Figure General Settings Tabs. Each of these views is discussed below.

1. Company Information

This tab’s view is rendered when a user clicks on the ‘Company Information’ tab indicated by 1 in the screen image illustrated in Figure menu above. The rendered screen looks as follows:

The purpose of each field is:

• Company Email: The email address associated with your organization’s CallCabinet account. Generally, you will create a distribution email account for this.
• Company Address: The physical location of your organization.
• Company City: The city in which your organization is located.
• Company State: The state in which your organization is located.
• Company ZIP: ZIP Code of the location of your organization.
• Company Phone No: The phone number associated with your organization’s CallCabinet account.

If a user makes changes to any of these fields, the Update button is automatically enabled, allowing the user to click it and save them.

2. Security Settings

This tab’s view is rendered when a user clicks on the ‘Security Settings’ tab indicated by 2 in the screen image illustrated in Figure menu above. The rendered screen looks as follows:

The purpose of each field is:

• Two Factor Authentication: This determines the multi-factor authentication option. By clicking on the dropdown, currently three options are available to the user; App MFA, which is recommended, Email MFA or No MFA.
• Business Contact: This is a very important field in which the admin user should enter a customer’s business distribution email account. CallCabinet will use this email address when sending business incident emails to recipients who have access to this email. It is important that a user does not enter an individual’s email address. The reason for this is if that user no longer belongs to the company, then any emails sent by CallCabinet may not be read. Having a distribution email account ensures that anyone who has access to the account will receive the email.
• Compliance Contact: This is a very important field in which the admin user should enter a customer’s compliance distribution email account. CallCabinet will use this email address when sending compliance incident emails to recipients who have access to this email. It is important that a user does not enter an individual’s email address. The reason for this is if that user no longer belongs to the company, then any emails sent by CallCabinet may not be read. Having a distribution email account ensures that anyone who has access to the account will receive the email.
• Finance Contact: This is a very important field in which the admin user should enter a customer’s finance distribution email account. CallCabinet will use this email address when sending finance incident emails to recipients who have access to this email. It is important that a user does not enter an individual’s email address. The reason for this is if that user no longer belongs to the company, then any emails sent by CallCabinet may not be read. Having a distribution email account ensures that anyone who has access to the account will receive the email.
• Disable Classic Login: By ticking this checkbox, a user will not be able to log in using their email address and a password. However, it allows for single sign-on (SSO) using Gmail, Google Apps, Windows Azure, or Okta username that matches the user’s specified email address in CallCabinet.
• Download Calls: By ticking this checkbox, a user with the requisite licensing will be able to download call recordings from the Call Listing and Call Details
• Email Calls: By ticking this checkbox, users with the requisite licensing will be able to email the call ID and other metadata directly from the Call Listing and Call Details
• Be Idle For: Defines, in minutes, how long a user, who is logged into CallCabinet, may be inactive on a screen. Once the time limit has expired, the user will be automatically logged out of CallCabinet. The reason for this is security.
• Share Calls: By ticking this checkbox, users with the requisite licensing will be able to compliantly share a call recording and selected metadata from the Call Listing and Call Details

NOTE: Download Calls, Email Calls and Share Downloadable Call features may result in a compliance violation depending on the regulations governing your industry and your organization. Check with your Compliance Officer or legal department about your specific security needs before using these features.

If a user makes changes to any of these fields, the Update button is automatically enabled, allowing the user to click it to save these changes.

3. Quality Assurance Settings

This tab’s view is rendered when a user clicks on the ‘Quality Assurance Settings’ tab indicated by 3 in the screen image illustrated in Figure menu above. The rendered screen looks as follows:

If you have purchased a Quality Assurance (QA) license and are going to allow users to perform QA on your agents, then it is in this section that you set the various QA features. The purpose of each field is:

• Email Agent on Eval: Ticking this checkbox allows a QA user to email the agent the report after completing a QA evaluation. The options that you may select are; No Mail, Share or Share With Call Audio.
• QA Email Message: You may enter a ‘pre-canned’ message in this field, which will be included in the email to the agent if Email Agent on Eval option has been enabled (ticked).
• QA Score Rounding Points: An admin user may set the number of decimal places required in a QA’s percentage score. The number of decimal positions required may be selected from the dropdown, where the minimum is 0, resulting in an integer value for example 45%, 67%, 88 and. the maximum selectable resolution being 4 decimal places resulting in a real value, for example 45.0001%, 67.0072%, 88.1536%.
• Email Manager on Completed QA: Ticking this checkbox allows a QA evaluator to automatically email the complete evaluation and results to the agent’s specified manager. Managers can be specified per agent on the Agent Management page by clicking on the Settings > Agent Management menu item.
• Don’t Grey out QA Questions: Ticking this checkbox will not grey out QA questions as they are completed during the evaluation.
• Show Completion Percentage: Ticking this checkbox allows for the displaying of the percentage of progress completed by a user (supervisor) before finishing the QA evaluation.
• Show Running Score: Ticking this checkbox allows for the displaying of the current score the agent is achieving as the user (supervisor) progresses through the QA evaluation.
• Include Screenshots in QA Completed Email: Ticking this checkbox results in any screenshots being included in the email sent to the agent’s specified manager mentioned above.
  If a user makes changes to any of these fields, the Update button is automatically enabled allowing the user to click it to save them.

4. Company Settings

This tab’s view is rendered when a user clicks on the ‘Company Settings tab indicated by 4 in the screen image illustrated in Figure menu above. The rendered screen looks as follows:

The purpose of each field is:

• Company URL: is the unique URL that was created for your organization’s access to CallCabinet, for example, https://artworks1.callcabinet.com.
• Send Weekly Email: refers to the weekly storage email updates. By ticking the checkbox in an email is sent each week to the address specified in the Company Email field entered under the Company Information widget.
• WIN Authorized Endpoint: permits the admin to select, via the drop-down menu, whether single sign-on (SSO) is through Azure B2C IDP, Live, NTLM or Office 365.
• Select Download Format: selects the audio format an audio file will be downloaded as. The required option is selected from the drop-down menu and the user may choose between an MP3, PCM WAV or the original audio file format.
• Company Date Format: determines the date and time formats (and durations) displayed in CallCabinet.
• Export Date Format: determines the date display format in the exported data files. The required option is selected from the drop-down menu. The current options are MinutesSeconds or TotalSeconds.
• Storage Location: refers to where your data is stored. It is set when your account was provisioned and may not be changed. NOTE: Please contact your service provider should you need to change or update your storage location if your account is a storage-based plan.
• Azure SSO Claim for email: The field in the Azure Active Directory Claim that contains the email of the user. If left blank it will assume the field name “email”, which is the typical field used. However, if your implementation in Azure AD uses a different field it can be specified here. NOTE: This field should not be changed unless you experience an issue with SSO login and only after consultation with CallCabinet Technical Support.
• Include Download Name in Excel Export: Ticking this checkbox will result in the download ‘audio file’ name being included as an extra column when an Excel file is exported. This column maps the name of the downloaded audio file to the call that it is associated with.

If a user makes changes to any of these fields, the Update button is automatically enabled, allowing the user to click it and save the changes.

5. Compliant Call Share Settings

This tab’s view is rendered when a user clicks on the ‘Compliance Call Share Settings tab indicated by 5 in the screen image illustrated in Figure menu above. The rendered screen looks as follows:

It is in this section that the administrator determines what call sharing features should be available to each user that has the requisite permission. The purpose of each field is:

• Share for a Maximum of: allows a user to define how long the complaint call share link is accessible to the recipient. Clicking on the dropdown exposes the options. Currently, the time restraints are predefined as: one hour, one day, one week, one month, two months and unlimited.
• Use OTP for Shares: By ticking this checkbox a two-step authentication process is activated for the recipient receiving a compliant call share email. When the recipient clicks on the link in the compliant call share email, a second email is sent to the recipient containing an OTP (One Time Password) that they will be required to input before they can access the compliantly shared call recording. This feature provides a user with an additional layer of security as well as a compliance share log in the audit trail to log the recipient’s receipt of the call recording.
• Share General Notes: By ticking this checkbox, a user with the requisite licensing will be able to share general notes along with the recorded audio when using the compliant call sharing feature.
• Share Time-based notes when Sharing Calls: By ticking this checkbox, the user with the requisite licensing will be able to share time-based notes along with the recorded audio when using the compliant call sharing feature.
• Share Point In Time Notes when Sharing Calls: By ticking this checkbox, a user with the requisite licensing will be able to share point-in-time notes along with the recorded audio using the compliant call sharing feature.
• Share Screenshot when Sharing Calls: By ticking this checkbox, a user with the requisite licensing will be able to share agent screenshots along with the recorded audio using the compliant call sharing feature.
• Share Extensions when Sharing Calls: By ticking this checkbox, a user with the requisite licensing will be able to share extension information along with the recorded audio when using the compliant call sharing feature.
• Share Transcription when Sharing Calls: By ticking this checkbox, a user with the requisite licensing will be able to share the speech-to-text transcription along with the recorded audio using the compliant call sharing feature.
• Share Downloadable Call: By ticking this checkbox, a user with the requisite licensing will be able to share a downloadable copy of the recorded audio when using the compliant call sharing feature. NOTE: CallCabinet DOES NOT recommend checking the Share Downloadable Call checkbox to ensure that your compliant call share feature is fully compliant.
• Share Call with permission to Add Note: By ticking this checkbox, a user with the requisite licensing will be able to grant permission to the recipient to add a note to the call share. Incidentally, when the recipient does add a note, the user that sent the call to the recipient will receive an email alerting the user to the fact that a recipient added a note to the call.

NOTE: Download Calls, Email Calls and Share Downloadable Call features may result in a compliance violation depending on the regulations governing your industry and your organization. Check with your Compliance Officer or legal department about your specific security needs before using these features.

If a user makes changes to any of these fields, the Update button is automatically enabled, allowing the user to click it to save them.

Custom User Roles

NOTE:  Users are individuals who have login access to the CallCabinet Cloud. Each user that is created is required to be assigned a specific role. These roles grant a user access and permission to perform specific tasks on the account they are logged into.

There are six predefined, non-editable user role types as illustrated by 1 in Figure – Predefined Roles. These are;

• A Support User role does not grant access to the Call Listing page. However, permissions to various settings and features, such as some general settings, QA, site, user, agent, extension, phone book retention policy and whitelist management settings are granted. As you can see, this is a support role.
• A Standard User role grants access to the Call Listing page and allows the user to filter call data and
• An Admin User role grants access to the Call Listing page as well as management of some of the system settings.
  • A Super Admin role grants access to the entirety of the settings in CallCabinet and is the highest role that can be assigned.
  • There are two types of restricted user roles.
    1. Restricted User (or Restricted Standard) role
    2. Restricted Admin role

Both roles can be restricted to Agent(s), Group(s) or Site(s). Please see the section on Restricted User Roles. A complete description of each of these five roles is described under the heading Predefined Roles and Associated Permissions. In order to understand what permissions each of these predefined roles have been granted, the logged in user having the requisite permission will be able to view each of them. As an example, clicking the Standard User role button, as illustrated by 1 in Figure – Standard User Roles results in the displaying of the permissions, illustrated by 2, each one’s dependencies, if any and the licenses required for specific features, illustrated by 3, should those features be required. Every single permission and feature that is available in CallCabinet is listed, however it is those permissions whose checkboxes are checked that will be assigned to the role. The key which describes the license ‘color bubbles’ is at the top of the view as illustrated by 4 in Figure – Standard User Roles.

Essentially, there are two license types:

• Advanced User License. When assigned to a user it grants access to the Call Details page (if the account is on a storage plan) and Reporting functionality. For Per-Seat plan accounts there is no limit as to the number of users that may be assigned the Advanced User License. However, Storage Plan accounts must purchase these licenses as required.
• The QA License class must be purchased before it may be assigned to a user. When assigned to a user, it will grant the user access to the Quality Assurance (QA) features. There are three sub-licenses associated with the QA License. These are:
  1. QA Supervisor
  2. QA Analyst
  3. QA Admin

The different permission granted by each of these licenses are illustrated in Figure Quality Assurance License Features.

Over and above the predefined roles, it is possible to create a custom role. To do so, the logged in user, who must have an Admin or Super Admin role, clicks the Add New Role on the top right side of the screen as illustrated by 2 in Figure – Predefined Roles. This will result in an Add New Role dialog appearing, as illustrated in Figure – Add New Role. The user enters the new role name, Custom Role for example and then selects Save.

Once done, the new role name will appear in the Role Name column, under the predefined roles. This is illustrated by 1 in the Figure – Allocating Permissions in a Custom Role.

NOTE:  Custom user roles are governed by licensing. For example: if the custom user role is to provide access to the QA features, a corresponding QA license is required.

If you study the six predefined roles created by CallCabinet you will notice each of them are granted all the Analytics and Transcription permissions. There may be times in which a use-case demands that the logged in user may not manually transcribe or summarize a call, which if they are assigned one of the predefined roles will allow them to do so. As these predefined roles are immutable, the only way around this is for an admin user to create a custom role in which the Manual Transcription and Manual Summary permissions are not enabled. The admin user may then, once enabling all the other required permissions and saving the custom role, assign the user this role thereby preventing the user from manually generating any transcriptions or call summaries.

The numbers in the discussion below relate to the image in Figure – Allocating Permissions in a Custom Role:

1. The Role Name section lists the roles that have been created and saved.
2. The Edit Pencil icon allows the user to edit the corresponding role.
3. The Trash icon allows the user to delete the role. If the role has been assigned to one or more users, then the role cannot be deleted. To remove the role, ensure that any users assigned the custom role are assigned another. Once the role is no longer assigned to any users, it may then be deleted.
4. The Permissions section allows the user to assign which CallCabinet features are required to be granted to the custom role being created or edited. To enable a permission, click the checkbox alongside the required permission. Should the permission be dependent upon another permission being enabled, if that dependent permission is not already enabled, then CallCabinet will automatically enable it.
5. Dependencies: To see which dependency a particular permission requires, hover over ‘Has Dependencies’ associated with the permission required. A tooltip will display containing the dependency information for the desired permission.
6. Clicking on Save Permissions will save any changes made to the custom role.

Once a new user role has been created, it may be assigned to a user.

Restricted User Roles

NOTE: An Admin, Super Admin or Support User Role is required to access the Settings pages.
The Figure – Restricted User Roles page allows a user to set parameters for restriction. Once a user has created

a new user under Settings > User Management and assigned this new user a restricted user role, the user will then appear here, in the restricted user roles page.

The numbers below relate to the image illustrated in Figure – Restricted User Roles:

1. The Data Table displays information associated with the restricted user. For instance, Email, First Name and Last Name.
2. The Assign Agent icon permits the logged in user to restrict a user by agent(s). Clicking this icon will result is an Edit Assigned Agents dialog appearing which will look similar to the following;
   
   In the dialog the admin user may assign the agents whose calls the restricted user may have access to. All the agents that may be assigned will appear in the column as illustrated by A. The admin user clicks the agent’s name they would like to assign the restricted. Doing so will result in the agent appearing in column B. An admin user may also search for an agent they may wish to assign by entering the agent’s name in the search field as illustrated by C. To remove an agent associated with a restricted user, the admin user would click on the agent’s name in column B. Once the admin user has assigned all the individual agents to the restricted user, they must save the selection by clicking the Save button illustrated by D. See Agent Management Page for more information regarding agents.
3. The Assign Group icon permits the admin user to restrict the agents whose calls the restricted user may have access by agent group(s). Clicking this icon will result is an Edit Assigned Groups dialog appearing which will look similar to the following;
   
   In the dialog the admin user may assign the agent groups whose calls the restricted user may have access to. All the groups that may be assigned will appear in the column as illustrated by A. The admin user clicks the agent group they would like to assign the restricted user by clicking on the group’s name. Doing so will result in the group appearing in column B. An admin user may also search for a group they may wish to assign by entering the group’s name in the search field as illustrated by C. To remove a group associated with a restricted user, the admin user would click on the agent group in column B. Once the user has assigned all the agent groups to the restricted user, they must save the selection by clicking the Save button illustrated by D. See Agent Groups Page for more information.
4. The Assign Site icon permits the admin user to restrict a user by site(s). Clicking this icon will result is an Edit Assigned Sites dialog appearing which will look similar to the following;
   
   In the dialog the admin user may assign the sites whose calls the restricted user may have access to. All the sites that may be assigned will appear in the column as illustrated by A. The admin user clicks the site they would like to assign the restricted user by clicking on the site’s name. Doing so will result in the site appearing in column B. An admin user may also search for a site they may wish to assign by entering the site’s name in the search field as illustrated by C. To remove a site associated with a restricted user, the admin user would click on the sites name in column B. Once the admin user has assigned all the sites to the restricted user, they must save the selection by clicking the Save button illustrated by D. See Site Management Page for more information
5. Clicking on Edit Columns allow the logged in user to change the columns the user would like to be visible. An example of the dialog that appears is;
   
   Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.
6. Clicking the circumflex associated with the agent will provide a summary of any agents, agent groups or sites that have been assigned the user

To discuss this a little further, the numbers below refer to Figure – Restricted User Agent Summary.

• The admin user clicks this circumflex associated with a restricted user, revealing an ‘agent permission’ card.
• Clicking this tab reveals a table displaying all the sites assigned to this restricted user. For example;
• Clicking this tab reveals a table displaying all the groups assigned to this restricted user. For example;
• Clicking this tab reveals a table displaying all the agents assigned to this restricted user. For example;
• Clicking this tab reveals a table displaying all the extensions assigned to this restricted user. For example;

Site Management

NOTE: An Admin or Super Admin role is required to access the Settings pages.
The Site Management page allows a user to edit and delete sites.

NOTE:  The default compliance interval for the CallCabinet Agent Client Desktop application is set per site and is managed in this page. The enable selective recording feature is also set per site and managed in this page.

The numbers in the discussion below relate to the image in Figure Site Management.

1. The Customer Information section displays Customer Name and Customer ID, which are unique to the customer
2. Clicking on the Provision button on any of the third-party applications the user would like to provision will direct the user to an instruction page for that application.

For instance, if the user clicked on the Provision button for Microsoft Teams button will direct the user to the CallCabinet for Microsoft Teams Installer. The user will then download the installer and follow the prompts to provision CallCabinet for Microsoft Teams. The page the user is directed to is illustrated in Figure – Provisioning Microsoft Teams and which outlines the prerequisites for provisioning the Microsoft Teams Installer.

Clicking the Provision button for Zoom will direct the user to the CallCabinet for Zoom Installer, which is illustrated in Figure – Provisioning Zoom. The user will download the installer and follow the prompts to provision CallCabinet for Zoom.

Clicking the Provision button for RingCentral will direct the user to the CallCabinet for RingCentral’s Installer. The user will then download the installer and follow the prompts to provision CallCabinet for RingCentral. The page the user is directed to is illustrated in Figure – Provisioning RingCentral and which outlines the prerequisites for provisioning the RingCentral Installer

As a final example; Clicking the Provision button for 8×8 will direct the user to the CallCabinet for 8×8’s Installer. The page the user is directed to is illustrated in Figure – Provisioning 8×8 and which outlines the prerequisites for provisioning as well as how to go about provisioning 8×8. The user must follow these instructions, entering all the relevant information. Once done the user would click the ‘Add to 8×8’ button to provision 8×8 for call recording.

3. The Data Table details a list of your current sites, including the unique site ID, site name, the default compliance interval and the hide unanalyzed calls feature for each site.
4. By checking the Hide Unanalyzed Call checkbox will result in the fact that only once a call has been fully analyzed will it appear in the Call Listing page. Until that time, it will remain invisible. By leaving the checkbox unchecked will result in the call being visible in the Call Listing page, even if it has not been fully analyzed by CallCabinet.
5. The Edit icon permits the user to edit the associated site.
6. The Trash icon permits the user to delete the associated site.
7. Clicking on Edit Columns allow the logged in user to change the columns the user would like to be visible. Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the ‘filter icon’ adjacent to the column heading the user is wanting to apply the filter.
8. Clicking this button will allow an admin user to create a new site. To add a new site, the user is required to enter the required information. The discussion below regarding the various fields relates to Figure – Add New Site.

• Site Name is the name you would like to give the site.
• The Upload Window Start Time and Upload Window Duration fields relate to the site-specific time period selected, defining when calls may be uploaded to CallCabinet. By default, the duration is set to zero, which means calls will upload as soon as they are processed.
• The Foundation URL field permits the user to enter a URL specific to an onsite recorder for CallCabinet’s Foundation users with a hybrid solution (on-prem and cloud storage).
• Storage Location is where the calls associated with this site are to be stored. The admin user should select the location that is closest to them.
• Transcription Language allows the admin user to select what transcription language should be by clicking the dropdown list and selecting the appropriate language. By default, CallCabinet attempts to auto detect the language being spoken and then transcribes for that language.
• Hide Unanalyzed Calls allows the admin user to determine whether a call should be listed if it has or has not been analyzed. By default, a call will not appear in the Call Listing page until such time all analysis on that call has been completed. This includes PIC redaction. Should a user want their calls on this site to be displayed even though analysis is not completed, then this feature should be unchecked. It is highly recommended that this remains checked
• The Enable Selective Recording enables users to select from the following settings:

1. 1. enable recording of all currently configured extensions,
   2. disable all recording for currently configured extensions and
   3. manually choose which currently configured extensions to record.

Checking this checkbox will result in a confirmation dialog appearing that the user needs to agree to in order for selective recording to be enabled. An example of this confirmation dialog is shown in Figure – Enable Selective Recording Confirmation.

• The Default Compliance Interval for the CallCabinet Agent Client Desktop application is set per site and is managed here.

Agent Management

NOTE:  Agents are individuals whose calls are being recorded by CallCabinet.
The Agent Management page permits a user to create, bulk import, edit and delete agents as required.

The numbers in the discussion below relate to the image in Figure Agent Management:

1. Clicking on the Add New Agent button opens a dialog, which is illustrated and described in Figure Add New Agent.

To add a new agent, the logged in user is required to enter information into the various fields as described below. This discussion relates to the image found in Figure Add New Agent

• The administrator enters the required agent information such as the agent’s First Name, Last Name, and Email address
• The administrator should select the appropriate Site Name from the site name drop-down list.
• The administrator should enter the agent’s Windows Username which is to identify the windows user to whom the CallCabinet Agent Client application will be assigned.
• The administrator should then select the agent’s Supervisor, Special Email, Extensions, Groups and any Notes that may be of use.
• Checking the Enable “Screen Capture/Video” check box will enable screenshots on this agent’s profile using the CallCabinet Agent Client. Once checked, the user will need to set the interval between screenshots. CallCabinet recommendation is 15-second intervals. Please note that a license is required for the use of this feature.
• Checking the Manual PCI check box will enable manual compliance intervention using the CallCabinet Agent Client. Please note that automatic PCI is enabled on an extension. If Manual PCI is enabled then the extension that is associated with this agent must have its ‘Redaction Automated’ checkbox disabled. Please note that a manual PCI license is required for this feature.
  NOTE: if automated PCI redaction is required, the administrator does not enable it here under Agent Management, but rather under the extension management where this feature is enabled on the extension that is associated with this agent.

2. Clicking on the Import Agents button opens a dialog which permits the user to download a template, complete the required fields and upload the template to perform a bulk import of agent information. An example of the Import Agents dialog is:
3. The agent license display area displays how many Screenshot Licenses are currently in use and available (purchased). For more information, please refer to Table 1 – Agent Licenses.
4. The agent license display area displays how many Manual PCI Licenses are currently in use and available (purchased). For more information, please refer to Table 1 – Agent Licenses.
5. The Agent Data Table displays all the account’s agent information. Details such as the agent’s first name, last name, site, assigned agent groups, whether screenshot capture is enabled and whether manual PCI redaction has been enabled are rendered.
6. The Items per-page drop-down allows a user to change the number of items returned on each page. The range is from 25 – 10 000.
7. The Excel icon, when clicked, will export the Agent Data Table in an xlsx file directly to the user’s desktop.
8. Clicking on the Cog icon results in a Reassign Calls dialog appearing in which the user may bulk re-assign extensions to agents using a defined date range. An example of the Reassign Calls dialog rendered is:
9. The Trash icon will delete one or more agents depending on how many you select using the bulk selector check box in the far left-hand column (indicator 13).
10. Clicking on Edit Columns allow the logged in user to change the columns the user would like to be visible.
11. The Edit Pencil icon permits the user to edit the associated site.
12. The Trash  icon permits the user to delete the associated site.
13. The Bulk check(tick) box; By checking this box, all the agents are selected that appear in the Agent Data Table. Should a user want to select individual agents, then the user would check each agent’s individual checkbox associated on each line.

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon  adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Assign Agents

The Assign Agents page grants the admin user permission to assign agents to extensions. Each agent may be assigned an extension. The numbers in the discussion below relate to the image in Figure Assign Agents:

1. Clicking on the Assign Extension button will open a dialog box allowing the user to associate an agent with an extension by choosing an agent and an extension from drop-down menus. An example of this dialog is illustrated below.Agents can be created by clicking on the Settings > Agent Management menu item. Extensions can be created by clicking on the Settings > Extension Management menu item.

2. The Assign Agents Table displays an agent list and their associated extensions.
3. The Edit Pencil icon permits the user to edit assigned extensions and agents.
4. The Trash icon permits the user to delete the associated agent and extension information.
5. The Items per-page drop-down allows a user to change the number of agents and associated extensions returned on each page. The range is from 25 to 2000.
6. The Excel icon, when clicked, will export the Assign Agents Table in an xlsx file directly to the user’s desktop.
7. Clicking on Edit Columns allow the logged in user to change the columns the user would like to be visible in the Assign Agents Table. An example of this dialog is;

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon   adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Agent Groups

The Agent Groups page permits the admin user to create one or more groups to which agents may be assigned.

For example, a company may want to group agents into a specific department, for instance a finance department. The user may then create the group, call it financeDepartment, and assign agents to it, thereby linking them to the financeDepartment group and all functions associated with it. This group then becomes useful, for instance, in the Call Listing page where a user might decide to filter calls associated with a particular department. The user may decide that the department is the finance department and then select the group financeDepartment as the filter. Performing a search against this filter will result in a list of all calls and participating agents being returned and displayed for this group only. Groups are useful for report generation too.

The numbers in the discussion below relate to the image in Figure Agent Groups:

1. The Add Group button will open a dialog box, in which the user may enter the name they would like to assign the group and which agents should be assigned to that group. An example of this dialog is illustrated below:
2. The Group Data Table displays a group list of all the groups created.
3. The Edit Pencil icon permits the user to edit the associated group and the agents assigned to that group.
4. The Trash icon permits the user to delete the associated group.

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon  adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Extension Management

The Extension Management page allows the admin user to manage extensions.

NOTE:  Speech-to-text transcription is assigned per extension and can be managed here.

The numbers in the discussion below relate to the image in Figure – Extension Management:

1. The Add New Extension button will permit the user to add a new extension. Pressing this button will result in an Add dialog to be rendered, as illustrated below. The user enters information in the Extension, Site Name and assigned Agent Name fields.

Recording Enabled will allow for the extension to be recorded. Turning this off by unchecking the checkbox will result in the extension no longer being recorded.

Platform Type will allow the admin user to select the platform on which the extension resides, for instance, Teams, Webex, SIP, Ring Central et cetera, from the dropdown list.

Transcription Type enables speech-to-text transcription on this extension, provided the relevant licensing has been provisioned. Transcription requires the extension the call accesses have the “Transcription Type” selected from the dropdown list that appears when clicked. The current options are;

1. None
2. Transcription
3. Standard Analytics
4. Advanced Analytics

Automatic PCI DSS redaction requires that the extension the call accesses has the “Redaction Automated” checkbox checked in its profile, and the agent associated with this extension has the “Manual PCI” checkbox unchecked in its profile. NOTE: Manual redaction is enabled under the agent’s profile accessed via the Settings > Agent Management menu item.

2. Clicking on the Import Extensions button opens a dialog which permits the user to download a template, complete the required fields and upload the template to perform a bulk import of extension information. An example of the Import Extensions dialog is:
3. All the licenses that have been purchased and consumed are listed in this portion of the view. In this example 21 Transcription licenses have been purchased of which 17 have been assigned to extensions. 50 Standard Analytics licenses have been purchased, 4 of which have been assigned to extensions, resulting in automatic Quality assurance taking place for those extensions, and 51 Transcription licenses have been purchased of which 18 have been assigned to extensions resulting in automatic PCI redaction occurring on those extensions.
4. The Extension Data Table details all the current extension information such as the Extension, the Site Name, the assigned Agent Name and whether recording and speech-to-text Transcription has been enabled on the extension
5. Platform Type indicates the platform the extension is associated with. For instance; Teams, Webex, SIP, et cetera
6. Transcription Type column indicates whether transcription is enabled on the extension and whether it is basic Transcription or transcription required for Conversation Analytics
7. Redaction Automated indicates whether the extension is enabled for automatic redaction. If it is, then a license is required.
8. Is Archived indicates whether the extension and associated calls have been archived. If it has, then a license is required. See 10 below for further explanation on archiving an extension.
9. The Edit Pencil icon permits the user to edit the associated extension where the admin user may, for instance enable or disable extension recording, change the transcription type for the extension as well as enable or disable automated redaction.
10. The Trash icon permits the user to delete the associated extension. When the admin user clicks on this a dialog appears warning the user that they have requested to either delete or archive the extension and its associated calls. Please be aware that in order to archive an extension’s calls, the customer must have already purchased an Archive License. A user cannot archive calls without the license unless the number of calls to be archived is less than 1000 (1k). An example of this dialog is:

Should the user want to continue with the process, they would click ‘Yes’ which will result in the following dialog being rendered;

The user is presented with the option of deleting the extension, which will result in all the calls associated with this extension becoming deleted forever, or archive the calls in which case the extension is removed, but its calls will be archived. Should the user select the Archive option, CallCabinet will apply an ‘Archive Extension’ license to this extension resulting in the customer being billed each month for as long as the extension remains archived and its calls ‘younger’ than the retention period. Remember, to archive an extension, the license must have already been purchased and provisioned or the number of calls is less than 1000, in which case an Archive License is not required. Any calls archived will be visible in the account’s Call Listing page. If the Is Archived column is visible in the Call Listing page, all calls that are archived will be marked as such in this column. Should the user have selected Delete, then all the calls associated with the extension will be deleted and will no longer be available.
NOTE: Once calls are deleted, they can never be recovered.
NOTE: Should any of the archived extension’s calls expire as per the customer’s retention policy, in other words they are ‘older’ than the retention policy stipulates, then those expired archived calls will be deleted and the associated archive license released. This license will then become available to archive any other extension’s calls.

11. Clicking on the Cog icon results in a Reassign Extension dialog appearing in which the user may re-assign an extension to an agent. An example of the dialog rendered is:
12. The Excel icon, when clicked, will export the Extension Data Table in an xlsx file directly to the user’s desktop.
13. The Map Extensions to Sites feature is checked when there may be duplicate extensions that need to be mapped.
14. The Items per-page drop-down allows a user to change the number of extensions returned on each page. The range is from 25 – 2000.
15. Clicking on Edit Columns allow the logged in user to change the columns the user would like to be visible in the Extension Data Table.

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon   adjacent to the column heading which appears as the user passes their cursor over the column’s name to which the user is wanting to apply a filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Call Tags

The Call Tags page is where the admin user is able to create, edit and delete Call Tags. Call Tags are applied to call recordings on both the Call Details and Call Listing pages as well as to a call that triggered a Notification, should this feature be enabled. Call Tags can be used as additional filtering parameters on the Call Listing page, helping users identify specific calls based on customized and thoughtfully applied Call Tags. A tag for instance could be called “Spam”. This tag may then be applied to a call, against which filtering may be applied.

The numbers in the discussion below relate to the image in Figure – Call Tags:

1. Clicking on the Add a New Tag button will open an Add New Tag dialog where the user may enter the name of the new tag and click Save to save it. An example of this dialog is illustrated below:

2. The Call Tags Data Table will display any call tags users have previously created and saved.
3. The Edit Pencil icon permits the user to edit the tag.
4. The Trash icon permits the user to delete the associated tag.
5. The Show Inactive Tags checkbox, when checked, will show any inactive tags in the Call Tags Data Table. Inactive tags are those that have not been assigned to any call..

The Name column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon adjacent to the column heading which appears as the user passes their cursor over the column’s name. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

QA Randomizer

This view is made up of three tabulated views, as illustrated by Figure QA Randomizer Settings Tabs. Each of these tabs and their associated view is discussed below.
NOTE:  An Admin, Super Admin or Support User Role is required to access the QA Randomizer settings pages.

The QA Randomizer view page allows the admin user to set additional controls for the QA Randomizer. The QA Randomizer tool removes the manual task of sourcing and handpicking a call for evaluation by randomly selecting a call for evaluation. The QA Randomizer is launched from the QA Dashboard page.

The numbers in the discussion below relate to the image in Figure – Randomizer Settings:

1. The Internal Calls checkbox, when checked, will include internal calls in the randomizer’s selection.
2. The Stopped Calls checkbox, when checked, will include stopped calls in the randomizer’s selection.
3. The From Date field defines a timeframe, measured in days passed that the randomizer will include when selecting call recordings for evaluation.
4. Any changes made on this page will result in the Update button becoming enabled allowing for the user to save the changes by clicking on the button.

The numbers in the discussion below relate to the image in Figure – Randomizer Call Direction:
The Direction section allows the user to define what percentage of incoming and outgoing calls should be included in the randomized evaluation. Combined value must equal 100%.

1. The Incoming spinner field permits the user to enter the weighting that should be applied to incoming calls. For example; a value of 90 means 90% of the calls selected for evaluation will be incoming calls.
2. The Outgoing spinner field permits the user to enter the weighting that should be applied to outgoing calls. For example; a value of 10 means 10% of the calls selected for evaluation will be outgoing calls.
3. Any changes made on this page will result in the Update button becoming enabled allowing for the user to save the changes by clicking on the button.

The numbers in the discussion below relate to the image in Figure – Randomizer Agent Settings:

The Agents section is where an admin user assigns weights against agents to determine the randomness of them selected.

1. The list of all agents.
2. The admin user may assign a weight to agents, guiding the randomizer to include more or less of the agent’s calls. The higher the weight the greater the chance of selection in the random selection process. TO amplify this a little more;
   When QA weights is equal to;
   • 0 then agents’ calls are not included in the randomizer queue.
   • 50 then agents’ calls shown two times less often.
   • 100 then agents’ calls show at the normal rate.
   • 400 then agents’ calls show four times more often.
   • 800 then agents’ calls show eight times more often.
3. The Items per-page drop-down allows a user to change the number of tags returned on each page. The range is from 25 – 2000.
4. Any changes made on this page will result in the Update button becoming enabled allowing for the user to save the changes by clicking on the button.

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon  adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Notifications

The Notifications page allows a user to add alerts based on custom created rules. These notifications are triggered by the Quality Assessment (QA) evaluation process. This feature enables users who have the appropriate permission to track critical trends in their data and receive timely Notifications when significant changes occur. This assists a business in making appropriate decisions as a result of these real-time insights.

NOTE:  An Analytics or QA License is required to activate this feature.

Depending upon whether an account has an Analytics license or not, the process of creating a notification differs.

Notification Creation when account is NOT configured with Conversation Analytics

If the account is a ‘standard’ account and does not have an Analytic License provisioned, then an admin user clicks on Settings > Navigation sub-menu, the notifications page as illustrated in Figure – Standard Notifications. In this default page that is rendered all the current notification configurations are displayed in a table, as illustrated by 1. The table consists of a number of columns. These are;

• Created: The day and time the notification was created.
• Name: A meaningful name given to the notification.
• Flow Type: This indicates whether it is the Standard trigger flow or triggering that occurs during the Analytics flow process.
• Last Trigger Date: This is the latest date and time this event triggered a notification.
• Type: This details the event that will trigger a notification. For the standard notification this will be ‘Keyword’.

The admin user may decide which columns they would like visible, or removed from the notification table by clicking the ‘Edit Columns’ button illustrated by 2. From the dialog that appears the admin user may make the changes they require. Once done the admin user must not forget to click the Save button to enforce their changes. Should the admin user click the Default button in the Edit Columns dialog, then all possible columns are displayed in a predetermined order in the Notification table.

It is possible for an admin user to edit any of the notifications rendered in the table by clicking the Edit icon associated with the notification configuration they would like to change. This is illustrated by 3. Likewise, a notification may be removed by clicking on the Trash icon, as illustrated by 4, that is associated with the notification the admin user wishes to delete. This page provides the admin user with an overview of all the Notification event configurations that have been created.

If an admin user wishes to create a new Notification, there are two processes from which they may select. One, use the wizard, or two, go straight to the Review page and enter all the required information there. To create a new notification using the wizard, the admin user must make sure that the checkbox ‘Skip Wizard’ is unchecked illustrated by 6 in Figure – Standard Notifications, then go ahead and click the New Notification button as illustrated by 5 in Figure – Standard Notifications. This results in a ‘wizard’ being rendered, which guides the admin user through a step-by-step Notification creation process.

The admin user enters the name they would like to give the notification into the Name field, as indicated by 1 in Figure – New Standard Notification. This is a required field. The admin user must ensure that the Keyword radio button is enabled. Once done, the admin user clicks the Next: Trigger button, illustrated by 2. Should the admin user want to exit creating a new Notification, they would click the Cancel button, illustrated by 3. An admin user may cancel at any stage of the process by clicking the Cancel button in any of the wizard’s views. By clicking the Next: Trigger button, the Trigger page is rendered. This is illustrated in Figure – Standard Trigger. The admin user enters the word that is to be detected, resulting in a Notification being raised. This is illustrated by 1 in Figure – Standard Trigger. When the word is triggered all related functions on the notification page will use this keyword. This word may be anything the user requires the system to trigger on, for instance, ‘cancel’ or a profanity.

Note: only one word or word phrase may be entered and is a required field.

Should the admin user want to change any information they entered in on the previous page, all they need to do is click the Previous button as illustrated by 2 in Figure – Standard Trigger. This is available in any of the wizard’s views. Once the admin user is happy with the trigger word or phrase they have entered, they click the Next: Actions button, illustrated by 3 in Figure – Standard Trigger to continue with setting up the Notification’s parameters.

Once the admin user clicks the Next: Actions button, the wizard’s Actions page is rendered. This is illustrated in Figure – Standard Action.

This page requires the admin user to decide the action that is to be performed when a Notification occurs. A message may be sent to a Webhook endpoint, whose POST URL must be entered in the field illustrated by 1, or an email address, illustrated by 2, of the recipients, where each recipient’s address is separated by a semi-colon. What is important is that at least one of these actions must be applied. Either a Webhook endpoint, or an email action, or both.

Another action feature an admin user may activate, is to select the tags, if required, that should be attached to the call whose conversation triggers the notification. If one or more tags are selected from the Tag dropdown list, as illustrated by 3, when a conversation raises a notification, these tags will be attached to the call. A user may then use these flags as filter criteria when searching for calls that raised a notification from within the Call Listing page.

Once the admin user has determined the actions that are to occur when raising a notification, they click the Next: Filters button, as illustrated by 4 in Figure – Standard Action the wizard’s Filters page is rendered. This is illustrated in Figure – Standard Filters.

Should it be necessary, the admin user may make changes to any of the fields previously configured. Once happy with the Notification’s configuration, the admin user clicks the Save button, illustrated by 1 in Figure – Standard Review to save and ‘activate’ the newly created Notification. This will result in a confirmation dialog appearing in which the admin user must confirm the ‘activation’ of the Notification by clicking the Confirm button in the rendered dialog. An example of this confirmation dialog is illustrated below. Should the admin user not want to ‘activate’ the notification then they would click Cancel.

Once complete, this new notification will appear in the notifications table, illustrated by 3 in the Notifications page, as illustrated by Figure – Standard Notifications.

Finally, the other option of creating a new Notification is; if the admin user does not want to use the wizard to create a new notification but rather configure it all on one view, they may do so by checking the ‘Always Skip To Review’ checkbox, illustrated by 6 in Figure – Standard Notification and click the ‘New Notification’ button illustrated by 5 in Figure – Standard Notification. Doing so renders the Review page, as illustrated in Figure – Standard Review. The admin user may now configure the Notification all in one view, entering in all the required information and pressing Save, as illustrated by 1 in Figure – Standard Review, and confirming the notification creation. This will result in the new notification appearing in the notifications table, illustrated by 3 in the Notifications page, as illustrated by Figure – Standard Notifications

Notification Creation when account IS configured with Conversation Analytics

Should an admin user wish to create a new Notification on an account that is provisioned for Conversation Analytics, there are two processes they may select from. One, use the wizard, or two, go straight to the Review page and enter all the required information there. To create a new notification using the wizard, the admin user must make sure that the checkbox ‘Skip Wizard’ is unchecked illustrated by 8 in Figure – Notifications, then go ahead and click the New Notification button as illustrated by 4 in Figure – Notifications. This results in a ‘wizard’ being rendered, which guides the admin user through a step-by-step Notification creation process:

In this first page rendered, the admin user enters the name they would like to assign the notification they are creating by entering this in the Name field. Next, the admin user must decide the Notification Type from the Type dropdown list. The Notification Type represents the specific event that will trigger the creation of a Notification Event. The selected Notification Type defines the available Notification Triggers that will be further customized during the Notification Configuration process. An example of the Notification Type dropdown is;

These Notification Type’s in the dropdown list are predefined by CallCabinet and are immutable. At the moment the Notification Type options are;

Once the admin user has entered the Name and selected the desired Type, they click the Next: Window button. The user is taken to the ‘Notification Window’ page, as illustrated by Figure – Notification Window. 

NOTE: both the Name and Type fields are required fields, which means that they require values before the admin user is able to proceed to the next step in creating the Notification.

The Notification Window defines the call volume threshold required to trigger the notification. The admin user is first required to decide on the Window configuration type from the Type dropdown list. Currently there are two options, Interval and Interaction;

If the admin user selects Interval, they are then required to enter the timeframe in Hours in which calls should be grouped and then evaluated before triggering a Notification event. For example;

Likewise, should the admin user select Interaction, they are then required to enter the Number of Calls to be evaluated before triggering a Notification event. For example;

Once done, the admin user clicks the Next: Triggers button and is navigated to the Notification Triggers page, as illustrated by Figure – Notification Triggers.

NOTE: both fields are required fields, which means that they require values before the user is able to proceed to the next step in creating the Notification.

A trigger is used to validate and trigger a Notification when the condition is met. An admin user is able to set a maximum of three triggers per Notification. So, Notification Triggers define the specific thresholds used to evaluate aggregated call data and determine whether a Notification Event should be created. 

The level of the notification may be: Info, Warning or Critical. This level is selected from the Level dropdown list. Once the admin user has selected the Level, they must select the Condition and associated value. 

NOTE: The options available in the Condition dropdown list is determined by the Notification Type selected earlier. For instance, if the user selected AudioDuration as the type, then the condition options are >= (greater-than or equal to) or <= (Less than or equal to). Likewise, if the admin user had selected a Notification Type of Phrases then the condition option is IN. Currently all possible options are 

Examples of Trigger Conditions include:

• Less Than or Equal to ( <= )
• Greater Than or Equal to ( >= )
• IN (the value is within a specified list of values)

Once the admin user has selected the Condition, the value associated with that condition must be entered. 

Each Trigger has the option to enable Notify Trigger. When selected, the trigger will send a push notification through notification channels such as an email or webhook. The configuration of these notification methods will be done later in the process. If the admin user does not check this checkbox, then the trigger will not be sent but will be entered into the Activity log.

If the admin user would like to add another trigger Condition, they would click the +Add Trigger button that appears across the notification Trigger screen as illustrated in Figure – Notification Triggers. 

The admin user proceeds to the next page once all the required fields have been populated with information, by clicking the Next: Cooldown button. This results in the Cooldown page being rendered, as illustrated in Figure – Notification Cooldown.

A Notification Cooldown period configures the amount of time that must pass after a notification is sent before another notification may be issued. This helps prevent users from receiving excessive notifications (i.e. being spammed) in short time frames. The time interval is set in Minutes, where the minimum allowed interval is 30 minutes. Once the Cooldown period has been set, the admin user moves onto the next page, Notification Actions by clicking the Next: Actions button.

Push notifications inform users about a new Notification Event. Please ensure that the Notify Trigger option is enabled when configuring Notification Triggers to activate notifications. Webhook is a POST URL where notifications will be sent. When the admin user checks this checkbox, the Webhook’s URL must be entered into the field that appears. Email is the email address where the notification will be sent when this checkbox is checked. When this is checked an email field appears in which the admin user may enter a list of comma-separated email addresses of the recipients to which the Notification event is to be sent. 

Should the admin user want a Tag to be attached to the call that resulted in a Notification Event to occur, then they would check this box, and from the dropdown list which contains all configured Tags, select the Tag they would like to be attached to the call. This is very useful, as a user is then able to filter all calls in the Call Listing page that have the Tag attached.

An example of a Notification that may be sent is:

Once the admin user has completed entering the required Notification Actions, they would click the Next: Filtersbutton which results in the Navigation Filters page being rendered, as illustrated in Figure – Notification Filters. Notification Filters allows for greater control by allowing an Admin user to specify which interactions should be considered when evaluating Notification Triggers. For instance, the admin user can limit a Notification to specific Agents or Groups of Agents as well as Sites, by clicking on the Filters Type dropdown list. The current filter options are;

The final step in creating a Notification is clicking the Review button. A page rendering the complete configuration parameters set for the Notification. An example of this is illustrated in Figure – Notification Review. The admin user may edit any of the fields, if necessary. Once the Admin user is satisfied with the Notification’s configuration, they must click the Save button to save the newly created Notification. Should any of the Notification’s conditions be met, a Notification Event is generated and at a minimum, logged.

If an admin user wishes to create a new Notification, without making use of the wizard, as described above then they would check (enable) the checkbox ‘Skip Wizard’ illustrated by 8 in Figure – Notifications, then click the New Notification button as illustrated by 4 in Figure – Notifications. This will result in the admin user being taken directly to the Review page in which they may enter all the Notification configuration details in one convenient view. Once they have entered all the pertinent information they would click Save to save the Notification’s configuration. An example of the ‘blank’ review page is illustrated in Figure – Notification Blank Review

Referring back to Figure – Notifications, there are two tablatures rendered; the Management tablature illustrated by 1 and the Activity Log tablature, illustrated by 2. We have discussed the Management tablature.

When the admin user clicks the Activity Log tablature, in which all Notifications that have occurred are rendered in the table. This table provides a detailed overview of past notifications, enabling the admin user to effectively monitor and analyze Notification Events with precise information on when and why they were triggered. An example of this Activity log is illustrated in Figure – Notification Activity Log.

Each Notification Log includes the following key details:

• Time Stamp: The exact time when the Notification was triggered.
• Title: The name of the admin for easy identification.
• Type & Level: The category and severity of the admin.
• Description: A concise explanation of the event that triggered the admin.
• Notification: Whether a notification was sent.
• Triggered Calls: The number of calls that triggered the admin.

By clicking on any notification, an admin user may access additional in-depth information, including:

• Condition: The specific metric that was being monitored.
• Trigger: The rule or threshold that activated the notification.
• Call Link: A direct link to the recorded call for further review.

Retention Policy

The Retention Policy page allows an admin user to define the data retention policy per site. The retention

period is always in terms of days. This therefore implies that year periods must be translated into their days equivalent.

NOTE: The minimum retention period is 180 days for storage-based accounts and 1 day for Per Seat based accounts.
The numbers in the discussion below relate to the image in Figure Retention Policy:

1. The Retention Policy Data Table displays a list of all current sites and their associated retention periods, measured in days.
2. The Edit icon permits the user to edit the retention policy associated with the site. The user, when editing, is able to set the number of days of retention or flag it to Never

Each column in the data table can be sorted by clicking on the column name and filtering can be applied by clicking on the icon  adjacent to the column heading which appears as the user passes their cursor over the column’s name the user is wanting to apply the filter. In the associated dialog that appears, the user will enter the criteria that are to be applied to the filter to produce the desired result.

Grid Management

A user with the requisite role, such as Super Admin is able to assign the default columns visible for all users, for instance on the Call Listing Page. Incidentally, a user may still add or remove columns, as well as order the columns to meet their personal preference.

The numbers in the discussion below relate to the image in Figure – Managing Data Table Columns

1. Grid Types display the list of pages on which columns can be added, removed or ordered.
2. Available Columns displays the list of columns that are currently hidden in the selected page’s data table, in this example, the Call Listing Page.
3. Visible Columns displays the list of columns that are currently visible in the selected page’s data table, in this example, the Call Listing Page.

To manipulate the columns the user must first press on the name of the page under the Grid Types column (labeled 1). To make a column visible, the user would left-press their mouse button on the column name in the available column and then keeping the left button depressed, drag the column name to the visible column. The user may also move the column name up or down in this list, to set the order of the columns. To remove a column, the process is the same except that the user drags the name from the visible column to the available column.

The numbers in the discussion below relate to the image in Figure Locking Grid Columns.

A user is able to lock the columns preventing removal or ordering. To do this, the user would first click on the edit icon
, labeled 2, next to the page name in the Grid Types column, labeled 1. Doing so will render a screen similar to that displayed in Figure – Locking Grid Columns. If a user clicks on the column name, labeled 3, they will be able to lock or unlock a column. Locking the column, prevents a user from removing it from, or reordering it on the Call Listing page view. A column that is locked will look similar to that indicated by 4 Incidentally, once the column is unlocked, the user may remove the column. Once all the desired changes are made and all the columns are locked the user may save the grid structure by clicking on the Save button, indicated by 5.

IP WhiteList

The IP WhiteList page allows an admin user to restrict login access to CallCabinet by specifying an IP address and enabling the IP WhiteList feature. By checking the Use IP Whitelist check box and the user entering their password to verify their identity limits access to CallCabinet from any IP Addresses other than those specified in the IP Address list.

The numbers in the discussion below relate to the image in Figure – IP Whitelist:

1. Clicking on the Use IP WhiteList checkbox enables the whitelist. However, before being enabled the user needs to enter their credentials in the dialog that is rendered. If the credentials are valid, the whitelist is enabled. An example of this dialog is illustrated below:
   
   Once the whitelist is enabled users may only login from IPs in the IP address list.
2. Clicking on the Add a new IP Address button allows the user with the requisite permission to add a new IP address to IP Address whitelist. This button is enabled once the Use IP WhiteList checkbox is enabled.
3. Table of whitelisted IP addresses. Remember, these IP addresses are outward facing IP addresses.
4. The Edit icon permits the user to edit the associated IP Address. This icon is enabled once the Use IP WhiteList checkbox is enabled.
5. The Trash icon permits the user to delete the associated IP Address. This icon is enabled once the Use IP WhiteList checkbox is enabled.

Phonebook

The Phonebook page allows the user to build a directory of contacts in CallCabinet. A phonebook is similar to that in a person’s cell or mobile phone, where a user adds numbers and names. This is a useful feature incorporated in the Call Listing Page. Should there be a phone number or email address, with an associated name present in the Phonebook, then the Phone Book field will be updated to contain the name associated with the number or email address in the Call Listing Page.

The numbers in the discussion below relate to the image in Figure – Phonebook:

1. The Phonebook Data Table displays a list of all the current contacts in the phonebook.
2. Edit icon permits the user to edit the associated phonebook contact.
3. The Trash icon permits the user to delete the associated phonebook contact.
4. The Excel icon, when clicked, will export the Phonebook Data Table in an xlsx file directly to the user’s desktop.
5. Clicking on the Add New Phone Book permits a user to add a contact to the Phonebook, which consists of the contact’s name and phone number. Clicking this button results in a dialog being rendered in which the user may enter the relevant information. An example of this dialog is illustrated below:
   
6. Clicking on the Import Phone Book button opens a dialog which permits the user to download a template, complete the required fields and upload the template to perform a bulk import of phone book information. An example of the Import Phone Book dialog is:
   

Conversation Analytics Portal – Analytics Tab

To access CallCabinet’s Analytics view, the analytics user must click the Analytics tab which appears at the top of CallCabinet’s view, as illustrated by 1 in the Figure – Enable Analytics View. When an analytics user clicks the Analytics tab a page similar to that rendered in Figure – Initial Analytics View is displayed.

The menu that is associated with the Analytics portal is rendered on the left side of the view, as illustrated by 1 in Figure – Initial Analytics View

An analytics user is able to create their own dashboards, each of which may contain up to six visuals. When the analytics user clicks on My Dashboards, as illustrated by 2 in Figure – Analytics Initial View, an Available Dashboards card is rendered as illustrated by 3 in Figure – Analytics Initial View. This card consists of a carousel which contains all dashboards the analytics user has created and may select. The analytics user is able to navigate from one dashboard slide to another by clicking the navigation icons,
 and . If a dashboard in the carousel is selected, it is then displayed with all its visuals. This is illustrated by 4 in Figure – Analytics Initial View. By default there will be an “Overview Dashboard” available in the analytics user’s dashboard.

For an analytics user to create a dashboard, they click the Manage Dashboards button, illustrated by 5 in Figure – Analytics Initial View. The very first time the analytics user accesses this view, it will contain a single pre-created default dashboard, and look similar to Figure – Initial Manage Dashboard. However, after the analytics user creates further dashboards containing visuals the view will look similar to Figure – Manage Dashboards.

NOTE: Each analytics user is able to create dashboards. The dashboards they create are applicable to them alone. This therefore implies that each analytics user in a customer’s account may have their own set of personalized, customized dashboards and associated visuals.

There are two ways in which an analytics user may add a dashboard to their My Dashboards view. The first way is to select a preconfigured template. These are located in the Dashboard Templates tab (illustrated by 2 in Figure – Dashboard Templates) that is made clickable when the analytics user clicks Manage Dashboards (illustrated by 1 in Figure – Dashboard Templates). Figure – Dashboard Templates is an example of this view containing all possible templates, illustrated by 3 an analytics user may choose. The displayed templates may be filtered by clicking the tags as illustrated by 4 in Figure – Dashboard Templates.

The current templates available are:

1. Overview Dashboard
2. Agents Dashboard
3. Agents Performance Dashboard
4. Interactions Dashboard
5. Interactions Journey Dashboard
6. Customer Experience Dashboard
7. Business Risk Dashboard
8. Customer Satisfaction Dashboard
9. CX Self Service Dashboard
10. Phrase Hit Analysis Dashboard

Should an analytics user wish to make use of one of the templates and attach it to their My Dashboards page, they would click the desired template. The selected dashboard will then be added to the My Configured Dashboards’ view, and the analytics user will be automatically navigated to this view. For instance, clicking on the Interaction Dashboard template will result in a view similar to that in Figure – Selected Template being rendered.

The analytics user may go ahead and change the dashboard and its visuals illustrated by 2 in Figure – Selected Template to meet their needs using this template as a basis, or they can merely save it by clicking the Save Dashboard button, as illustrated by 1 in by Figure – Selected Template. Doing so adds the dashboard and its associated visuals to their My Dashboards view. Editing the dashboard is described further on in this document where creating a dashboard is discussed. If the analytics user does not want to edit or save the selected template, they would click the Close Editor button as illustrated by 3 in by Figure – Selected Template. Should the analytics user click on My Dashboards, they should see their newly added dashboard.

Before discussing the second way in which an analytics user may create a dashboard, let us discuss the purpose and features of each of the above-mentioned dashboard templates.

1. 1. Overview Dashboard
      The main goal of the Overview Dashboard is to provide key insights into Conversation Analytics. The dashboard serves as a central hub for viewing important KPIs related to Conversation Analytics and aims to offer a high-level summary of performance and key operational metrics, such as Agent Performance and Call Handling Statistics.
      The Overview Dashboard consolidates various metrics like Call Interactions, Automated Quality Assurance (AQA) Scorecard Performance, Overtalk, Silence, and various other statistics into a single, easy-to-navigate view. The aim is to facilitate quick decision-making by providing easy-to-read visuals that highlight areas that need attention or improvement and allowing managers and decision-makers to identify trends, outliers, and opportunities for training or operational improvement.
      The purpose of each visual in this dashboard is;
      • Overview KPI Card: Provides an at-a-glance summary of key metrics – Interactions, Agent Sentiment, and Caller Sentiment. This enables analytics users to compare metrics against Month to Date (MTD), Previous Month (Prev Month), and the change from one month to the next (MoM Change).
      • Interactions: In Conversation Analytics, Interactions are the back-and-forth exchanges across audio, email, and chat. These conversations are analyzed to understand things like how happy or frustrated someone is, what they’re trying to ask or solve, and how well the conversation is going. This helps businesses improve their customer service and make conversations smoother.
      • Agent Sentiment: It looks at how the agent’s words or responses come across — whether they’re friendly, neutral, frustrated, helpful, or anything in between.
      • Caller Sentiment: Refers to the caller’s perspective and is determined by analyzing the language and expressions the caller uses, which can reveal if they are feeling happy, frustrated, confused, angry, or satisfied.
      • Interactions by Agent Group Bar Chart: This visual allows for the easy comparison of interaction volumes across different Agent Groups. Analytics users can quickly see which Agent Groups are handling more interactions. By visualizing the data in this way, analytics users can identify which Agent Groups are more efficient or effective based on the number of interactions they manage. This can help in assessing workload distribution and performance metrics
        
      • Selected Metric Value by Date with Forecasting Trend Line Chart: Using the KPI Parameter Filter will allow an analytics user to see how various KPI Parameters change over a specified date range. This can help identify patterns, seasonality, or long-term trends. This can also be helpful in identifying areas needing improvement.
        
      • AQA Score by Date and Scorecard Trend Line Chart: This visual compares AQA (Automatic Quality Assurance) Scores per Scorecard across different dates, allowing analytics users to monitor changes in AQA scores for each scorecard, assessing how quality assessments evolve and determining the effectiveness of training or process improvements. The chart enables the identification of consistent trends or anomalies in AQA scores across different scorecards, highlighting areas of concern or improvement within interactions.
        
        To allow analytics users to easily navigate from high-level insights to detailed analysis, the Overview Dashboard flow is as follows. Starting with the KPI Card – the purpose is to provide a high-level view of key metrics and indicate metrics needing deeper analysis. For example, if metrics decrease month-on-month, it signals a need for further investigation.
        Interactions by Agent Group then displays the number of interactions per Agent Group. Clicking on a specific Agent Group filters the KPI card and other visuals on the dashboard to focus on that Agent Group, helping identify which Agent Group’s performance is impacting the month-on-month metric changes.
        Next the KPI Parameter Filtered by Date visual shows trends of selected metrics over a specified date range. When an Agent Group is selected, this visual shows the trend for that specific Agent group, highlighting increases and decreases in metrics.
        The AQA Scorecard Scores visuals allows users to compare AQA scores against KPI parameters. Low scores on certain days can be analyzed in context, e.g., correlating high interaction spikes or short call durations. Selecting an Agent Group will visualize the scorecard scores for that Agent Group over the same date period.
        By allowing users to interact with the dashboard in this way, the tool provides a flexible, real-time approach to monitoring and improving customer interactions. It empowers users to dive into specific areas, identify patterns, and respond proactively to issues, enhancing decision-making, training, and overall performance.
   2. Agents Dashboard
      The main goal of the Agents Dashboard is to provide key insights into Conversation Analytics for specific Agents. It aims to offer a high-level summary of performance- and key operational metrics (such as Agent Performance and Call Handling Statistics) with the ability to easily select an Agent and assess the statistics for the selected Agent.
      • Agent KPI Card: Provides an at-a-glance summary of Agent Sentiment, the Agents that have improved and regressed the most, Positive Engagements, and Negative Engagements, as well as a summary of the Interactions. This specifically looks at Interactions per Words, Interactions per Agent, Highest number of Interactions by an Agent, and Lowest number of Interactions by an Agent. The KPI card provides an immediate overview of each Agent’s performance metrics, allowing managers and stakeholders to quickly assess how individual Agents are performing in terms of sentiment and engagement.
        
        • Interactions per Workday: Refers to the total number of exchanges between an agent and a customer that take place during a standard 8-hour workday (Monday – Friday).
        • Interactions average: The average number of interactions that took place in the selected date range.
        • Highest Interactions: Refers to the agent that handled the greatest number of calls within the selected date range.
        • Lowest Interactions: Refers to the agent that handled the fewest number of calls within the selected date range.
        • Agent Sentiment: Refers to the emotional tone or attitude of an agent during a conversation.
          • Most Improved: Most Improved refers to the agent who has shown the greatest positive change in sentiment compared to the previous month’s sentiment value. This could indicate that the agent is becoming more confident, friendly, or effective in their communication, leading to improved customer experiences and better overall sentiment in their interactions.
          • Most Regressed: Most Regressed refers to the agent whose sentiment has worsened compared to the previous month’s sentiment value, resulting in more negative or less effective interactions. This may suggest issues such as increased frustration, burnout, or communication challenges, which could affect the quality of customer service.
          • Negative Engagements: Refers to interactions where the agent’s tone or responses are perceived as frustrated, unhelpful, or disengaged, leading to a negative experience for the customer. These types of interactions can indicate dissatisfaction or tension between the agent and customer, requiring further attention or coaching.
          • Positive Engagements: Refers to interactions where the agent’s tone and responses are warm, supportive, and solution-focused, leading to a positive customer experience. These interactions often reflect an agent’s ability to maintain professionalism and empathy, creating a more satisfying experience for the customer.
      • Interactions by Agent Bar with drilldown for Audio Duration Bins and Audio Duration (Mins): This visual allows for the straightforward comparison of the number of interactions handled by each Agent. This helps identify high-performing Agents as well as those who may need additional support or training. By visualizing interactions over time, managers can spot trends in individual Agent performance, such as consistent increases or decreases in interactions, which can indicate changes in efficiency or engagement. Drilling down on specific Agents allows analytics users to see additional information regarding the average audio duration across their interactions.
        
      • Interactions and Agent Sentiment by Date: Allows analytics users to compare different categories or groups. The added sentiment line shows how the sentiment changes over time, which allows for the identification of trends.
      • Productive Time Split Chart: This chart provides a clear overview of how each Agent spends their time each 8-hour work day. By comparing the segments of Productive vs. Unproductive Time, managers can quickly identify which Agents are maximizing their productive time and which may be spending too much time in non-productive activities. Agents with a high proportion of productive talk time compared to unproductive time can be recognized as more efficient, while those with higher idle or unproductive time may need support or training.
        
      • Productive Time: This represents the time agents are actively engaged in calls.
      • Unproductive Time: Represents periods when agents are on calls but not actively engaging with customers. This could include:
        Holding for Information: Waiting for a supervisor or accessing customer data.
        Internal System Navigation: Using internal tools or software during a call.
        Customer Silence: Periods where the customer is silent, perhaps thinking or on hold themselves.
        Idle Time: Represents any time agents spend not actively on calls.

        The Agents Dashboard‘s flow enables users to effectively analyze individual Agent performance, identify trends, and make data-driven decisions to enhance productivity and scheduling in conversation analytics.

        The KPI Card provides a high-level overview of key performance metrics, which highlights metrics needing further analysis, e.g., a month-on-month decrease prompts investigation into underlying causes.

        Moving to Interactions by Agent – this chart displays the number of interactions for each Agent. Clicking on a specific Agent filters the KPI card and other visuals, allowing for targeted analysis of that Agent’s metrics, helping to identify who may be affecting overall performance.

        Then the aggregated Interactions and Agent Sentiment chart shows daily totals of interactions and sentiment for all Agents. Selecting an Agent visualizes their specific interactions and sentiment for the selected date period. A drill-down feature provides hourly data, helping to identify patterns such as call volume spikes during lunch and corresponding low sentiment, indicating potential staffing issues.

        The last visual on this dashboard, the Productive Time Split chart, illustrates how Agents utilize their time during an 8-hour workday. Selecting a specific Agent will update the metrics to show a breakdown of that Agent’s time spent on calls (Productive/Talk Time), Unproductive Time (Silence/Hold Time), and Idle time.

   3. Agent Performance Dashboard
      The aim of the Agent Performance Dashboard is to provide a detailed overview of the AQA (Automated Quality Assurance) Scores for each Agent, enabling managers and stakeholders to assess individual performance effectively. The dashboard not only displays overall scores but also breaks down the results by specific questions and sections, allowing for a clear understanding of strengths and areas for improvement. Furthermore, the dashboard features an interactive trend analysis component. When a specific Agent is selected, analytics users can visualize their performance trends over time. This functionality allows for easy identification of patterns, such as improvements or declines in scores, correlating with changes in training, process adjustments, or other operational factors.
      • AQA Score by Section and Question Table: This visual serves as a quick overview of the overall AQA performance across various aspects of the interaction. It helps identify areas where Agents may need further training or coaching to improve their performance and ensure customer satisfaction.
        
      • Agent Performance KPI Card: This KPI Card provides a quick snapshot of Agent performance, focusing on their Quality Assurance (QA) scores. It helps to identify areas where the Agent excels and where they may need improvement. Specific metrics focused on in this KPI Card include the overall AQA Score, AQA Score MTD, AQA Score MoM %, Best AQA, Worst AQA, Worst Question, Best Section, Best Question, and Worst Section. The overall AQA score indicates the overall quality of Agent Performance whereas some of the other metrics highlight the Agent with the best AQA score and the Agent with the worst AQA score. Supervisors can use this KPI Card to identify specific areas where an Agent needs improvement and tailor their coaching sessions accordingly.
        
        • AQA Score: This is an agent’s or a group of agents’ overall score for the selected timeframe, based on the configured QA Scorecards.
        • AQA Score MTD: This represents the agent’s average QA score for the current month-to-date. If a single question is selected, this will update to show a value for that specific question.
        • AQA Score MoM%: This shows the percentage change in the agent’s QA score compared to the previous month. In this case, the score has decreased by 3.06%.
        • Best AQA: Refers to the agent that scored the highest across all scorecard questions or for a specific question.
        • Worst AQA: Refers to the agent that scored the lowest across all scorecard questions or for a specific question.
        • Best Question: Indicates the specific questions on the QA scorecard where the agent(s) performed the best.
        • Worst Question: Indicates the specific questions on the QA scorecard where the agent(s) performed the worst.
        • Best Section: Shows the sections within the QA scorecard where the agent(s) scored the highest.
        • Worst Section: Shows the sections within the QA scorecard where the agent(s) scored the lowest.
      • AQA Score by Agent Bar Chart: Provides a clear visual comparison of AQA (Automated Quality Assurance) scores across different Agents. This helps identify high performers and those who may need additional support or training. Additionally, this chart can reveal patterns in performance over time, allowing managers to track improvements or declines in quality scores for individual Agents.
        
      • AQA Score by Date with Forecasting Chart: Allows stakeholders to monitor changes in AQA scores across specific dates, helping to identify trends in Agent performance over time. The chart can reveal patterns, such as seasonal fluctuations or recurring issues, indicating when performance may dip or improve, which can be crucial for planning and resource allocation. If any changes are made, e.g., new training programs or process adjustments, the trend line chart can help assess their effectiveness by comparing scores before and after the implementation.
        
      • Interactions and Caller Sentiment by Date (with Drilldown for Hour of Day) Chart: The combined display of interaction volume and sentiment allows for the analysis of whether changes in interaction volume directly impact customer sentiment. For instance, a sudden spike in interactions might be associated with a decrease in sentiment, suggesting that agents are struggling to keep up with demand. The added drilldown functionality offers a more granular view of the number of interactions at specific hours of the day along with the corresponding Caller Sentiment.
        
      • Productive Time Split Chart: This chart provides a clear overview of how each Agent spends their time each day. By comparing the segments of Productive vs. Unproductive Time, managers can quickly identify which Agents are maximizing their productive time and which may be spending too much time in non-productive activities. Agents with a high proportion of productive talk time compared to unproductive time can be recognized as more efficient, while those with higher idle or unproductive time may need support or training.
        
        Productive Time: This represents the time agents are actively engaged in calls.
        Unproductive Time: Represents periods when agents are on calls but not actively engaging with customers. This could include:
        Holding for Information: Waiting for a supervisor or accessing customer data.
        Internal System Navigation: Using internal tools or software during a call.
        Customer Silence: Periods where the customer is silent, perhaps thinking or on hold themselves.
        Idle Time: Represents any time agents spend not actively on calls.

        The Agent Performance Dashboard provides a comprehensive and dynamic view of Agent quality and efficiency, allowing managers to easily monitor performance and identify areas for improvement. By selecting a specific Agent, the dashboard updates to display tailored metrics relevant to that individual, ensuring focused insights.

        The AQA scores across different sections and questions offer a detailed breakdown of the Agent’s performance in various areas. This allows managers to pinpoint specific strengths and weaknesses, helping to identify where further training or coaching might be needed. The table provides a quick snapshot of the overall quality of interactions, as well as more granular insights into individual aspects of the conversation.

        For a more focused look at performance, the KPI card highlights critical metrics such as the overall AQA score, MTD and MoM percentage changes, as well as the best and worst AQA scores. Selecting an Agent updates the card to reflect their specific performance, showcasing both areas of excellence, such as the best question or section, and areas for improvement, such as the worst question or section. This enables supervisors to tailor coaching efforts based on the individual’s strengths and areas where they may be struggling.

        The bar chart offers a side-by-side comparison of AQA scores across all Agents, making it easy to see where the selected Agent stands relative to others. It can also track performance trends over time, helping managers identify consistent top performers or those needing additional support.

        To better understand performance over time, the trend line chart tracks AQA scores by date, highlighting any fluctuations or seasonal trends. Selecting an Agent updates the chart to show their individual score trends, helping managers assess whether changes in performance are due to external factors or internal adjustments, such as new training programs or process changes.

        The interactions and caller sentiment chart allows managers to explore the relationship between interaction volume and customer sentiment. By drilling down to specific hours of the day, this visual helps identify if high volumes of interactions are impacting sentiment negatively. The updated view for a specific Agent allows managers to see whether an increase in workload correlates with a decline in sentiment for that individual.

        Finally, the productive time chart displays how the selected Agent spends their time throughout the day, distinguishing between productive and unproductive time. This allows managers to quickly identify areas where the Agent could improve efficiency and focus more on productive tasks, providing a clear basis for coaching and performance optimization. It is important to understand how the data in this visualization is aggregated and how it can be filtered for more granular analysis. The metrics shown (Productive Time, Unproductive Time, and Idle Time) represent the combined activity of all agents on a given day. This means that for any selected date:

        Total Time: The sum of all three metrics will equal 8 hours multiplied by the number of agents working that day.
        Agent Filtering: You can filter the data to analyze the performance of individual agents. When a single agent is selected, the metrics will reflect only that agent’s activity, totaling 8 hours for their workday (Monday – Friday). This functionality allows for both high-level overview of team performance and detailed analysis of individual agent activity.

        Together, these visuals form a dynamic, easy-to-navigate dashboard that allows supervisors to monitor and improve Agent performance with data-driven insights tailored to each individual.

   4. Interactions Dashboard
      The Interactions Dashboard allows analytics users to view a comprehensive summary of customer interactions over a specific time period, enabling them to identify and analyze trends related to spikes in interaction volume. Analytics users can drill down into specific timeframes to uncover patterns in interaction frequency, which can highlight periods of increased customer inquiries or concerns.
      • Interactions KPI Card: This KPI Card provides a quick overview of all interaction metrics. It helps to assess Agent productivity, engagement quality, and overall effectiveness. The KPI Card highlights the total number of Interactions, the number of Short Calls, Positive Engagements, Negative Engagements, Productive Time, Unproductive Time, and showcases other metrics such as Overtalk and Silence that can be used to identify areas where training is required.
        
        Interactions: Shows the total number of interactions within the selected date range.
        Short Calls: The number of calls that were shorter than a defined threshold, which is 60 seconds.
        Distinct Agents for Date Period: This shows the total number of unique agents who handled calls during this period.
        Avg Agents per Workday: This is the average number of agents working on each day within the selected date range. This helps understand staffing levels and potential fluctuations in agent availability. Workday refers to Monday – Friday, i.e., the metric excludes Saturday and Sunday.
        Total Available Time (HH:MM): This represents the total time agents were scheduled to work during this period (8 hours per day, Monday – Friday), summed across all agents for the selected date range.
        Productive Time (HH:MM): This is the total time agents spend actively engaged in calls with customers. This is a key metric for measuring agent productivity and efficiency.
        Unproductive Time (HH:MM): This refers to the time agents were on calls but not actively interacting with customers. This could include time spent on hold, navigating systems, or waiting for information.
        Idle Time (HH:MM): This represents the time agents were not on calls. This could include time spent between calls, on breaks, in meetings, or doing administrative tasks.
      • Interactions by Date Graph: The trend graph allows analytics users to visualize how interactions change over time. This can help identify patterns, such as peak interaction periods as well as sudden shifts in interactions. By adding forecasting, it helps analytics users anticipate future customer behaviors and trends based on historical data, allowing for better planning and decision-making.
        
      • Agent Sentiment and Caller Sentiment by Month and Day of Month Graph: Allows analytics users to visualize how Agent and Caller sentiment change over time. This can help identify patterns, such as seasonal trends in customer sentiment as well as sudden shifts in sentiment.
      • Interactions by Topic Column Chart: This chart allows analytic users to easily compare the frequency or volume of different topics within conversations. This helps identify which issues are most prevalent and which may require more attention. By visualizing how topics change over time, organizations can spot emerging trends, such as rising customer concerns or shifting interests.
        
      • Interactions by Audio Duration Bin with drilldown for Audio Duration Minutes Chart: By plotting audio duration over time, teams can analyze trends in call length on a per Agent basis. This can reveal patterns, such as whether calls are getting longer due to increased complexity or shorter due to improved efficiency.
        
      • Call Listing Table: Table displaying all the calls in the selected time period. Metrics shown in this table include Audio Duration, Agent, AQA Score, Silence, Overtalk, Agent Sentiment, and Caller Sentiment. Analytics users are able to select a specific call which will update all other metrics on the dashboard.
        The Interactions Dashboard provides a comprehensive and dynamic view of customer interactions, allowing analytic users to monitor key metrics, analyze trends, and make data-driven decisions. When analytic users interact with various visuals on the dashboard, the data updates in real time, providing tailored insights based on their selections.

        The KPI Card offers a quick snapshot of overall interaction metrics such as total interactions, short calls, positive and negative engagements, productive and unproductive time, overtalk, and silence.

        The Interactions by Date graph visualizes how interactions evolve over time and includes forecasting to predict future trends. If an analytic user clicks on a specific date range or a peak interaction period in the graph, the rest of the dashboard will update to reflect data for that selected timeframe. For example, selecting a spike in interactions will update other metrics, like sentiment, agent performance, or topic frequency, to show how those elements were affected. This allows analytic users to see how shifts in interaction volume correlate with other key metrics, helping to better understand patterns and plan for future periods.

        The sentiment trend graph tracks how both Agent and Caller Sentiment change over time. If an analytic user clicks on a specific dip or peak in sentiment, the dashboard updates to show detailed insights related to that period. For instance, selecting a drop in sentiment might trigger updates that show how specific topics, agents, or customer concerns influenced the shift. This enables managers to identify patterns in sentiment and take action to address issues or capitalize on positive changes.

        The chart showing Interactions by Topic allows analytic users to see the frequency of different topics within interactions. Clicking on a specific topic, such as “Billing Issues,” filters the dashboard to focus on interactions related to that issue. Other visuals will update to reflect the data for that selected topic, showing how it compares in terms of sentiment, call duration, and agent performance. This helps identify prevalent concerns, emerging trends, or areas requiring more attention and support.

        The Audio Duration Bin chart tracks call length over time. By drilling down into a specific duration bin, such as calls lasting 5-10 minutes, the dashboard updates to show data specific to that call length. Analytic users can analyze which Agents are handling these calls, whether the calls are longer due to increased complexity or shorter due to improved efficiency, and how other metrics such as overtalk or silence are affected. This helps teams understand if changes in call duration are tied to performance trends or process efficiencies.

        Finally, the Call Listing table displays all interactions within the selected time period. When an analytic user selects a specific call from the table, all the other visuals on the dashboard update to show detailed data for that interaction. For example, selecting a call with low sentiment may trigger updates in the sentiment graphs, showing how it impacted the Agent and Caller experience. The analytic user can also drill down into metrics like the AQA score or Audio Duration to better understand the factors that contributed to the call’s outcome.

        By allowing analytic users to interact with the dashboard in this way, the tool provides a flexible, real-time approach to monitoring and improving customer interactions. It empowers users to dive into specific areas, identify patterns, and respond proactively to issues, enhancing decision-making, training, and overall performance.

   5. Interactions Journey Dashboard
      The Interactions Journey Dashboard provides a comprehensive view of customer call interactions, empowering Agent Groups to enhance service quality and optimize performance. Featuring a Call Listing Table, AQA Scorecard, and Chat With Data. The dashboard enables users to analyze key metrics such as call length, sentiment, and AQA scores. By allowing users to drill down into specific calls, the dashboard reveals valuable insights into Agent performance, customer sentiment, and common inquiry trends. This data-driven approach facilitates informed decision-making, targeted training, and continuous improvement in customer support operations, ultimately driving better customer experiences and outcomes.
      • Chat With Data: Allows users to run a query on the selected call and gain additional context and information based on AI findings.
        
      • Call Listing Table: Table displaying all the calls in the selected time period. Metrics shown in this table include Call Length, AQA Score, Agent, Audio Duration, Silence, Overtalk, Agent Sentiment, and Caller Sentiment. Analytics users are able to select a specific call which will update all other metrics on the dashboard.
        
      • AQA Score by Section and Question: This visual serves as a quick overview of the overall AQA performance across various aspects of the interaction. It helps identify areas where Agents may need further training or coaching to improve their performance and ensure customer satisfaction.
        The Interactions Journey Dashboard is designed with an intuitive flow that allows users to seamlessly explore call data, uncover insights, and make informed decisions based on detailed analysis. The journey begins with the Call Listing Table, which provides a sortable and filterable list of all calls from the selected time period. Analytics users can click on a specific call, and all visuals will update to display metrics related to that particular interaction.

        Once a call is selected, the AQA Score by Section and Question visual updates to show the overall AQA score for the selected call, along with a detailed breakdown of scores for each question. This breakdown allows analytics users to analyze how the AQA score aligns with other metrics, providing a clear understanding of the Agent’s performance during that call.

        In addition to these visuals, analytics users can further explore the selected interaction through the Chat with Data feature. By inputting specific queries, analytics users can leverage AI-driven insights to uncover patterns or gather additional context about the call, enabling a deeper understanding of the factors influencing performance and customer sentiment. Analytics users are also able to leverage this feature to ask for action steps or follow-up activities that need to be performed after the conclusion of the call.

        This seamless flow enables analytics users to move from a high-level overview to detailed call-specific insights, facilitating a comprehensive analysis of each interaction.

   6. Customer Experience Dashboard
      The Customer Experience Dashboard offers a holistic view of customer interactions, leveraging conversation analytics to assess the quality and effectiveness of communication. It highlights key metrics such as sentiment analysis and call outcomes, enabling organizations to gauge overall satisfaction and engagement. By tracking trends in Agent performance and identifying recurring themes in customer inquiries, the dashboard empowers stakeholders to make data-driven decisions that enhance service delivery. Ultimately, this dashboard serves as a vital tool for improving customer experiences, fostering loyalty, and driving continuous improvement across all interactions.
      • Customer Experience Score Chart: Radar charts allow for the representation of multiple dimensions of customer experience, as it relates to soft skills, simultaneously. Each axis represents different aspects of AQA (Automated Quality Assurance) scores. This chart clearly shows imbalances in performance across different criteria, helping teams focus on specific areas for development.
        
      • Agent Sentiment and Caller Sentiment by Audio Duration Bin Chart: By comparing Caller Sentiment (how customers feel) with Agent Sentiment (how Agents perceive the interaction), the radar chart can reveal discrepancies. This dual perspective is essential for understanding the overall tone of conversations. For example, if a caller expresses frustration while an Agent feels positive, it may indicate a misalignment that needs addressing. Over time, the radar chart can help users track changes in sentiment, helping organizations gauge the effectiveness of training, process changes, or new initiatives aimed at improving customer experience.
        
      • Customer Experience Score Issues by Date Chart: The stacked column chart visually represents the count of each issue type on a given date. By hovering over a specific column, users can gain detailed insights into the composition of issues for that particular day. The visual helps identify periods with a high volume of customer issues, allowing for targeted analysis and intervention. It can reveal potential correlations between different issue types. For example, an increase in escalations might be linked to a rise in customer confusion. By comparing data before and after implementing changes, the dashboard can assess their impact on customer experience.
        
      • Interactions Time Breakdown by Date Chart: Using a stacked column chart allows for easy comparison of these three metrics (Total Talk Time vs Total Hold Time vs Total Overtalk Time) side by side. The data is aggregated across all agents by default, but can be filtered to display individual agent activity. Stakeholders can quickly assess how each time metric relates to the others, helping identify patterns or discrepancies. Over time, the chart can highlight trends in customer interactions. For example, if hold time is increasing while talk time decreases, it may indicate inefficiencies in the support process. Additionally, by visualizing these metrics, the chart can help monitor the performance of customer service representatives and overall service efficiency, facilitating targeted training or process improvements.
        
        Total Talk Time: This represents the total duration of active conversations between agents and customers. When viewing aggregated data, it reflects the combined talk time of all agents on a given day.
        Total Hold Time: This measures the total time customers are placed on hold during calls. This metric can highlight potential inefficiencies in call handling or access to information.
        Total Overtalk Time: This indicates instances where simultaneous speaking occurs, either with the agent interrupting the customer or both parties talking over each other. Monitoring this can help improve communication clarity and customer experience.

        The Customer Experience Dashboard flow provides a comprehensive overview of customer experience and Agent performance metrics. It combines soft skill assessments with operational insights, allowing analytics users to identify training needs, analyze sentiment discrepancies, and evaluate productivity across interactions.

        Starting with the Customer Experience Performance radar chart, this visual focuses on Customer Confusion, Call Backs, Profanity, Escalation, and Transfers. The ‘Topics’ in the Customer Experience Score visual are currently static, meaning analytics users are unable to modify them.

        Next, the Agent Sentiment vs. Caller Sentiment by Audio Duration Bins radar chart reveals discrepancies in sentiment between Agents and Callers across different call durations. This visual highlights instances where Agent Sentiment is significantly lower than Caller Sentiment, indicating areas where additional training may be necessary.

        Following that, the Issue Ranking by Date Time chart is designed to pinpoint specific days and interactions where certain topics are most frequently addressed. This visual allows users to track how various issues evolve over time and analyze the context of those calls.

        Finally, the Interactions Time Breakdown by Date graph shifts the focus to operational metrics. This chart compares Hold Time with overall Talk Time and Overtalk Time, enabling users to assess system efficiency and determine whether Agents require further training. It provides insights into Agent productivity on specific workdays.

   7. Business Risk Dashboard
      The Business Risk Dashboard provides a comprehensive view of conversation analytics, focusing on the identification and fluctuation of key issues/risks over time. By visualizing the frequency and impact of specific issues on different days, the dashboard allows stakeholders to track trends and patterns in customer interactions. Additionally, it analyzes how these issues affect both Agent- and Caller Sentiment, highlighting correlations that can inform strategic decision-making. This integrated approach empowers organizations to proactively address risks, enhance customer experience, and improve Agent performance.
      • Business Risk Rates KPI Cards: Provides an at-a-glance summary of key issues/risks, which allows users to view the Month to Date (MTD) metrics, view metrics from the Previous Month (Prev Month), and see the Month on Month (MoM) Change.
        
        Escalation: A customer issue that requires transfer to a supervisor or specialized team because the first agent is unable to resolve it.
        Cancellations: A customer expresses their intent to discontinue a product, service, or order during the conversation.
        Formal Complaint: A customer actively initiates a formal complaint process regarding their experience with the company.
        Legal Mention: The customer brings up legal action, regulations, or their legal rights during the interaction.
        Report to Agency: The customer explicitly threatens to involve a regulatory body or consumer protection agency (which varies by region/country) due to their dissatisfaction.
      • Business Risk Rate by Date Chart: This trend line chart provides a holistic view of how these Business Risks increased or decreased over time. This allows users to view various rates and compare for the entire year or drill down to specific dates.
        
      • Interactions by Business Risk and Sentiment (with Drilldown for Agent) Chart: This column chart displays the frequency or severity of various business risks identified in conversations. The line chart displays Agent Sentiment and Caller Sentiment. Overlaying sentiment data on the column chart provides context. It allows stakeholders to observe patterns, such as whether negative sentiment increases in response to specific issues, which can inform strategies for improvement. Together, these charts create a comprehensive view of the conversation analytics, helping stakeholders identify not just what issues are present, but also how they impact sentiment. Identifying trends in sentiment and business risks at the Agent level can highlight areas where specific Agents may need additional training or support. This can further reveal which Agents handle business risks more effectively or demonstrate higher levels of sentiment during conversations.
        
      • Business Risk Call Listing Table: This table shows all calls that occurred during the selected time period and gives users the ability to view a specific call when clicking on the Call Link icon. The table also displays the number of Business Risk Issues that were mentioned on each call, as well as the duration of the call and Agent who handled the call.
        This structured flow ensures that analytics users can effectively navigate the Business Risk Dashboard, leveraging its features to maximize understanding and drive strategic actions.

        Analytics users begin by reviewing the Business Risk Rates KPI cards, which provide essential Month to Date (MTD), Previous Month (Prev Month), and Month on Month (MoM) change metrics. This quick summary helps analytics users identify immediate concerns or areas needing attention, setting the context for deeper analysis.

        Analytics users then navigate to the Business Risk Rate by Date chart to visualize how business risks have fluctuated over time. This visual allows analytics users to compare various rates for the entire year or drill down to specific dates, allowing them to identify patterns or anomalies in risk levels.

        Next, analytics users examine the Interactions by Business Risk and Sentiment chart, which combines the frequency/severity of identified business risks with Agent and Caller Sentiment data. The drill down feature allows analytics users to analyze individual Agent performance, helping identify those who effectively manage risks or require further training based on sentiment trends.

        Finally, analytics users access the Call Listing table, which displays all calls that occurred during the selected time period. Analytics users can click on the Call Link icon to view specific calls and see the number of business risks mentioned, enabling the granular analysis of individual interactions. This table serves as a resource for analytics users to investigate particular calls related to high-risk issues, facilitating follow-up actions or discussions.

   8. Customer Satisfaction Dashboard
      The Customer Satisfaction Dashboard provides a comprehensive view of customer sentiment regarding a company’s products or services, with the primary goal of helping organizations monitor and improve customer experiences. It aggregates key metrics to assess customer satisfaction, including:
      • Customer Satisfaction Score (CSAT): Measures overall customer satisfaction with specific interactions or products.
      • Net Promoter Score (NPS): Evaluates customer loyalty and their likelihood of recommending the company to others.
      • Customer Effort Score (CES): Determines the level of effort required by customers to resolve issues or complete tasks
        By visualizing these metrics over time, the dashboard enables the identification of trends and highlights areas that may need attention. It also allows for deeper analysis by customer segment, product category, or geographic region, making it easier to pinpoint opportunities for improvement and ensure a better customer experience.

        The Customer Satisfaction Score (CSAT) quantifies the level of satisfaction a customer expresses regarding a specific interaction, product, or service. CSAT is calculated based on a specific topic in the CallCabinet portal that addresses the question: “How would you rate your satisfaction with us?”  Responses are commonly captured using a numerical rating scale – in this case a 5-point scale ranging from 1 (“Very Dissatisfied”) to 5 (“Very Satisfied”). The system analyzes customer responses by identifying pre-defined phrases within standardized phrase packs. These phrases are associated with distinct satisfaction levels and contribute to the CSAT score based on their assigned weighting. Examples include:
        Very Satisfied (Score 5), For example “exceptionally good service ~4”
        Satisfied (Score 4), For example “satisfied results ~3”
        Neutral (Score 3), For example “bland service ~3”
        Dissatisfied (Score 2), For example “insufficient standards ~3”
        Very Dissatisfied (Score 1), For example “deeply regret using ~4”
        Each response category is scored based on what is found in the call transcript.

        Calculation:
        CSAT = ((CSAT Very Satisfied Calls x 5) + (CSAT Satisfied Calls x 4) + (CSAT Neutral Calls x 3) + (CSAT Dissatisfied Calls x 2) + (CSAT Very Dissatisfied Calls x 1)) / Total Number of Responses

        The “Total Number of Responses” refers to the number of calls in which any of the phrases for CSAT are picked up. When none of the phrases are picked up, that call is ignored.

        CSAT is most effectively employed to gauge satisfaction with specific, transactional interactions such as post-support ticket resolution, immediately after a purchase, or following an onboarding process. Timely deployment of CSAT surveys is crucial to capture accurate feedback related to the specific event.

        Customer Satisfaction Score Benchmark (CSAT)

        Rating Category	Score Range	Interpretation
        Good	Above 70%	Strong to exceptional customer satisfaction
        Average	60% to 70%	Industry standard performance
        Poor	Below 60%	Improvement needed
        Industry Average	60% to 70%	Benchmark across all industries

        In highly competitive industries like SaaS, benchmarks tend to be higher, with good scores typically above 70%.

        The Net Promoter Score (NPS) is a key metric used to gauge customer loyalty and advocacy by assessing the likelihood of customers recommending a business, product, or service to others. Net Promoter Score (NPS) is calculated based on customer responses to the fundamental question: “How likely are you to recommend us?” In the CallCabinet portal, each of these NPS categories is established as a distinct topic. Phrase packs are then linked to these topics to identify relevant customer feedback within conversations.

        Responses are commonly captured using a numerical rating scale – in this case a 3-point scale ranging from 1 (“Detractors”) to 3 (“Promoters”).
        Definitions and examples of phrases associated with each group include:
        Promoters (Score 3): These customers are highly satisfied and enthusiastic about the company, demonstrating strong loyalty and a high propensity to recommend it to others. They are considered brand advocates. For Example, “totally impressed quality ~4”
        Passives (Score 2): These customers are generally satisfied but not particularly enthusiastic. They are unlikely to actively promote the company but are also not at high risk of churn. For Example, “average sort experience ~4”
        Detractors (Score 1): These customers are dissatisfied and at risk of negatively impacting the brand through negative word-of-mouth. They represent areas needing immediate attention and improvement. For Example, “diabolical service throughout ~4”
        Each response category is then scored based on what is found in the call transcript.

        Calculation:
        NPS = (NPS Promoters / Total Number of Responses) – (NPS Detractors / Total Number of Responses)
        Note: “Total Number of Responses” refers to the number of calls where any of the phrases for NPS are picked up. When none of the phrases are picked up, that call is ignored.
        Based on research and industry standards, the calculation for NPS does not consider “NPS Passives”.

        NPS is most valuable for measuring overall customer loyalty and the health of long-term customer relationships. It is typically deployed through surveys conducted on a periodic basis, such as quarterly or bi-annually, to track trends in customer sentiment over time.

        Net Promoter Score Benchmark (NPS)

        Rating Category	Score Range (Raw: -100 to +100)	Score Range (Decimal: -1 to +1)	Interpretation
        Good	Above 30	Above +0.30	Strong customer loyalty and advocacy
        Average	0 to +30	0 to +0.30	Industry standard performance
        Poor	Below 0	Below 0	Improvement needed, more detractors than promoters
        Industry Average	+17	+0.17	Benchmark across all industries

        NPS varies significantly by industry. Specialty stores can average around +56 while internet services might be as low as –3. The decimal format applies when calculating (% Promoters – % Detractors) without multiplying by 100.

        The Customer Effort Score (CES)
        Definition: Customer Effort Score (CES) is a metric that quantifies the level of effort a customer perceives they have to exert to resolve an issue, complete a task, or utilize a product or service. It focuses on minimizing friction in the customer experience. The CES is derived from customer responses to a question designed to gauge the ease of their interaction, such as: “How easy was it to interact with us?”
        Responses are commonly captured using a numerical rating scale – in this case a 5-point scale ranging from 1 (“Very Easy”) to 5 (“Very Difficult”). Customer feedback is then categorized into five distinct levels of effort; each associated with specific phrases identified in the conversation:
        Very Easy (Score 1), For Example, “zero difficulties whatsoever ~4”
        Easy (Score 2), For Example, “generally uncomplicated process ~4”
        Neutral (Score 3), For Example, “standard complexity level ~4”
        Difficult (Score 4), For Example, “far too complicated ~4”
        Very Difficult (Score 5), For Example, “insufferably complex ~3”
        Each response category is then scored based on what is found in the call transcript.

        Calculation:
        CES = ((CES Very Easy Calls x 1) + (CES Easy Calls x 2) + (CES Neutral Calls x3) + (CES Difficult Calls x 4) + (CES Very Difficult Calls x 5)) / Total number of responses

        A lower CES score generally indicates a better customer experience, signifying less effort required.
        “Total Number of Responses” refers to the number of calls where any of the phrases for CES are picked up. When none of the phrases are picked up, that call is ignored.

        CES is particularly valuable for evaluating the ease of specific customer interactions such as support inquiries, onboarding processes, and checkout experiences. It helps businesses pinpoint areas where processes can be simplified and the overall customer journey made more effortless.

        Customer Effort Score Benchmark (CES)

        Rating Category	Score Range (1-5 Scale)	Equivalent Percentage	Interpretation
        Good	1.0 to 2.5	0% to 37.5%	Low to reasonable effort required
        Average	2.6 to 3.5	37.5% to 62.5%	Industry standard effort
        Poor	3.6 to 5.0	62.5% to 100%	High to excessive effort required
        Industry Average	3	50%	Benchmark across all industries

        For CES, lower scores/percentages are better as they indicate less customer effort required. This table uses the 1-5 scale where 1 (0%) represents “Very Easy” and 5 (100%) represents “Very Difficult”.

        Percentage Calculation: (Score – 1) / 4 x 100
        For Example:

        High customer effort

        Poor

        4.6 to 5

        90% to 100%

        Excessive effort

      • Customer Satisfaction KPI Card: This visual provides a single KPI card visual that displays the following information for each of the three metrics (CSAT, NPS, and CES): o Current Scores: The most recent value for the respective metric.
        Month on Month (MoM) Percentage Difference: The percentage change in the metric’s value compared to the previous month.
        Positive Engagements: The number of positive feedback instances contributing to the metric.
        Neutral Engagements: The number of neutral feedback instances contributing to the metric.
        Negative Engagements: The number of negative feedback instances contributing to the metric.

        It provides a unified view of the current standing and recent performance trajectory of the core customer satisfaction indicators. This allows for a quick comparison of performance across different metrics and an immediate understanding of whether satisfaction and loyalty are improving or declining. The inclusion of positive, neutral, and negative engagement volume provides context to the score changes.
        

      • Customer Satisfaction Metrics by Agent This visual allows the user to visualize and compare the performance of individual customer service agents across the three customer satisfaction metrics (CSAT, NPS, and CES). This allows for the identification of top-performing agents, areas where individual agents may need additional support, and the overall distribution of customer satisfaction across the service team.

        It provides a granular view of customer satisfaction performance at the individual agent level. This enables targeted interventions, such as recognizing high-performing agents and providing coaching or training to those with lower scores. By comparing metrics across agents, it helps identify best practices and potential inconsistencies in service delivery. This visual supports efforts to improve overall customer satisfaction by focusing on agent-specific performance.
        

      • Interactions by Sentiment Group: illustrates the distribution of customer interactions based on the sentiment expressed within them. This provides a clear understanding of the overall categorization of customer feedback and highlights the proportion of Positive, Neutral, and Negative interactions.

        In the donut chart where the whole circle represents the total number of customer interactions, and each segment represents a sentiment group (Positive, Neutral, Negative). The size of each segment is proportional to the number or percentage of interactions belonging to that sentiment.

        This visual offers a high-level overview of customer sentiment trends within the collected interactions. A larger positive segment indicates a generally positive categorization of customer feedback, while a significant negative segment may signal areas needing attention. The neutral segment provides context on the volume of feedback that is not strongly categorized as positive or negative. This visual helps in quickly assessing the overall customer sentiment categorization and identifying potential areas of concern or success.
        

      • Customer Satisfaction Call Listing: This visual provides a detailed, granular view of recent customer interactions, along with the associated satisfaction scores, and direct access to the underlying conversation data. The data table displays individual customer calls as rows. Key columns include Date/Time of call, Agent involved, CES score, CSAT score, and NPS score. This visual provides a detailed examination of individual customer interactions, allowing for the correlation of satisfaction scores with the actual conversation content.
        
      • Customer Satisfaction Scores by Date: This visual allows the analytics user to visualize the evolution of the overall CSAT, NPS, and CES scores over time. This allows for the identification of trends, patterns, and potential fluctuations in each metric, helping to assess the impact of changes or events on overall customer satisfaction and loyalty. It provides a dynamic and comparative view of customer satisfaction and loyalty over time. By observing the trends of all three metrics simultaneously, analytics users can gain a more comprehensive understanding of customer sentiment and identify any correlations or divergences in their movements. This helps in evaluating the long-term impact of strategies across different facets of customer experience and proactively address any negative trajectories or capitalize on positive momentum.
        
      • Customer Satisfaction by Agent Heat Map: The purpose of this visual is to visualize the performance of individual agents across various satisfaction metrics, allowing for quick identification of high and low performers. The matrix visually represents each agent, with their individual CES, CSAT, and NPS scores clearly presented thereby providing a visual representation of agent performance across key satisfaction indicators, enabling managers to quickly identify top performers, those needing coaching, and potential trends for specific agents or across different metrics.
        
        The Customer Satisfaction Dashboard is structured to provide a comprehensive understanding of customer sentiment and agent performance through a series of interconnected and interactive visuals. It begins with the Customer Satisfaction KPI Card, offering an immediate, high-level snapshot of key satisfaction metrics (CSAT, NPS, CES) and associated positive, neutral (for CSAT/CES), and negative feedback volumes, highlighting current performance and recent trends. Clicking on any of the metrics within the KPI Card will dynamically filter the data across all other visuals on the dashboard, allowing users to focus their analysis on a specific satisfaction indicator.

        To dissect the overall satisfaction at an individual agent level, the dashboard presents the Customer Satisfaction Metrics by Agent bar chart. This visual allows for a direct comparison of agent performance across the core satisfaction metrics, facilitating the identification of top performers and areas for targeted development. This chart, like others, will be updated to reflect the metric selected on the KPI Card.

        Complementing this agent-centric view is the Customer Satisfaction by Agent matrix, providing a consolidated heat map of agent performance across various satisfaction metrics. This enables a quick identification of performance patterns and potential areas of focus, and will also respond to selections made on the KPI Card.

        To understand the broader context of customer feedback, the Interactions by Sentiment Group donut chart illustrates the distribution of customer interactions by positive, neutral, and negative sentiment, offering an immediate grasp of the overall customer sentiment landscape, which will be refined based on the chosen KPI.

        For a granular examination of individual customer interactions, the Customer Satisfaction Call Listing provides a detailed tabular view, linking sentiment and satisfaction scores with specific call data. This allows for in-depth analysis of the drivers behind satisfaction scores, filtered according to the selected metric.

        Finally, the Customer Satisfaction Score by Date trend line chart visualizes the evolution of CSAT, NPS, and CES over time. This enables the identification of trends and the assessment of the impact of operational changes on customer satisfaction and loyalty, with the displayed trend adapting to the metric selected on the KPI Card.This structured and interactive flow of visuals allows users to move from a high-level overview to detailed agent performance and individual interaction analysis, dynamically filtering the data based on their specific area of interest, ultimately providing a holistic and adaptable understanding of customer satisfaction.

   9. CX Self-Service Dashboard
      The CX Self-Service Automation Identification Dashboard provides a clear overview of how customer interactions are being automated to enhance the customer experience and optimize operational efficiency. Its primary goal is to track and identify opportunities for automating customer service tasks, enabling businesses to reduce wait times, improve customer satisfaction, and streamline internal processes. By identifying interactions suitable for self-service automation, the dashboard helps drive cost reduction and improve customer accessibility through optimized channel utilization.
      The dashboard focuses on key self-service and automation areas, including:
      • Customer Self-Service: This includes functions like account information updates, password resets, and order tracking, where customers can independently handle tasks through automated systems without needing agent assistance.
      • Agent-Assisted Tasks: Tasks such as data entry and document retrieval can be enhanced with automation tools that assist agents in providing faster, more accurate service.
      • Back-Office Automation: Critical back-office tasks, including report generation and invoice processing, are automated to reduce manual effort, improve accuracy, and free up resources for more strategic work.
        By monitoring and analyzing self-service automation metrics, the dashboard helps businesses identify areas where further automation can be implemented, track the effectiveness of existing automation solutions, and ensure a seamless experience for both customers and agents.
      • CX Self-Service Opportunities KPI Card: provides an overview of performance for each opportunity, comparing month-to-date (MTD) figures against the previous month. It offers a quick, high-level view of key performance indicators for each opportunity, helping track changes over time.
        
      • CX Self-Service Rate by Question: displays the percentage of calls where self-service opportunities were identified and highlights the effectiveness of self-service identification across different opportunities.
        
      • CX Self-Service Hits by Date: visualizes historical trends and forecasts when specific opportunities are likely to occur in the future, based on past data and helps predict future call volumes for specific self-service opportunities.
        
      • CX Self-Service Hits by Site Name (with Drilldown for Agent Group & Agent): visualizes which sites, agent groups, and individual agents are most often transferring calls, allowing for prioritization of call-routing solutions. It helps identify where process improvements can be made, and which teams need more focus on self-service automation.
        
      • CX Self-Service Hits, Agent Sentiment and Caller Sentiment by Opportunity: visualizes the most frequently hit opportunities and identifies which ones have the worst sentiment for both agents and callers. It shows areas with high opportunities and areas where sentiment needs improvement for both agents and callers.
        The CX Self-Service Automation Identification Dashboard empowers analytics users to optimize self-service performance through a dynamic and data-driven approach. It delivers actionable insights by providing:
      • Key Performance Indicator (KPI) cards for quick assessments of performance across automation opportunities.
      • Interactive charts and graphs for detailed analysis, including trend lines with forecasting, to track performance and predict future outcomes.
      • Detailed breakdowns of performance by question, site, agent group, agent, and sentiment, enabling users to pinpoint impacted areas.
        Selecting an automation opportunity dynamically filters all visuals, allowing for focused analysis. This integrated functionality enables users to identify optimization opportunities, enhance customer experience, and drive efficiency.
   10. Phrase Hits Analysis Dashboard
       This dashboard is designed to empower analytics users to gain valuable insights from recorded conversations, focusing on the occurrence and context of specific phrases within those interactions. By leveraging the visualizations within this template, analytics users can efficiently analyze call data, identify key trends, and understand how language is used in relation to evaluation metrics.

       The primary objective of this dashboard is to enable users to effectively analyze the usage of specific phrases within recorded conversations. It aims to provide a clear and actionable understanding of:

       • Where and when specific phrases are being used.
       • How phrase usage relates to call evaluations and scoring.
       • The context in which these phrases are spoken within individual conversations.
       • Overall trends and patterns in phrase usage across multiple calls.

       Ultimately, this dashboard is intended to facilitate data-driven decision-making for improving agent performance, refining evaluation processes, and gaining deeper insights into customer interactions.

       • Call Listing Table: provides a granular view of all recorded calls within the specified date range/time period. It serves as the primary point of entry for in-depth analysis. The table displays key information about each call, including the Audio Duration, Agent who handled the call, AQA Score, percentage of Silence, percentage of Overtalk, and Agent- and Caller Sentiment. Analytics users are able to quickly scan and select specific calls for further investigation using other dashboard visuals.
         
       • Phrase Hits by Agent (with drilldown for Phrase): Displays the total number of tracked phrase hits attributed to each agent. It allows for a comparison of phrase usage across different agents and serves as a starting point for identifying top and bottom performers in terms of specific phrase occurrences. The visual displays each agent’s name along the vertical axis and the corresponding count of phrase hits on the horizontal axis. It includes a drilldown capability to view the specific phrases contributing to each agent’s total. Analytics users are able to identify agents with the highest and lowest frequency of tracked phrase usage. The drilldown feature allows for further investigation into the specific phrases used by each agent, which can inform coaching opportunities, highlight best practices, or reveal potential areas of concern regarding adherence to language guidelines.
         
       • Phrase Hits by Scorecard, Section, Question, and Phrase: provides a multi-dimensional view of phrase hits within a selected call, pinpointing where specific phrases were used and correlating phrase usage with the evaluation structure. The matrix displays phrase hits across different levels: Scorecard, Section, Question, and Phrases, allowing Analytic users to understand how and where phrases are used in the context of the evaluation, identifying trends and patterns in phrase usage.
         
       • Transcription: provides a detailed, textual representation of a selected call, and to visually highlight instances where tracked phrases were spoken. The textual transcript with highlighted phrases provides a complete record of the conversation, enabling Analytics users to understand the context in which phrases are used and to facilitate qualitative analysis.
         Phrase Hits by Section and Scorecard (with drilldown for Questions and Phrases): provides a summarized overview of phrase hits, organized by scorecard sections, and to enable drilldown to more granular data. The visual summarizes phrase hit data, shows which scorecard sections have the most hits, and allows Analytics users to drill down to identify areas where agents may need training or where they excel.
         The visuals on the Phrase Hits Analysis dashboard template are designed to work guiding users through a step-by-step process of looking at and understanding the call information. This connection means that when an Analytics user interacts with one visual, it can change what is seen in the others, helping to focus on the most important details.
         1. Start with the Call Listing Table: Analytics users typically begin their analysis by reviewing the Call Listing table. This provides an overview of all available calls, allowing them to filter and select specific calls of interest based on relevant criteria. Selecting a specific call allows for deeper analysis.
         2. Identify Overall Agent Performance Regarding Phrase Usage: The Phrase Hits by Agent visual provides an overview of how frequently each agent uses the tracked phrases across all their calls within the selected timeframe. This allows Analytics users to quickly compare agent performance in terms of adhering to or deviating from desired language. The ability to drill down and see the specific phrases used by each agent offers further insight into individual tendencies and potential areas for coaching or recognition.
         3. Examine Phrase Usage within the Evaluation Structure: The Phrase Hits by Scorecard, Section, Question, and Phrase matrix then displays where the tracked phrases occurred within the selected call, broken down by the different levels of the evaluation scorecard. This helps Analytics users understand the relationship between phrase usage and the evaluation framework.
         4. Understand the Context of Phrase Usage: To gain a deeper understanding of how the phrases were used, users can refer to the Transcription visual. This visual provides the full transcript of the selected call, with the identified phrases highlighted within the surrounding conversation. This allows for qualitative analysis and understanding of the context.
         5. Identify Broader Trends and Areas of Focus: The Phrase Hits by Section and Scorecard visual provides a summarized view of phrase hits across all (or a filtered set of) calls, organized by scorecard sections. This allows Analytics users to quickly identify which areas of the evaluation have the most or least phrase hits. The drilldown functionality enables further investigation into specific questions or even the individual phrases contributing to the counts within each section. This can highlight areas where agents may consistently use specific language or where certain evaluation sections are particularly relevant to phrase usage.

         By following this flow, Analytics users can move from a high-level overview of call data to a detailed understanding of specific phrase occurrences within individual conversations and broader trends across multiple interactions.

         Now that you know the purpose and features each of the predefined dashboard templates provide, it is appropriate to look at the second way an analytics user may create a custom dashboard.

         The second way in which an analytics user may create a dashboard is to click the Add Dashboard icon  in the My Configured Dashboards tab. Doing so will result in another view appearing. An example of this is illustrated in Figure – Creating a Dashboard.

The analytics users have access to various functions, including:

1. Adding or removing dashboard filters.
2. Modifying the dashboard name and description.
3. Adjusting the dashboard layout.

On the left of the view are a number of pre-created visuals (illustrated by 1 in Figure – Creating a Dashboard) that the analytics user may drag-and-drop to Add Visual on the dashboard, indicated by 2 in Figure – Creating a Dashboard. There are a number of predefined dashboard layouts an analytics user may choose from. These are selectable by clicking the desired layout icon illustrated by 3 in Figure – Creating a Dashboard. As the analytics user drags visuals from the ‘visual’ panel as illustrated by 4 in Figure – Creating a Dashboard, to the dashboard Add Visual section 2 in Figure – Creating a Dashboard they are creating, the current number of visuals permitted per dashboard as well as the current number of visuals applied to the dashboard is displayed, as illustrated by 5 in Figure – Creating a Dashboard. Currently, each dashboard may contain a maximum of six visuals. Once this number is reached, no further visuals may be added to the dashboard. An analytics user may however remove a visual and replace it with another. Setting a dashboard as the default means the dashboard will be the first to load when viewing the My Dashboards page.

Note: For each customer’s account the pre-created visuals, as illustrated by 1 and 4 in Figure – Creating a Dashboard, are published in this section. These visuals will be applicable to the customer’s business and may contain visuals such as Call Sentiment, Silence, Overtalk, Call Listing, Chat with Data, et cetera as determined appropriate by CallCabinet’s analytics team. CallCabinet’s analytics team ensures these visuals relate (or attach) to the customer’s data, providing instant visual metrics once the dashboard has been completed.

An analytics user may click on the Visual Types dropdown list, as illustrated by 6 in Figure – Creating a Dashboard and select the type of visual they desire. An example of this dropdown list is;

Once selected, all the available visuals relating to the type selected will appear in section 1 illustrated in Figure – Creating a Dashboard. The analytics user would then select the desired visual, as indicated by 4 in Figure – Creating a Dashboard and drag-and-drop it into the dashboard’s Add Visual section illustrated by 2 in Figure – Creating a Dashboard currently being created. Incidentally, the analytics user may also search for a visual, by typing the required visual’s name in the Search Visuals search field. For example, ‘chat’ would result in a Chat with Data visual being displayed in section 1 illustrated in Figure – Creating a Dashboard which the analytics user may then drag and drop onto the dashboard as described earlier. Likewise, entering ‘sentiment’ will render numerous visuals the analytics user may choose from.

The analytics user may set default filters that they may use to filter the visual data, in real time. This is achieved by dragging the desired filter from the Visual Types column to the Add Filter section indicated by 7 in Figure – Creating a Dashboard. What is important to understand is that only those visuals that are marked as a filter may be applied. For example, in the Visual Types dropdown list, as indicated by 6 in Figure – Creating a Dashboard, the user may select ‘Filter Date Range’, or ‘Filter Date Period’ and then drag the visual to Add Filter (illustrated by 7 in Figure – Creating a Dashboard).

To amplify this explanation a little further, the Figure – Drag Filter illustrates a dashboard that has a visual already added (as indicated by 1). To add a filter the user selects the filter and drags it to Add Filter as illustrated by 2 in Figure – Drag Filter. Once done, the filter is displayed. For example;

This filter will be available to the analytics user, when viewing the dashboard, to select the criteria they would like to apply for all the visuals rendered in the dashboard.

The purpose of each of the filters available are:

• Agent Dropdown: Using the dropdown, analytics users can select a specific Agent to view their interactions and update the dashboard metrics for that specific Agent. This is helpful for individual Agent performance analysis or identifying training needs.
• Agent Clarity Slider: This filter gives analytics users the ability to filter data based on the audio clarity scores to evaluate audio quality during calls.
• Agent Clarity Bin Dropdown: With this filter, analytics users are able to group calls into bins based on Agent Clarity ranges. The Agent Clarity Bins are split into intervals of ten (10) percent starting with the 0-10% range and going up to 90%+.
• Agent Group Dropdown: Filters data based on a specific Agent Group. This can be useful for comparing performance across different Agent Groups and identifying areas for improvement and training needs
• Agent Sentiment Slider: Filters data based on Agent Sentiment, and this can be used to identify calls where the Agent was stressed or unprofessional or where the Agent handled the call well.
• Agent Sentiment Group Dropdown: Allows analytics users to group calls by Agent Sentiment categories, either “Negative”, “Neutral”, or “Positive”.
• Audio Direction Dropdown: Filters data based on the direction of the audio (Inbound or Outbound). This can be useful for analyzing different types of interactions.
• Audio Duration Bin Dropdown: Groups calls by ranges of Audio Duration.
• Audio Duration (Mins) Slider: Filters data based on the call duration (in minutes) that the analytics user specifies using the slider. This can be used to identify long or short calls, which may indicate specific issues or opportunities.
• Call ID Filter Dropdown: The Call ID filter allows analytics users to search or filter data by a unique CallID. This provides the ability to access a specific call record.
• Call Options Dropdown: Filters data based on the type of call, which is categorized as follows:
  External Calls: Calls between an agent and an external phone number, i.e., the external number is a phone number.
  Internal Calls: Calls between two Agents, where the external number is an Agent ID.
  Meetings: Calls involving more than two participants or identified as Microsoft Teams meetings. This can be useful for analyzing different types of interactions.
• Caller Clarity Slider: The Caller Clarity filter gives analytics users the ability to narrow down calls by caller clarity score to assess audio problems on the customer’s side.
• Caller Clarity Bin Dropdown: Analytics users will use this filter to group calls into bins based on Caller Clarity ranges.
• Caller Sentiment Slider: By filtering data based on the Caller Sentiment, analytics users are able to identify calls where the Caller was frustrated or dissatisfied or happy.
• Caller Sentiment Group Dropdown: Allows analytics users to group calls by Caller Sentiment categories, either “Negative”, “Neutral”, or “Positive”.
• Date Slider: Allows analytics users to select a specific date range to filter the data. This allows data to be narrowed down to the events on a specific date.
• Day Dropdown: Analytics users will use this filter-to-filter data by day of the week, e.g., Monday, Tuesday.
• Hour of Day Dropdown: The Hour of Day filter allows analytics users to filter data by specific hours of the day to analyze time-based events.
• KPI Metric Selector Dropdown: When analytics users select a specific KPI Metric from the dropdown, the data will be dynamically adjusted and displayed on the dashboard. The KPI Metrics that are available for analytics users to choose from are:
  Agent Sentiment (%)
  AQA Score
  Avg Audio Duration (Mins)
  Caller Sentiment (%)
  Interactions
  Overtalk (%)
  Silence (%)
• Month Dropdown: analytics users can select a specific month to view data aggregated for that month.
• Overtalk Slider: Filters data based on the percentage of time where the Agent speaks over or is constantly interrupting the Caller. This can be used to identify potential communication breakdowns, or areas where Agents may need to improve their active listening skills, or areas where the Agent requires additional training.
• Overtalk Bin Dropdown: Allows analytics users to group calls into bins based on Overtalk ranges.
• Phone Number Dropdown: Analytics users will use this filter to analyze data for specific customers.
• QA Type Dropdown: The QA Type filter allows analytics users to filter calls based on their QA Type, which can be either Auto QA or Manual QA.
• QC Section Dropdown: Filters data by a specific scorecard section for focused analysis.
• Quarter Dropdown: Allows analytics users to choose a quarter, e.g., 1 or 2, to analyze data grouped into a three-month period.
• Question Dropdown: The Question dropdown allows analytics users to filter by specific AQA Questions that were logged during call evaluations.
• Scorecard Dropdown: Filters data by a specific AQA Scorecard. This allows analytics users to evaluate specific call outcomes.
• Silence Slider: Using the slider, analytics users can filter data based on the percentage of silence in the conversation. This can be used to identify areas where Agents may need to improve their speaking pace or engagement and highlight training needs.
• Silence Bin Dropdown: Allows analytics users to group calls based on Silence ranges.
• Site Dropdown: Filters data based on the site or location where the interaction occurred. This can be helpful for identifying regional trends or issues.
• Suppression Calls Dropdown: This filter gives analytics users the ability to filter based on calls that have been marked as suppressed in the frontend portal.
• Topic Dropdown: The Topic filter narrows data based on Topics or reasons for calls, for example Billing or Support.
• Words per Minute Slider: This filter allows analytics users to identify Agents who speak too quickly or too slowly. These metrics can then be used to identify areas where training is needed.
• Words per Minute Bin Dropdown: Allows analytics users to group calls into bins based on speaking rate (Words per Minute) ranges.

Once the analytics user has completed configuring their dashboard, they may decide whether this dashboard should be the default dashboard rendered when viewing their My Dashboards page. To do this, the analytics user would click the Set as Default Dashboard checkbox as indicated by 3 in Figure – Drag Filter.

The final action required by the analytics user when creating a dashboard is to give it a name, as illustrated by 4 in Figure – Drag Filter. The user may provide an explanation as to the purpose of this dashboard, by entering information in the description field as illustrated by 5 in Figure – Drag Filter. Should the analytics user want to add tags to this dashboard, they may do so by entering a name for the tag and then adding it by clicking the Add Tag button as illustrated by 6 and 7 respectively in Figure – Drag Filter. Adding a tag is useful for filtering the analytics user’s dashboards rendered on their My Configured Dashboards and Dashboard Templates tab views. When an analytics user selects the tag (or tags) in the tag listing, then only those dashboards that have those tags attached will be displayed. Doing this may help to minimize the ‘visual noise’ on the view allowing the analytics user to focus on particular dashboards. The user would then click the Save Dashboard button illustrated by 8 in Figure – Drag Filter.

Being able to create their own dashboards, with the views and metrics desired, provide an analytics user with powerful tools to gain important insight into their recorded calls.

Depending upon the visual the analytics user places on a dashboard, different behavior may occur. As an example, let us assume that the analytics user created a dashboard that focuses on interactions between customers and agents. An example of this type of dashboard is illustrated in Figure – Interaction Dashboard.

As can be seen there are six visuals on this dashboard. The analytics user is able to glean further information by hovering their cursor over the various visuals. Depending on the visual, there is different functionality. For example, if the analytics user hovers over one of the vertical bars in the bottom left visual, Interactions By Agent, a context menu appears, something like this;

Notice that the popup for this view renders the agent’s name and the number of interactions they have participated in. A button also appears, Drill down. Clicking this allows the analytics user to evaluate this agent’s interactions a little further. Notice how the dashboard changed in Figure – Agent Drill Down. The information rendered is applicable to the selected user

Once again, if the analytics user hovers their cursor over any of these visuals, more granular information is rendered.

Figure – Another Dashboard is a dashboard in which a date filter is being applied and which contains other visuals, inter alia AQA (Automated Quality Assurance) results, overtalk and silence.

As an analytics user, CallCabinet encourages you to experiment with the various visuals, dashboards and related functionality.

AI Agent in the Analytics Portal

The AI Agent will provide its findings, as illustrated in Figure – AI Agent Answer. You will soon discover that the information returned by the AI Agent is extremely comprehensive. The Analytics user will have the ability to engage in a continuous conversation where the model retains complete context, ensuring seamless reference to prior interactions.

As mentioned, any question may be asked. For example: “How do I create a scorecard”. The executive AI Agent will respond with a step-by-step process on how this is achieved. Another question may be “Did the agent introduce themselves?”. Essentially, any question concerning the CallCabinet application or any call may be asked. The agent is an executive agent that is capable of providing answers to anything CallCabinet related.

Once questions have been asked, a record of those questions is kept and displayed, as indicated by 4 in Figure – AI Agent GPT View Page. An Analytics user can access this full conversation history, allowing them to effortlessly pick up where previous discussions concluded. This is illustrated by Figure – Executive Agents.

It is highly recommended, by CallCabinet, that before an Analytics user starts asking the AI Agent questions, the Analytics user applies filtering against the calls. Doing so will greatly improve the results returned by the AI Agent. To apply filters, the Analytics user would click the Call Filters button, as indicated by 5 in Figure – AI Agent GPT View Page. When the Analytics user clicks this button, a dialog is rendered, as illustrated by Figure – Call Filters.

Currently, the filters that may be applied are;
Date Rage,
Agent Group,
Agent,
Call ID,
Direction,
Duration,
Extension,
Site ID,
Number.

Once the Analytics user has selected the filters and set the criteria they would like to use, they must click the Apply button. Once done, the Analytics user would then go and pose questions for the AI Agent to answer.

Please note that the user that is logged in and performing queries, the AI Agent will take the user’s role into account. As an example, a user may not ask questions about any calls they are not allowed to view or listen to.

Notifications allow a user to add alerts based on custom created rules. These notifications are triggered by the Quality Assessment (QA) evaluation process. This feature enables users who have the appropriate permission to track critical trends in their data and receive timely Notifications when significant changes occur. This assists a business in making appropriate decisions as a result of these real-time insights.

When an Analytics user clicks the Analytics tablature indicated by 1 in Figure – AI Agent GPT View Page, the general analytics view will be rendered. A menu is displayed in the left panel, and should the user click the Notifications icon, illustrated by 8 in Figure – AI Agent GPT View Page, the following Figure – Notifications Activity view is rendered.

This table provides a detailed overview of past notifications, enabling the Analytics user to effectively monitor and analyze Notification Events with precise information on when and why they were triggered. An example of this Activity log is illustrated in Figure – Notification Activity.

Each Notification Log includes the following key details:

• Time Stamp: The exact time when the Notification was triggered.
• Title: The name of the Notification for easy identification.
• Type & Level: The category and severity of the Notification.
• Description: A concise explanation of the event that triggered the Notification.
• Notification: Whether a Notification was sent.
• Triggered Calls: The number of calls that triggered the Notification.

By clicking on the caron (v) associated with any notification, an Analytics user may access additional in-depth information, including:

• Condition: The specific metric that was being monitored.
• Trigger: The rule or threshold that activated the notification.
• Call Link: A direct link to the recorded call for further review.

For example:

When the Management tablature, as illustrated by 1 in Figure – Notification Management is selected, all the notification configurations are displayed in a table.

The table consists of a number of columns. These are;

• Name: A meaningful name given to the notification.
• Created: The day and time the notification was created.
• Flow Type: This indicates whether it is the Standard trigger flow or triggering that occurs during the Analytics flow process.
• Last Trigger Date: This is the latest date and time this event triggered a notification.
• Type: This details the event that will trigger a notification. Examples of a type are, silence, keyword and AudioDuration.

The user may decide which columns they would like visible, or removed from the notification table by clicking the ‘Edit Columns’ button illustrated by 2. From the dialog that appears the user may make the changes they require. Once done the user must not forget to click the Save button to enforce their changes. Should the user click the Default button in the Edit Columns dialog, then all possible columns are displayed in a predetermined order in the Notification table.

It is possible for an admin user to edit any of the notifications rendered in the table by clicking the Edit icon associated with the notification configuration they would like to change. This is illustrated by 3. Likewise, a notification may be removed by clicking on the Trash icon, as illustrated by 4, that is associated with the notification the Analytics user wishes to delete. This page provides the Analytics user with an overview of all the Notification Event configurations that have been created.

If an Analytics user wishes to create a new Notification, there are two processes they may select from. One, use the wizard, or two, go straight to the Review page and enter all the required information there. To create a new notification using the wizard, the Analytics user must make sure that the checkbox ‘Skip Wizard’ is unchecked illustrated by 6 in Figure – Notification Management, then go ahead and click the New Notification button as illustrated by 5 in Figure – Notifications. This results in a ‘wizard’ being rendered, which guides the user through a step-by-step Notification creation process:

The Notification Window defines the call volume threshold required to trigger the notification. The user is first required to decide on the Window configuration type from the Type dropdown list. Currently there are two options, Interval and Interaction;

If the user selects Interval, they are then required to enter the timeframe in Hours in which calls should be grouped and then evaluated before triggering a Notification event. For example;

These Notification Types in the dropdown list are predefined by CallCabinet and are immutable. At the moment the Notification Type options are;

Once the user has entered the Name and selected the desired Type, they click the Next: Window button. The user is taken to the ‘Notification Window’ page, as illustrated by Figure – Notification Window.
NOTE: both the Name and Type fields are required fields, which means that they require values before the user is able to proceed to the next step in creating the Notification.

The Notification Window defines the call volume threshold required to trigger the notification. The user is first required to decide on the Window configuration type from the Type dropdown list. Currently there are two options, Interval and Interaction

If the user selects Interval, they are then required to enter the timeframe in Hours in which calls should be grouped and then evaluated before triggering a Notification event. For example;

Likewise, should the user select Interaction, they are then required to enter the Number of Calls to be evaluated before triggering a Notification event. For example;

Once done, the user clicks the Next: Triggers button. The user is taken to the Notification Triggers page, as illustrated by Figure – Notification Triggers.

NOTE: both fields are required fields, which means that they require values before the user is able to proceed to the next step in creating the Notification.

A trigger is used to validate and trigger a Notification when the condition is met. A user is able to set a maximum of three triggers per Notification. So, Notification Triggers define the specific thresholds used to evaluate aggregated call data and determine whether a Notification Event should be created.

The level of the notification may be: Info, Warning or Critical. This level is selected from the Level dropdown list. Once the user has selected the Level, they must select the Condition and associated value. NOTE: The options available in the Condition dropdown list is determined by the Notification Type selected earlier. For instance, if the user selected AudioDuration as the type, then the condition options are >= (greater-than or equal to) or <= (Less than or equal to). Likewise, if the user had selected a Notification Type of Phrases then the condition option is IN. Currently all possible options are

Examples of Trigger Conditions include:

• Less Than or Equal to ( <= )
• Greater Than or Equal to ( >= )
• IN (the value is within a specified list of values)

Once the user has selected the Condition, the value associated with that condition must be entered.

The user must also enter the Trigger Threshold (%). This value represents the percentage of interactions within the window that need to be considered for a trigger event to be fired. For example: If the user selects a Notification Window Configuration type of ‘Interval’ of 24 hours, and a trigger configuration of >= whose Trigger value (%) is 10% and the Trigger Threshold (%) is 50%, this means that a trigger will be fired if 50% of calls within the 24-hour period are above or equal to 10%.

Each Trigger has the option to enable Notify Trigger. When selected, the trigger will send a push notification through notification channels such as email or webhook. The configuration of these notification methods will be done later in the process. If the user does not check this checkbox, then the trigger will not be sent but will still be inserted into the activity log.

If the user would like to add another trigger Condition, they would click the +Add Trigger button that appears across the notification Trigger screen as illustrated in Figure – Notification Triggers.

The admin user proceeds to the next page once all the required fields have been populated with information, by clicking the Next: Cooldown button. This results in the Cooldown page being rendered, as illustrated in Figure – Notification Cooldown.

A Notification Cooldown period configures the amount of time that must pass after a notification is sent before another notification may be issued. This helps prevent users from receiving excessive notifications in short time frames. The time interval is set in Minutes, where the minimum allowed interval is 30 minutes. Once the Cooldown period has been set, the user moves onto the next page, Notification Actions by clicking the Next: Actions button.

Push notifications inform users about a new Notification Event. Please ensure that the Notify Trigger option is enabled when configuring Notification Triggers to activate notifications. Webhook is a POST URL where notifications will be sent. When the user checks this checkbox, the Webhook’s URL must be entered into the field that appears. Email is the email address where the notification will be sent when this checkbox is checked. When this is checked an email field appears in which the user may enter a list of comma-separated email addresses of the emails to which the Notification event is to be sent.

Should the Admin user want a Tag to be attached to the call that resulted in a Notification Event to occur, then they would check this box, and from the dropdown list which contains all configured Tags, select the Tag they would like to be attached to the call. This is very useful, as a user is then able to filter all calls in the Call Listing page that have the Tag attached.

An example of a Notification that may be sent is:

Once the Admin user has completed entering the required Notification Actions, they would click the Next: Filters button which results in the Navigation Filters page being rendered, as illustrated in Figure – Notification Filters. Notification Filters allows for greater control by allowing an admin user to specify which interactions should be considered when evaluating Notification Triggers. For instance, the admin user can limit a Notification to specific Agents or Groups of Agents as well as Sites, by clicking on the Filters Type dropdown list. The current filter options are;

The final step in creating a Notification is clicking the Review button. A page rendering the complete configuration parameters set for the Notification. An example of this is illustrated in Figure – Notification Review. The Admin user may edit any of the fields, if necessary. Once the Admin user is satisfied with the Notification’s configuration, they must click the Save button to save the newly created Notification. Should any of the Notification’s conditions be met, a Notification Event is generated and at a minimum, logged.

If an Admin user wishes to create a new Notification, without making use of the wizard, as described above then they would check (enable) the checkbox ‘Skip Wizard’ illustrated by 8 in Figure – Notifications, then click the New Notification button as illustrated by 4 in Figure – Notifications. This will result in the user being taken directly to the Review page in which they may enter all the Notification configuration details in one convenient view. Once they have entered all the pertinent information they would click Save to save the Notification’s configuration. An example of the ‘blank’ review page is illustrated in Figure – Notification Blank Review.

Referring back to Figure – Notifications, there are two tablatures rendered; the Management tablature illustrated by 1 and the Activity Log tablature, illustrated by 2. We have discussed the Management tablature.

Logout

Pressing on this menu item will result in the logged in user being logged out of the CallCabinet application and being presented with CallCabinet’s login screen, as illustrated below.

Support

Should you, the user of CallCabinet, have any questions or require any form of CallCabinet support, either

1. Email us at support@callcabinet.com or
2. Visit our help desk by clicking here to go to https://support.callcabinet.com/hc/en-us. When a user visits this web page, they will be presented with a screen similar to that illustrated in Figure – Support Portal (Website). There are a number of links the user may click on to try and find an answer to their problem. A user may also click on the Submit a Request button, indicated by number 1 in Figure – Support Portal (Website) to submit a request for help. Clicking on this button will direct the user to the page illustrated in Figure – Submit a Request for Support. Here a user may enter a description of the problem they are facing, once done, they may submit this request for help. It is imperative that the user, submitting a request for assistance, provides an accurate and detailed description of their issue in order

for CallCabinet to resolve their problem with minimal delay.

Predefined Roles and Associated Permissions

The predefined roles available in CallCabinet are:

• Restricted User
• SupportUser
• Restricted Admin
• Standard User
• Admin
• Super Admin

Any of these roles may be used as the ‘root role’ when a user, with the requisite permissions, creates a custom role.

NOTE:  In order to have access to certain sections, the user must also have a corresponding license. A quality assurance license grants access to the quality assurance features in CallCabinet including performing QA evaluations, running QA related reports and creating QA scorecards. This license includes three associated roles, which are preceded by QA:

1. QA Supervisor
2. QA Analyst
3. QA Admin
4. Advanced User – a value-add feature license that grants any user role access to the advanced call details page and reporting features in CallCabinet.

NOTE:  A permission may depend on other permissions. In such cases, when the dependent permission is enabled, so are all its dependent permissions.

Restricted User

Support User

Restricted Admin

Standard User

Grants users’ access to the Call Listing page for call playback and filtering.

Admin

Grants users’ access to the Call Listing page and some system settings including user- and agent management. This role is typically assigned to a manager, supervisor or IT professional who is responsible for maintaining some overall system settings in CallCabinet.