Wildix Integrations Changelog

[WMS-23854] - wms: fixed an issue in which Voice bot call could be interrupted in some cases due to triggering silence timeout when processing third-party function request 

[WMS-24880] - wim: added the possibility to create a Lead and Contact entity in Salesforce Lightning during or after a call

Documentation: Salesforce Lightning Integration - User Guide - English, Salesforce Classic Integration - User Guide - English

[WMS-24327] - ai: added possibility to select the preferred Model (e.g. GPT-4.1, GPT-5, etc.) in Advanced configurations of a Chat Bot

How-to:

1. Go to WMS -> PBX -> Integrations -> Cloud integration -> Chat Bots

2. Select the Chat bot or create a new one

3. Navigate to Advanced configuration -> Model

4. Select the preferred model 

Documentation: How to configure Voice Agents

[WMS-22396] - ai: fixed an issue where the Voice Bot Traces in WMS displayed traces that were already deleted

Note: 

• Traces are stored for 100 days. 

• Also, added possibility to search traces by caller name, bot name or session ID.  

[IT-6881] - ai: updated the logic of AI bundle usage calculation to prevent double-counting of voice bot calls by excluding separate transcription calculations

[WMS-24346] - int: added possibility to log call summary for integrations set up via Integrations Hub

Documentation: How to enable Call Summary for Integrations HubPreview

[WMS-24506] - sys: fixed an issue where the voice bot mispronounced phone numbers, when using ElevenLabs Italian voices

Documentation: How to configure Voice Agents

[WMS-24504] - voicebot: replaced Spanish Voice Bot voices with more native-sounding ones for improved quality

[WMS-24491] - voicebot: fixed an issue where ElevenLabs voices for Voice Bots used incorrect accents 

Documentation: How to configure Voice Agents

[XBS-5990] - wms: added Traces feature to Chat Bots, which helps to debug chat sessions by showing which tools were used, what data was returned, and other related details

Documentation: How to configure AI Chat Agents

[WMS-24316] - ai: added possibility to select the preferred Model (e.g. GPT-4.1, GPT-5, etc.) in Advanced configurations of a Voice bot 

How-to:

1. Go to WMS -> PBX -> Integrations -> Cloud integration -> Voice Bots

2. Select the Voice bot or create a new one

3. Navigate to Advanced configuration -> Model

4. Select the preferred model 

Documentation: How to configure Voice Agents

[WMS-24181] - wda: updated Webhook integration by adding message ID to sms.status webhook 

Documentation: How to set up Webhook integration

[WMS-24118] - wms: fixed an issue in which Chat Bot stopped responding to messages after the Delegate tool was used

Documentation: How to configure AI Chat Agents

[WMS-24225] - ai: added support for extended list of Voices for Voice Bots 

How-to: 

1. Proceed to the Dialplan application Voice Bot 

2. In the Voice field, choose the preferred voice 

Documentation: How to configure Voice Agents

[WMS-23176] - int: added the Integrations Hub in WMS -> PBX -> Integrations -> Cloud integrations,  which allows to integrate Wildix communications solutions with a wide range of CRMs and other systems

• Note: The option is supported starting from WMS 7.03.

See the details and instructions in the documentation: How to Use Integrations Hub

[WMS-23793] - int: fixed an issue with Microsoft Teams Presence Sync integration, where calls made on Wildix side didn’t update the Teams status to “In a call”

[WMS-23779] - wim: fixed an issue when it was impossible to exclude user in Microsoft Teams Presence synchronization settings if user email was too long

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-23322] - wim: fixed an issue in which Microsoft Team Presence integration could not be installed in some cases 

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-23160] - int: improved the logic to avoid an issue in which there were duplicate call entries in HubSpot in case multiple HubSpot integrations were enabled in WMS (e.g. HubSpot, HubSpot Auto Logging)

Note: In case HubSpot and HubSpot Auto Logging integrations are installed, user needs to go to Wildix App settings inside HubSpot -> turn off the option "Enable Logging Activities". By default, the option is enabled.

Documentation: HubSpot Integration - User Guide - English 

[WMS-23083] - int: released new Datev integration installer, which fixes issues during installation of the integration

Documentation: GDrive Link

[WMS-20269] - wda: updated Webhook integration by adding SMS events, which return SMS status for 2-way SMS

Documentation: How to set up Webhook integration

[WMS-22686] - int: updated Apex class API to version 55, which fixes an issue with Salesforce update  

Documentation: Salesforce Lightning Integration - User Guide - English, Salesforce Classic Integration - User Guide - English

[WMS-21802] - wda: added possibility for PBX admin to manage status mapping for Microsoft Teams Presence integration

1. Go to Go to WMS -> PBX -> Integrations -> Cloud integrations tab

2. Click Microsoft Teams Presence

3. Proceed to Presence Mapping section and click Add mapping

4. Choose MS Teams / PBX status in the drop-down menu in front of the “From” field and the preferred corresponding status that should be synced to PBX/ MS Teams in the “to” field

5. To add more status mapping, click +

6. Once filled out, click Save 

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-21810] - wim: improved Microsoft Teams Presence integration by adding possibility to enable/ disable the integration for specific users

How-to: 

1. Go to WMS -> PBX -> Integrations -> Cloud integrations tab -> click Microsoft Teams Presence

2. Click on the Advanced users configuration

3. Select the option Exclude users or Include users 

4. Enter the necessary users email addresses and click Save

When you exclude specific users, presence sync is disabled for them, while for the rest users the integration remains active. When you include specific users, presence sync works only for the mentioned users. 

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-21542] - wda: updated Webhook integration by adding transcription and summary completed events, which include full transcription and summary

The following new events were added to the section Analytics events:

• call:transcription:completed

• call:transcription:text:completed 

• call:summary:completed

• conference:transcription:completed

• conference:transcription:text:completed

• conference:summary:completed

Note: 

• In case of call:transcription:completed / conference:transcription:completed and call:summary:completed / conference:summary:completed the transcription and summary are stored in JSON format.

• The events call:transcription:text:completed / conference:transcription:text:completed store call/ conference transcription in text format. 

Documentation: How to set up Webhook integration

[WMS-21887] - x-hop: added the Dial by name feature for Voice Agents which allows to dial colleagues by pronouncing their name / extension when speaking with a Voice Agent

How-to:

1. In Voice bot settings add the Transfer tool 

2. Choose the option Directory in the Destination field

3. In the Description field, enter instructions for the transfer, e.g. “Transfer the call if user asks. Transfer only to the users who are in the Directory”

For detailed instructions, check out the documentation How to configure Voice Agents

[WMS-22045] - int: fixed an issue with Webhook integration, in which AWS SQS type integration didn’t work for regions other than eu-central-1

Documentation: How to set up Webhook integration

[WMS-20599] - int: fixed an occasional issue in which users were repeatedly logged out of the integration

Documentation: Salesforce Lightning Integration - User Guide - English, Salesforce Classic Integration - User Guide - English

[WMS-20839] - int: fixed an issue with Outlook integration in which calendar sync and contact search didn’t work correctly in some cases

Note: The fix is available with WIService v. 3.18.4

Documentation: What is WIService, Outlook integration for Microsoft Windows

[IT-1575] - int: added possibility to track tasks from the Activity tab in Salesforce via Salesforce Opportunity integration in x-bees, as well as add and edit tasks and change task status

Documentation will be updated soon: /wiki/spaces/DOC/pages/30279050

[WMS-20733] - wim: improved the logic so that user status on PBX is not changed in case status in MS Teams automatically changes to offline after some idle time

[WMS-20484] - int: fixed a rare issue with Salesforce integration, in which Collaboration plugin crashed in some environments

Documentation: Salesforce Lightning Integration - User Guide - English, Salesforce Classic Integration - User Guide - English

[WMS-20172] - int: fixed an issue in which it wasn’t possible to select calendars for sync in Outlook integration 

Note: The fix is available starting from WIService v. 3.18.1. 

Documentation: What is WIService, Outlook integration for Microsoft Windows

[WMS-19834] - wms: fixed an occasional issue with Zoho integration in which after enabling the integration, the Click-to-call feature was not available for some users

To apply the fix, the integration needs to be reinstalled.

Documentation: Zoho CRM integration with Wildix PBX, Zoho Bigin integration with Wildix PBX

[WMS-20009] - wim: fixed an issue with Microsoft 365 Integration with x-bees in which Meeting Scheduler didn’t work if user’s email contained uppercase letters

Documentation: x-bees Meeting Scheduler

[WMS-19813] - int: improved the login logic in Salesforce Lightning and Salesforce Classic integrations by adding notification in case of a CORS error, which requests to check if Salesforce Custom Domain is whitelisted in WMS and provides a button to copy the Custom Domain in one click

Documentation: Salesforce Lightning Integration - User Guide - English, Salesforce Classic Integration - User Guide - English

[WMS-19595] - col: fixed an issue with Microsoft Presence Sync integration in which user presence changed to available when call duration was longer than 15 minutes

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-19601] - int: made some performance and synchronisation improvements to Salesforce Auto Logging integration

Documentation: Salesforce Integration with x-bees - User Guide

[WMS-19887] - int: improved the logic in HubSpot integration to avoid an issue when an unanswered call was logged as an answered one if there was a voicemail

According to the updated logic, all outgoing calls that are less than 15 seconds are logged as unanswered.

Documentation: HubSpot Integration - User Guide

[WMS-19103] - wim: improved the installation process of Microsoft Teams Presence integration 

• In WMS -> PBX -> Integrations -> Cloud Integrations, after clicking Install the integration, the status now changes first to Installing and only after the installation is complete, the status is changed to Installed.

• Added Warning and Broken statuses, displayed in Microsoft Teams Presence section on the Cloud Integrations tab in case of any issues with synchronisation (Warning status), or if the integration stopped working for some reason (Broken). Broken status is also displayed in case of an attempt to install integration with an account which is already used.

[WMS-19614] - wim: added possibility to disable presence sync between Wildix PBX and Microsoft Teams for agents who use phones only, which helps to avoid an issue when user status was displayed as Away when only phone was used 

How-to: Custom extensionAttribute “sipOnly” should be set in users Microsoft Account.

[WMS-19498] - int: fixed an issue in which owner was incorrectly assigned in HubSpot and Salesforce Integrations in some cases

[WMS-19567] - int: fixed an issue with Salesforce Lightning integration in which any unsaved data (e.g. text of an email, etc.) was lost upon receiving an incoming call

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-19076] - int: fixed an issue, in which after ending a call in Zoho integration, “Dialed number is busy” notification was displayed

Note: The fix is supported starting from WMS 6.06.20240315.1

Documentation: Zoho CRM integration with Wildix PBX

[WMS-18543] - int: made updates to Salesforce integration in the view of Google Chrome ending support of third-party cookies 

Important:

With the current update, it is necessary to go to WMS -> PBX -> Integrations -> Cloud integrations and enable the “Salesforce Telephony” integration. Otherwise, users will not be able to log in to the Salesforce integration after the update. For instructions and more details, check the documentation (see the section “Enable Salesforce Telephony in WMS”): 

• Salesforce Lightning Integration - User Guide - English

• Salesforce Classic Integration - User Guide - English

[WMS-18925] - int: fixed an issue with Salesforce Lightning Integration in which outgoing calls were logged as incoming

[WMS-19099] - wim: updated Webhook integration by adding possibility to enable User presence events sending

For details and instructions, see documentation: How to set up Webhook integration

[WMS-18755] - int: removed the option Use HTTP from the “Outlook to PBX synchronization” window in Outlook integration, which made it impossible to connect to the PBX unless HTTP was manually deactivated  

Note: The improvement is available with the updated Outlook contacts Import app, which you can download in the documentation: Outlook integration for Microsoft Windows

[WMS-19128] - int: fixed an issue with Outlook integration in which contact name during a call was displayed incorrectly due to Outlook contact lookup overwriting internal extension number

Note: The fix is available starting from WIService v. 3.17.6

Documentation: What is WIService, Outlook integration for Microsoft Windows

[WMS-17813] - int: fixed an issue in which caller name lookup via Outlook Integration stopped working and caller number was displayed instead of the caller name

[WMS-18003 ] - int: fixed an issue in which new draft emails were generated after enabling Outlook integration

Note: The fixes are available starting from WIService v. 3.17.4

Documentation: What is WIService, Outlook integration for Microsoft Windows

[WMS-18612] - int: fixed an issue with HubSpot integration in which incoming group call was logged multiple times, for every user with the call ringing

Limitation: The first agent in the call group queue should be logged into HubSpot integration, as any missed calls are logged to HubSpot on behalf of the agent who is first in the call group queue. If the agent is not logged in, the missed call may not be recorded in HubSpot.

Documentation: HubSpot Integration - User Guide - English

[WMS-18298] - int: fixed an issue in which outgoing calls placed from Deals and Tickets pages in HubSpot didn’t appear on the Calls tab

Documentation: HubSpot Integration - User Guide - English

[WMS-18502] - wim: fixed an issue in which it was impossible to install MS Teams Presence integration due to an authorization error

[WMS-16922] - wda: added possibility to sync user presence status from Collaboration / x-bees to Microsoft Teams

Notes:

• PBX should be updated to WMS v. 6.05.20231229.4 or higher

• Cloud Analytics should be activated in WMS -> PBX -> Features

• Any other calendar integrations (Google Calendar or Microsoft 365) should be deactivated, otherwise Microsoft Teams presence sync won't work

• Important: If you have previously activated Microsoft Teams Presence, you need to reactivate it for 2-way presence sync

How-to:

• Go to WMS -> PBX -> Integrations -> Cloud integrations

• Click Microsoft Teams Presence

• Click Install and log in to your Microsoft account

• Once your user status is changed in Collaboration/ x-bees, it is automatically aligned in Microsoft Teams

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation.

[WMS-17643] - wim: released a new version of Salesforce integration with x-bees

• The integration is available in WMS -> PBX -> Integrations -> x-bees tab -> Salesforce Automation and performs logging of calls and meetings between PBX users and Salesforce contacts. If you enable the new integration, the logging is performed via the new integration.

• Note: Starting from WMS 6.05.20231110.2, x-bees tab in WMS -> PBX -> Integrations is renamed into Cloud integrations. 

Important: At the current development stage, it is not recommended to disable the old version of Salesforce integration yet, as part of the current functionality (e.g. the display of Salesforce contact information on the Info frame in x-bees) may become unavailable.

Documentation: Salesforce Integration with x-bees - User Guide

[WMS-18677] - wim: added possibility to install HubSpot Automation and Salesforce Automation integrations on PBX with Collaboration licenses 

The integrations perform logging of Collaboration calls and conferences performed to HubSpot or Salesforce, saving the call or meeting record on the relevant contact page in the corresponding CRM. 

[WMS-18141] - int: fixed an issue in which calls were not saved in the Activity section of the relevant contact in Salesforce in some cases

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-18412] - int: fixed an issue in which there was a notification asking for confirmation to leave the page when user wanted to open another tab or another section on the HubSpot page after completing a call

Limitation: In case the option “Hide the popup after the call is completed” is enabled in Settings, which automatically hides Wildix widget, you may face the notification confirming to leave the page if you proceed to another tab or another section in HubSpot in less than 1-2 seconds after completing the call. 

Documentation: HubSpot Integration - User Guide - English

[WMS-18051] - int: added possibility to generate DTMF during a call from Salesforce Wildix integration 

[WMS-18203] - int: improved the logic so that when opening contact details, they are opened in the same Salesforce page rather than in a new browser tab

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-18517] - int: fixed an issue in which incorrect error message (“Unsupported PBX version” instead of “Collaboration not connected”) was displayed when creating a conference in Outlook Integration, when Collaboration was not connected

Note: The fix is available starting from WIService v. 3.16.8.

Documentation: What is WIService, Outlook integration for Microsoft Windows

[WMS-18547] - int: fixed an issue in which Hold button didn’t work in Salesforce integration in case x-bees Web was selected as an active device

Note: The fix is supported starting from WMS 6.05.20231121.1.

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-17641] - wim: released a new version of HubSpot integration with x-bees (currently in Beta)

The integration is available in WMS -> PBX -> Integrations -> x-bees -> HubSpot Automation and performs logging of calls and meetings between PBX users and HubSpot contacts. If you enable the new integration, the logging is performed via the new integration.

Important: At the current development stage, it is not recommended to disable the old version of HubSpot integration yet, as part of the current functionality (e.g. the display of HubSpot contact information on the Info frame in x-bees) may become unavailable.

Documentation: HubSpot Integration with x-bees – Admin Guide 

[WMS-18043] - int: fixed an issue in which some calls were not saved on the Activity and Call tabs in HubSpot and there were occasional pop-ups requesting to reinstall the application

Documentation: HubSpot Integration - User Guide - English

[WMS-18085] - wim: fixed an rare issue in which Microsoft Teams presence sync didn’t work if user’s email contained capital letters

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-17535] - int: fixed an issue in which outgoing call from x-bees and Collaboration was displayed as inbound in HubSpot

[WMS-17656] - int: fixed an issue in which instead of the name, extension of the caller was displayed in call history on the Activity tab in HubSpot

Note: You need to relogin to HubSpot after the update. 

Documentation: HubSpot Integration - User Guide - English

[WMS-17373] - wda: added possibility to configure Webhook integration with third-party web applications and services for sending call related events

For instructions, see documentation: How to set up Webhook integration

[WMS-17747] - int: fixed an issue in which it wasn’t possible to create a contact without email in Salesforce Lightning integration

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-17634] - int: fixed an issue in which a call to a contact was not saved to Activity in HubSpot integration in case the phone number included spaces

Documentation: HubSpot Integration - User Guide - English

[WMS-17683] - int: fixed an issue of Datto Autotask integration not connecting because *.wildixin.com could not be allowed in WIService

Note: The fix is supported starting from WIService v. 3.15.4.

Documentation: What is WIService, How to set up Wildix integration with Datto Autotask

[WMS-17618] - int: fixed a rare issue in which there was an error displaying call history in Salesforce Lightning integration 

Documentation: Salesforce Lightning Integration - User Guide - English

[WMS-17541] - int: made some performance improvements to avoid an issue when calls were not displayed on the Activity tab in some cases if there were multiple HubSpot tabs open

Documentation: HubSpot Integration - User Guide - English

[WMS-17452] - int: fixed PBX domain validation issue in teams4Wildix integration by adding possibility to a) enter custom PBX domain, that may contain numbers and hyphen; b) use different ports to connect, e.g. :8888

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-16767] - int: made some improvements to HubSpot integration which include:

• Added compatibility with x-bees

• Added OAuth 2.0 authorization to provide a more secure authentication mechanism
  Users who already use the integration need to re-connect with OAuth 2.0 Application ID

Consult HubSpot Integration User Guide for details.

[WMS-16406] - wda: added possibility to sync user presence status from Microsoft Teams to Collaboration / x-bees

How-to:

1. Go to WMS -> PBX -> Integrations

2. Proceed to the Calendars tab (or to x-bees tab in case of a PBX with x-bees licence)

3. Click Microsoft Teams Presence

4. Click Install

5. Log in to your Microsoft account

Note:

• Presence sync with Microsoft Teams is part of teams4Wildix integration which requires CLASSOUND license.

• Currently, the sync is performed in one way, from Microsoft Teams to Collaboration / x-bees. User status sync from Collaboration / x-bees to Microsoft Teams is not supported. 

• Make sure you don’t have any calendar integrations (Google Calendar or Microsoft 365) enabled, otherwise Microsoft Teams presence sync won't work.

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

[WMS-15346] - int: made some improvements to Datto Autotask integration which include:

• Stability, name lookup and number detection functionality improvements

• Added a clickable link to user name on the Wildix popup, which opens a separate window with contact information, in case the contact is available in Autotask phonebook 
  Note: To use the feature, pop-ups should be allowed in browser settings 

• Added relevant alerts in case Collaboration tab is closed and if ClickToCall extension is disconnected

Note: ClickToCall extension v. 0.0.4, available by this LINK

Documentation: How to set up Wildix integration with Datto Autotask

[WMS-15117] - int: added the Domain field to Wildix ClickToCall extension -> Datto API variables screen, which allows to indicate any Datto Autotask domain when configuring the integration

Note: ClickToCall extension v. 0.0.2, available by this LINK

Documentation: How to set up Wildix integration with Datto Autotask

[WMS-14688] - int: added support of TLS 1.2 on Datev integration, which fixes Datev connection issues

Documentation: GDrive Link

[WMS-14441] - int: added support of Wildix Collaboration integration with Datto’s Autotask Professional Services Automation (PSA)

Documentation: How to set up Wildix integration with Datto Autotask

[WMS-11916] - int: uploaded Wildix Collaboration to Microsoft Store