Patch corrections

Patch is a correction package that fixes business-critical issues.

We list here the issues fixed from RTC (release to customer) onwards.

To see which version your tenant has, open Communication Panel and go to User Menu > Settings > About. The patch number is the last digit in the Version field.

The latest patch includes fixes from all previous patches of the release. For example, corrections made in the first patch release are also in the second one, and so on.

26Q1.2 (build number 10.0.2602.2) — added January 27 2026

  • Searching the directory was slow if there were many directory groups in the system. This has been fixed by improving RESTful Interface's database caching. ID: SCC-19017

  • Occasionally, Visitor Chat didn't show the welcome prompt or incorrectly showed connectivity errors. This happened due to a timing problem. The issues have been fixed, which also improves the startup time, responsiveness, and scaling of the Visitor Chat UI.

  • When using embedded Communication Panel with SSO, users couldn't log into the Salesforce integration or use the responsive My Conversations view with a popped out Communication Panel in any CRM integration. To avoid issues with SSO login, we recommend updating to the latest Salesforce integration package from Contact Pro.

  • Contact Pro uses a certificate to encrypt secrets in the database. If a secret was added through the RESTful Interfaces, it was encrypted with an incorrect certificate. This caused authentication failures with integrations, such as Conversation API, after certificate renewal. ID: SCC-18378

26Q1.3 (build number 10.0.2602.3) — added February 5 2026

  • If conversation attached data (CAD) was added by an event-driven integration (EDI) to an unallocated chat and the chat was recovered after a backend module restart, the CAD was lost due to the Received event not triggering the EDI configuration. ID: SCC-19222

  • In a predictive campaign, CMI contact search was slow for active calls (In process, In queue, Pending, Wrap-up). This caused slowness and failing searches in Dashboard and Communication Panel. ID: SCC-19228

  • In request GET /RI/rmi/contacts, some query parameters didn't work with the limit query parameter. ID: SCC-19185

  • After the SQL Server reset, chats may occasionally fail, or attached data may be missing.

  • The following CP issues have been fixed:

    • For predictive campaign calls, CP used the incorrect number when doing a customer history search.

    • CP sent unnecessarily AI Analysis data requests for active conversations.

    • CP failed to prevent duplicate search filter items in customer history search.

    IDs: SCC-19090, SCC-19228

26Q1.4 (build number 10.0.2602.4) — added February 12 2026

In some rare cases, if one participant left a conference, this could result in the call continuing with no audio. ID: SCC-19309