End-of-life Luware on-premise solutions

Updating to LUCS 3.7 LTS

We recommend you update to Luware LUCS 3.7 LTS as this is our long-term support release.
LUCS 3.4 and 3.5 will be supported until July 31, 2022.
LUCS 3.6 and 3.7 LTS will be supported until January 9, 2024.
Extended support until October 14, 2025, can be requested for LUCS 3.7 LTS.

Request quote for update

LUCS 3.6 release notes are accessible on the Knowledge Base.

LUCS 3.7 LTS is planned for July 31, 2022, with the following features.
Important note: This is a preliminary feature list which is subject to change.

• Managing standby duty in the inbuilt calendar: Currently, an Exchange/Outlook calendar is necessary to manage standby duty. LUCS already has an inbuilt calendar to manage opening hours. The 3.7 LTS release will allow you to also manage their standby duty in the inbuilt calendar.
• Replacement of the log framework: Currently, the log framework requires a skilled software developer to retrieve and analyze log entries from LUCS. The 3.7 LTS release will come with a new log framework which is more user-friendly and empowers system administrators to analyze the logs themselves.
• LUCS APIs to access configuration raw data: LUCS calculates the internal distribution of interactions based on the defined distribution rules (such as skills and responsibility), for example: who gets which call, when, through which service. Any change of the distribution rule had to be done with due consideration as there was no validation or visualization of the configuration. To enable you to visualize and validate their configuration, we are exposing the LUCS APIs that makes the raw data accessible.
• Improved scheduling and assignment logic: The Callback Task Configuration has been updated to give Administrators and Supervisors more control and Agents are now kept “available” in between retries and not blocked from receiving further tasks.

Migration to Teams and Luware Nimbus

Luware Nimbus currently offers basic contact center features such as skill-based routing, after call work and dashboards. Our current Contact Center module is a solid base, and we are continuously developing features to fully cater to the needs of complex contact centers and to turn Nimbus into a powerful contact center tool equivalent to LUCS.

We recommend you evaluate and plan your transition from LUCS to Teams and Luware Nimbus Contact Center in the second half-year of 2022 and then tackle your migration in 2023. This allows you to holistically plan your communication and customer service strategy and ensure a smooth transition.

Updating to TeamManager 3.7 LTS

We recommend you update to TeamManager 3.7 LTS as this is our long-term support release.
TeamManager 3.4 and 3.5 will be supported until July 31, 2022.
TeamManager 3.6 and 3.7 will be supported until January 9, 2024.
Extended support until October 14, 2025, can be requested for TeamManager 3.7 LTS.

Request quote for update

TeamManager 3.6 release notes are accessible on the Knowlege Base.

TeamManager 3.7 LTS is planned for July 31, 2022, with the following features.
Important note: This is a preliminary feature list which is subject to change.

• Managing standby duty in the inbuilt calendar: Currently, an Exchange/Outlook calendar is necessary to manage standby duty. TeamManager already has an inbuilt calendar to manage opening hours. The 3.7 LTS release will allow you to also manage their standby duty in the inbuilt calendar.
• Replacement of the log framework: Currently, the log framework requires a skilled software developer to retrieve and analyze log entries from TeamManager . The 3.7 LTS release will come with a new log framework which is more user-friendly and empowers system administrators to analyze the logs themselves.

Migration to Teams and Luware Nimbus

The Luware Nimbus modules for Advanced Routing and Enterprise Routing are our call queueing solutions for Teams. If you are only using TeamManager in your organization and are transitioning to Teams, you can migrate to Luware Nimbus. If you also have LUCS in place in your environment, we recommend you plan your transition to Teams and Nimbus in the second half-year of 2022 and then tackle your migration in 2023 (see LUCS).

Request quote for Nimbus

Updating to Switchboard 4 LTS

We recommend you update to Switchboard 4 LTS as this is our long-term support release which will be supported until January 9, 2024.
Releases 2.0 and 3.0 will be supported until July 31, 2022.
Request quote for update

Migration to Teams and Luware Nimbus

If you are already using or want to transition to Teams, and want to migrate your Switchboard, you can use the Luware Nimbus Attendant Console. The Nimbus add-on Attendant Console empowers your front desk, reception, attendants, and frequent callers to easily transfer calls. The Luware Nimbus Attendant Console comes as an add-on to either of the Nimbus modules Advanced Routing or Enterprise Routing.

Request quote for Nimbus

Updating to RTC Launcher 2.6 LTS

We recommend you update to RTC Launcher 2.6 LTS as this is our long-term support release which will be supported until January 9, 2024.
RTC Launcher 2.5 and below will be supported until July 31, 2022 (see latest updates on the Knowledge Base).
Request quote for update

Migration to Teams and Luware Nimbus

If you are already using or want to transition to Teams, and want to migrate your RTC Launcher, you can replace it with Luware Nimbus Interact. The Interact module allows your customers to start voice and video chats directly from your website – for remote advisors, field support or tele sales. Your employees take the calls directly in their Teams client. Once the conversation was started, chat and screenshare can be added.

Request quote for Nimbus

Updating to PresenceAssistant 3.1 LTS

We recommend you update to PresenceAssistant 3.1 LTS as this is our long-term support release which will be supported until January 9, 2024.
PresenceAssistant 3.0 and below will be supported until July 31, 2022.
Request quote for update

Migration to Teams

Currently, Luware Nimbus does not offer any replacement for the Presence Assistant as it is not technically possible for us with the APIs that Microsoft offers. We will continuously evaluate our possibilities to develop a solution for Teams.