14 posts tagged with "Chat & messaging"

This release contains further reliability improvements to additional services.

Change log​

Improvements and adjustments​

1. Improved speed and reliability of call recordings.
2. Further resilience improvements for chat.
3. Added an endpoint to be able to download agent-side transcripts.

This release brings further improvements to resilience and new supervisor tools.

Change log​

New functionality​

1. Added support for WebRTC and external agent extensions, enabling agents to use a valid configuration for both desktop and mobile agent applications without supervisor intervention. This is now displayed in the administration portal under an agent profile’s user details. You can now specify a phone number, and the WebRTC extension will be displayed alongside it.

2. The chatbot integration API now provides message status notifications. Read more in our developer documentation.
3. Added the option to hide a campaign’s additional CSV fields from agents, allowing campaign administrators to retain valuable data without exposing it to agents.

4. We’ve added the option for supervisors to log out an agent even when the agent is busy with a task. This can be useful when the agent forgets to close a task and leaves, when a task becomes unresponsive due to a system error, or when an agent stays in a lookup task too long. In the administration portal, go to Realtime reports > Teams Reports > Agents, find the agent, click Change state, and select Logout. Once confirmed, the agent will be logged out immediately.

Improvements and adjustments​

1. Fixed an issue where empty completion codes could be set at the channel level.
2. Fixed an issue where a TTS message failed to play when the TTS text was replaced with a much longer version.
3. Fixed an issue where Microsoft Teams users would experience duplicate Teams pop-ups when initiating a call from our CRM widget.
4. Fixed an issue where postponed records in a predictive campaign retained the predictive execution mode instead of falling back to preview.

This release lets campaign administrators cancel records after a nuisance call on predictive campaigns and adds an API for managing do-not-call lists.

Change log​

New functionality​

1. We've added a new public API endpoint to programmatically manage the Do Not Call lists. This allows integrators to synchronize their Graia CCaaS list with external systems they have, or with government lists.
2. Nuisance call treatment for predictive campaigns. Previously, nuisance calls were automatically postponed and had their dialing mode switched to preview. With this new configuration, campaign administrators can change the default behavior to cancel the record instead.

Improvements and adjustments​

1. Performance improvements for chat workflows.
2. Fixed an issue where removing an attachment from an email being forwarded also made it unavailable in the conversation history viewer.
3. Fixed a display issue on the administration portal where customer import jobs showed an unknown state.
4. Fixed a display issue where Task History filters for supervisors were displayed incorrectly on some screen sizes.

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 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.