We are excited to announce the Evolve Contact Suite (ECS) v5.3.2 release that includes new capabilities for our customers that will be available on February 28, 2021.
What do you need to know?
- Any changes made to your environment must be fully deployed via Setup before the upgrade and previously deployed versions will no longer be available after the upgrade.
- If your organization is staffed during the maintenance, they will experience a short period of downtime (less than 10 minutes).
- Users will get a notification on their first login after the upgrade to accept and download the newest update. Please instruct your users to accept the application update.
- For more details about the steps each customer can take after the release, see the Post Release Testing article.
This release contains the following known limitations:
In some situations, a Callback will remain in Pending status instead of being offered to an Agent in the Ready state. The Callbacks will appear in the "Callbacks to be processed" metric inside Supervisor and will need to be activated using the "Send to Queue" command.
This release contains the following feature enhancements:
- The Auto Answer Interaction capability can be activated separately by media type. For phone calls, a configurable delay can be added to allow time for the Agent’s workstation to launch the business application “screen pop” to ensure synchronized delivery to the Agent.
- For outbound emails, a new ECS SMTP Relay capability enables organizations the flexibility of sending emails from any address configured inside Setup. By enabling ECS as an authorized sender of the client’s email domains, the contact center gains the ability to easily send from any email account or address without the need for individual account authentication or concerns about the recipient’s email solution displaying phishing or spam warnings.
- Improved error handling when an Application Server is removed from service.
- For Overlay call recording, the destination for the files is now configurable per organization.
- An active call is no longer terminated when the Agent application loses its connection.
This release contains the following reporting enhancements:
- The 4.13 report now includes the following fields: Inbound Handled in BP/Channel, Non-Campaign Handled by Agent, and Campaign Handled.
- The 3.05 report now includes the Business Process Name field and denotes when a Chat session is closed.
- The 7.04 report now display the values of the Abandon Thresholds in the column headers.
- When selecting a folder, the report pane will display the reports contained inside that folder.
- The Subscriptions tab now includes the following fields: Report Name and the subscription’s Schedule.
- The word Report has been removed from the report names on the Report Output: 1.01, 1.04, 1.06, 2.01, 2.03, 3.01, 3.03, 4.01-05, 4.07-11, 4.14, 5.05, 6.01, 6.03, 6.04, and 7.01-05,
This release contains the following bug fixes:
- In Setup, the Agent Import/Export spreadsheet including a leading space on the Chat Private Greeting field label.
- Agent displayed visual inconsistencies when email attachments were added and removed to an email reply.
- Supervisor displayed an incorrect Abandon Rates for custom Interaction Types.
- On a consulted transfer, if the second Agent answers simultaneously on the handset and the Agent application, the transferring Agent would lose all call handling commands.
- The queue messaging didn’t play if the caller pressed a DTMF digit while the call was being offered to an Agent in a Unified deployment.
- The BP Dashboard inside Supervisor displayed the incorrect number of Agents in each ACD State during a Light Deploy.
- The ASA and Service Level on the Contact Center Dashboard displayed incorrect values that made the results look worse than actual.
- Consulted transfers via the web Agent fail to complete.
- When the agent's HPBX endpoint returns a SIP 480 error, the Supervisor application continues to increment the Waiting Time for that interaction.
- When the agent's HPBX endpoint returns repeated SIP errors, the agent was not placed automatically into the No Answer state.
- A Callback interaction is misidentified in the queue and cannot be answered by an agent.
- An organization's service package failed to start after a Full Deploy.
- Outbound Campaign calls were placed outside of the specified Customer Calling Hours.
- The Agent application experienced significantly degraded performance.
- Ready agents were not offered a queued interaction.
- A Full Deploy that included the renaming of hundreds of agents failed to complete.
- An interaction that was active during a Light Deploy didn't display on reports.
- The position in queue spoken to a caller was incorrect.
This release contains the following reporting fixes:
- The 7.x reports will no longer include Callbacks in the Calls Queued calculation.
- The 2.01 report displayed no results when an interaction Direction was selected.
- The 3.04 report incorrectly included Pre Queue Duration in the Abandon time field.
- In certain scenarios a Callback requested in the queue was considered Abandoned if the caller disconnected before the system confirmed their callback request.