New Features

Support for multiple clients logged in on the same user

Clients with v2.0.7 and higher will now support running multiple instances of the client that are logged into the same user. This will enhance the user-experience when a user is operating multiple PC's at the same time, or often switching between PC's.

Automatically change status on lock/unlock

Clients with v2.0.7 and higher where User Status is enabled now have extra options in the settings menu that allows the configuration of an automatic status change when locking / unlocking your device. Any status can be configured by the user.

Control which client responds to certain features

With multiple clients now supported you can control which device needs to respond / execute certain features. This can be managed from the settings menu.

Callto:// & tel:// support on MacOS

Both protocols are now also supported on the MacOS build of the client.

Fixes

• Client Fixed an issue where the pop-up sizing was not being set correctly.

New Features

Launching a workflow as a user-action from the pop-up

Previously a user action from a pop-up record could only open URL's. Now it can also be configured to launch workflows. This opens up the possibilities of actions to perform when clicking on a pop-up record. The client now supports this feature with a new icon.

The launchURL action can still be used side-by-side.

Fix for users getting stuck in client setup

When inserting an internal number in the VoIPcube client you can now navigate backwards to the license key entry screen.

Users can now manage the values of the user scoped parameters that are available from the integrations. When hovering over the assigned integrations the users can now click through to the integration settings.

A new page will display the user specific parameters that the user can change.

When using the custom status feature in combination with 3CX the custom status in VoIPcube will now be reflected as the status in the 3CX clients as well. The custom custom status message field is used for this functionality

The client now has a new user setting that remembers the size of the pop-up window when resizing. Future pop-ups will open with this size.

The client now supports the voipcube:// protocol to automate starts of the VoIPcube client. A CallId parameter is available to automatically open the call history window on the specified call to easily find call info and recordings.

• Fixed a client issue where the pop-up can appear outside of the screen in dual monitor setup.

This release brings Playbook Versioning and Call Tagging, along with some fixes.

New Features

Call Tagging

Use Call Tagging to assign tags to inbound / outbound calls. The tag assignments can be used to gather insights about the call behaviour, trends and reasons for inbound / outbound calls.

Customer Service API

A new customer facing API is launched customer.voipcube.nl where customers can directly access their VoIPcube data. The first endpoint in the API is /stats/call-tag endpoint that provides a summarized call-tag count per period.

Fixes

• Client .MSI installer is now correctly signed with a valid certificate.

• Fixed an issue where the caller id was undefined on outbound call popups.

• Fixed an issue where custom trigger workflows did not send their result state back to the client on some errors.

• Fixed an issue where client license keys are not updated to the correct format.

The Call Popup is now separated from the main client. Each popup will launch in a separate window and can be launched as ‘Always On Top’ depending on user preference. The Popups are context aware and will double in size when a custom trigger is used.

For 3CX only it is now possible to configure Caller ID / DIDs on a customer level and assign these to users. When assigned the clients will show a new tab and allow the users to select / change his current outbound caller ID with a single click.

This number will then be set in the 3CX outbound Caller ID field by VoIPcube on the user level so the next outbound call will be performed with this Caller ID. (If trunk settings allow for it.)

VoIPcube Client

• Client can no longer be run more than once.

• Autoupdater logic changed. Updating now requires manual initiation before download. User will be notified.

• Check Update interval increased to 60 minutes.

• Improved websocket stability for intermittent internet connections.

• Removed the 'Synchronize calls from PBX' toggle and disabled client side call monitoring. This feature is deprecated. (F12 to unhide)

• Improved 'Reset License Key' flow so it automatically asks for the internal number.

• Window name is now set to 'VoIPcube' instead of Vue App.

This release brings some large new features to the VoIPcube platform and some welcome improvements to Call Tagging. Some general improvements and fixes are also put in place.

New Features

Call Recording (3CX and Swyx only!) Client >= 1.2.0 required

VoIPcube can now monitor the recording files of the PBX. When enabled the recordings are automatically uploaded to the VoIPcube platform and can be downloaded or listened to by the user directly from the client.

Call Journey Client >= 1.2.0 required

It’s now possible to see a visualized representation of the caller’s journey throughout the PBX and transfers between users.

This view is combined into the existing call popups when enabled.

Call History Client >= 1.2.0 required

If enabled for a user the client now allows the user to browser historic calls and view details of a specific call. This call history window is a starting point of a centralized location to all the data VoIPcube collects around calls. Currently the call info, assigned tags, call journey, and available recordings are shown.

• UI improvement for larger quantity of tags Client >= 1.2.0 required If more than 5 tags are assigned to a user the UI changes into a dropdown selector. This select field supports keyword entry to quickly find tags.

• Fixed an issue in the client where the old Telepo logo is shown.

New Features

User Status Tracking 3CX ONLY!

For 3CX customers you can now enable User Status tracking. This will automatically keep track of user status changes which can be used in integrations. It also allows you to create and map custom statuses to expand the options for the end-user. Each custom status needs to be mapped to a native 3CX status. The synchronization is 2-way.

LAR can consider user status 3CX ONLY

Last Agent Routing can now consider the user state before routing to a user. This can minimize the number of failed routing attempts.

Looks good right? This release marks the starting point of our new documentation platform. This is the place to read all about release notes, user manuals, and more.

This release marks the launch of a completely new VoIPcube Client. All aspects of the client regarding UI and architecture have been redesigned and improved. The client now sports a modern look and feel and is built on top of the VoIPcube Client SDK for a more robust technical implementation.

The new client now supports multiple languages. This is a per-machine preference. languages supported from this release are: