...
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 in Q1 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 feature enhancements:
...
- 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:
...