24 posts tagged with "Administrator"

This release brings business-unit-level Do Not Call lists and stability improvements.

Change log​

New functionality​

1. Business-unit-level Do Not Call list: The Do Not Call list helps comply with regulations and customer preferences not to be contacted. Previously this list was tenant-level and affected all business units. We now allow business-unit-level lists to add extensions to the tenant-level list. The business-unit-level list extends the tenant-level list rather than replacing it.

Improvements and adjustments​

1. Added queue details for agent-to-agent transfers. Previously the target agent saw the queue name as "Unknown queue" when the call came from another agent rather than from a queue.
2. Improved recording handling when either the customer or the agent is placed on hold, preventing unexpected behavior in certain scenarios.

This release introduces new agent management tools and stability improvements.

Change log​

New functionality​

1. Disable outbound capabilities per agent: You can now disable the ad hoc outbound capabilities for a specific agent. This means the agent will no longer have the lookup option, cannot re-open email threads from their Task History, and the Website visitors tab is hidden, blocking outbound chats. Typical outbound calls via campaign tasks are not affected by this feature.

Improvements and adjustments​

1. Additional redundancy for voice services.
2. Further resilience improvements for reporting.

This release brings new campaign management tools, additional KPI for realtime reports and voice related stability improvements.

Change log​

New functionality​

1. Voicemails are now displayed in the administration portal. Voicemails left by customers through the Voicemail node are now displayed in the administration portal. Supervisors or team leads can now see their details, playback voicemails and download them via the dedicated menu item. Each voicemail is displayed as a separate row in the list, even if there are multiple voicemails for the same conversation. Users may search for voicemails by conversation ID or customer phone number.

2. We added a new KPI for email-heavy businesses. You can now view, in the team reports, the total emails sent by your team as well as per agent in the agent view. This KPI is displayed at a glance, even if the agent card is expanded.
3. Automatically move agent to a selected break when entering lookup task mode. As a supervisor or team lead, you can now configure an option to automatically move agents to a break code you choose when they open their lookup task. This break code is not visible in the agent application as a selectable option and is automatically cancelled when the lookup task ends, without moving the agent to break. This is particularly useful if your agents perform back-office tasks and they should not be disturbed with an inbound task while they are in a lookup task.

4. Change predictive campaign dialing mode to preview. While operating a predictive campaign, you may decide that the campaign is not very efficient due to low agent count, or it already achieved its purpose, in which case, from the predictive settings, you may switch the campaign back to preview, without having to create another campaign. You can switch back to predictive at any time, but records already in progress are not affected by the change.
5. In some cases, the default music for customers waiting in the queue to be connected to an agent when using predictive dialing mode is not the best approach. For this, we introduced the option to disable it completely via the predictive settings, in which case, the customer will not hear anything until connected to an agent.

6. We introduced the option to enable queue timeout for predictive campaigns. When enabled, the timeout can be set from 0 seconds (a single attempt is made to connect the customer with an agent before abandoning the call) to 60 minutes. Customer calls terminated by a queue timeout will be considered a nuisance, the record state will become postponed and their dialing mode will be switched to preview.

Improvements and adjustments​

1. Fixed an issue where a predictive campaign record was being set to Rescheduled instead of Postponed when the call was flagged as a nuisance call.
2. Fixed an issue where the Language profile creation modal was not scrollable on small screens.
3. Fixed an issue where the CSV export for historical conversation reports was missing some fields.
4. Fixed an issue where announcements could not be stopped if there was a transfer happening while the announcement was playing.
5. Fixed a rare issue where an agent could receive two calls at once.
6. Further resilience improvements for outbound calls.

This release brings message status indicators for webchat, new campaign functionalities and additional agent management tools.

Change log​

New functionality​

1. We introduced the Read receipts functionality for webchat conversations. This allows the agent and the customer engaged in a conversation to see if their message has been sent, delivered, and read by the other party. Please note that this functionality is not available for other digital channels, such as Instagram, WhatsApp, or Facebook Messenger.

2. We introduced the option to Pause new campaign record processing to campaigns. This allows campaign administrators to ensure rescheduled records are processed and agents can meet their commitments to customers. When this feature is enabled, newly added or postponed records are not processed; only rescheduled records are handled.

3. A second campaign management tool we introduced in this release is the option to Suspend campaign records. Suspending a campaign record prevents it from being processed until unsuspended, allowing team leads to temporarily restrict records from being handled. This operation is available per record through campaign actions as well as in bulk through the selection mode.

4. The option to suspend campaign records is also available through the public API: you can suspend and unsuspend campaign records by their IDs, up to 100 per request.

5. BI developers need to track consultative call attempts accurately. We've simplified this by introducing a relationship ID in the OData calls table, allowing them to link consultative call attempts to their originating calls.
6. Agents may sometimes inadvertently cause issues with customer records. We introduced two controls for administrators to restrict access to certain functionalities. Administrators can now prevent agents from creating or editing customer records, helping keep customer data accurate. This is fully optional and configured per tenant.

Improvements and adjustments​

1. We've improved how campaign filters work. Previously, users could select only one campaign record state as a filter, but with the introduction of campaign record suspension and its associated filter, this became unnecessarily complicated. We've enhanced the user experience by transforming the status filter into a multi-select dropdown grouped by active and completed states. You can now apply multiple status filters combined with other filters, making it easier to find the records you need.
2. Emails received by the system are now marked as read. Previously, if the administrator checked the mailbox configured as an inbound email channel, emails processed by the system were not marked as read. Administrators had to check each email individually to verify processing. Emails processed by the system are now automatically marked as read in the mailbox.
3. We modified workflow-controlled campaigns to prevent system spam from very short calls. The maximum parallel call count is now guaranteed for calls longer than 30 seconds. For shorter calls, the system will not initiate new calls until the 30-second mark is reached.
4. Additional redundancy for voice services, rolled out gradually.
5. Fixed an issue where replying to a transferred email kept the original channel email address as the sender.
6. Fixed an issue where email conversations could be stuck without history updates or failed routing in situations involving faulty conversational bot configuration and handling.
7. Fixed an issue where a tenant having multiple Entra IDs configured could not create new channels under specific circumstances.
8. Fixed an issue where cloning a workflow did not clone its containers as well.
9. Fixed an issue where logout durations happening over the weekend were not tracked correctly.
10. Fixed an issue where unquoted display names resulted in the email address not being parsed correctly when pasting them into the email to field.
11. Fixed an issue where the agent workspace ID was missing from the OData feed for calls initiated through the public API.
12. Fixed an issue where a call freshly associated with a new contact record was not shown in the activity history.
13. Fixed an issue where the recording was not available for calls initiated through the public API.

This release brings stability improvements, performance improvements, new node options and more!

Change log​

New functionality​

1. Improved the stability of campaign processing under high load.
2. Further resilience improvements for voice services, reducing the chance of stuck calls.
3. Added the option to mark a custom question node as sensitive data. Sensitive data is never stored and, by default, is not made available to other nodes or integrations. You may add a variable resulting from a custom question node as an exception to the voice's custom integration node or the JavaScript node.

4. Added a new voicemail node. This node allows administrators to configure paths where the customer can leave a voicemail, for example, after a CSAT node where the customer left a poor rating. Voicemail playback via the portal will be added in a future release.

5. Added the option to cancel all filtered campaign records, making it easier for campaign administrators to cancel an entire list of records at once. Simply apply your record filters, then click the Cancel all filtered records button.

Improvements and adjustments​

1. Fixed an issue where the outbound dial duration limit was applied per trunk, causing multiple call attempts in some specific scenarios.
2. Fixed an issue that could prevent stuck calls from being cleared.
3. Based on your feedback, we removed the announcement button when no agent announcements are configured.
4. Fixed an issue where greetings and agent announcements would not stream properly if the call was transcribed.
5. Fixed an issue regarding attachment handling for the agent in chat where in some rare cases, the attachment uploading did not work properly.
6. We've made several performance improvements to customer management targeted at users having more than 1000 customer records in a single business unit. Based on our testing, search results should now appear at least 2 times faster. We will continue to monitor the situation.