XCALLY Changelog

XCALLY Changelog

The Motion versioning follows the Semantic Versioning guidelines.
In this changelog you can find our main versions, with updates and improvements, while in Advanced Changelog (dedicated to XCALLY partners and stakeholders) you can view the details of all released tasks.

Remember to Hard Refresh and clear Application Data in your browser after the update

[If you need to explore the previous changelog click on the relative year: 2025 | 2024 | 2023 | 2022 or find out Phonebar Changelog]

 

Last Version

 

 

Last Version

 

XCALLY

3.67.0

Warning: Starting from version 3.66.0, microservices are mandatory. Do not upgrade to this version unless you have already installed the microservices and they are fully operational in your environment. You can check if microservices are already installed, by following this guide, otherwise you can explore how to install microservices

Release Date:
Aug 4, 2026

Asterisk

Recommended Version:
20.18.2

Link to update:
Asterisk Update

Important Notice: Redis Container Requirement

Starting from version 3.34, a dedicated container including a Redis instance was introduced to support QA-related functionalities. Beginning with version 3.57.0, the presence of this container has become required for several core platform features.

To ensure full compatibility and access to all new capabilities, it is mandatory to perform a complete installation of all microservices (procedure available on Advanced wiki), which includes:
- the Redis container (bullmq-v1) --> discover how to check Redis installation (Advanced wiki)  
- the new real-time dashboards
- the system monitoring components available through Grafana.
Alternatively (less recommended option), it is possible to install only the bullmq-v1 container to meet the minimum requirements. However, this configuration will not provide the enhanced monitoring and real-time features introduced in recent versions.

Important Notice: Redis Container Requirement

Starting from version 3.34, a dedicated container including a Redis instance was introduced to support QA-related functionalities. Beginning with version 3.57.0, the presence of this container has become required for several core platform features.

To ensure full compatibility and access to all new capabilities, it is mandatory to perform a complete installation of all microservices (procedure available on Advanced wiki), which includes:
- the Redis container (bullmq-v1) --> discover how to check Redis installation (Advanced wiki)  
- the new real-time dashboards
- the system monitoring components available through Grafana.
Alternatively (less recommended option), it is possible to install only the bullmq-v1 container to meet the minimum requirements. However, this configuration will not provide the enhanced monitoring and real-time features introduced in recent versions.
Consider that some features are available only on New Client Experience. If your server was installed before July 27, 2023, run the following script to update the NGINX configuration (standalone or all-in-one installations only - if you have HA, DR, reverse proxy etc you need to contact our support team):
curl -u 'public:bs4#)W]h8+VK),RV' --silent --location https://repository.xcally.com/repository/provisioning/Scripts/motionV3_nginx_update_for_x_client | bash
To avoid issues, we recommend launching the script while agents and users are not logged in to the system. Consider that, by running the script, a new NGINX configuration file will be installed while the old client configuration file will be saved as a backup at the path indicated in the script. Any custom changes made by the user will not be automatically carried over.

Important Notice – Debian and MySQL
Starting from the XCALLY Motion release 3.59.0, we support Debian 13 and we suggest it as operating system.

Furthermore the MySQL 8.0.X version, currently included in the XCALLY Motion installation, will reach End of Life in April 2026. For this reason, starting from the XCALLY Motion release 3.59.0, we support MySQL 8.4.X version.

  • For new servers: the installation will automatically include the MySQL 8.4.X.

  • For existing servers: A manual update procedure to upgrade to MySQL 8.4.X is available at this link on Advanced wiki (Jira credentials required).
    Manual upgrade to MySQL 8.4.X is strongly recommended only starting from release 3.59.0.
    Previous versions contain a Foreign Key not fully compatible with the constraints introduced in MySQL 8.4.


Version 3.67.0

Aug 4, 2026


Updates & Improvements

[XM-5492] Added new typology “VoiceBot" when creating an agent to enable integration with XCALLY Virtual AI Agent, a customizable AI platform that lets organizations design, build, configure, and manage intelligent virtual agents tailored to their business requirements. Virtual AI Agent is available only for voice channel → XCALLY Virtual AI Agent (Advanced wiki)

[XM-5505][XS-15923] Increased limit on WhatsApp template variables, so users can now create templates with more than 9 variables

[XM-5540][XS-16071] Implementation to configure Dynamic URL variables in Call To Action buttons inside templates creation → Dynamic URLs in CTA buttons

[XM-5626][XS-15339] Improvement of application's login security (both via user interface and direct API requests) with IP-based rate limiting and reCAPTCHA added after multiple failed login attempts. New security settings have been added for administrators to settings DB table → General Settings | Security | Motion DB Tables - Settings

Advanced Release Notes - New database columns:

settings table

  • rateLimitEnabled

  • rateLimitMaxAttempts

  • rateLimitWindowMinutes

  • rateLimitBlockMinutes

  • loginCaptchaEnabled

  • loginCaptchaSiteKey

  • loginCaptchaSecret

  • loginCaptchaAfterAttempts

  • loginCaptchaMinScore

 

Version 3.66.0

Jun 18, 2026

Updates & Improvements

Warning: Starting from version 3.66.0, microservices are mandatory. Do not upgrade to this version unless you have already installed the microservices and they are fully operational in your environment. You can check if microservices are already installed, by following this guide, otherwise you can explore how to install microservices

[XM-5159] Added new settings and configuration fields related to the new XCALLY Dialer V2:

Please note that the new XCALLY Dialer (V2) is currently in Beta and is available only for IVR campaigns. Discover more

The legacy dialer remains available and continues to support all existing features.

Advanced Release Notes - New database columns:

settings

  • maxConcurrentIvrCalls

  • maxConcurrentDialerCalls NOT SUPPORTED YET

campaigns

  • priorityRetry

[XM-5237] Added support for Call Permission Request (to ask customers if you can call them on WhatsApp) when creating WhatsApp Marketing and Utility templates using Meta. Added the ability to import existing Call Permission Request templates from Meta through the Import/Sync function → WhatsApp Templates | Create a template

WhatsApp calling is not yet available. This enhancement is preparatory work to support WhatsApp Calls in future releases. While Call Permission Request templates can already be created and synchronized, the actual calling functionality will be introduced in a later version.

Advanced Release Notes - New database column:

whatsapp_template_messages

  • metaSubCategory

[XM-5524][XM-5525][XM-5527][XM-5530] Added new settings and configuration fields to allow the integration between the new XCALLY Dialer (V2) and List Manager under:

Please note that the new XCALLY Dialer (V2) is currently in Beta and is available only for IVR campaigns. Discover more

The legacy dialer remains available and continues to support all existing features.

List Manager solution is currently in Beta version. Please contact sales@xcally.com to receive information on how to access the Beta program.

Advanced Release Notes - New database columns:

settings

  • listManagerUrl

  • listManagerApiKey

campaigns

  • listManagerEnabled

  • listManagerCampaignId

[XM-5528][XM-5581] Added option to enable the new dialer (V2) in the IVR campaigns during creation process. Furthermore in the campaigns list there are two new columns to show the dialer version (V1 or V2) and if the List Manager integration is enabled → IVR Campaigns | Create the IVR Campaign

Please note that the new XCALLY Dialer (V2) is currently in Beta and is available only for IVR campaigns. Discover more

The legacy dialer remains available and continues to support all existing features.

List Manager solution is currently in Beta version. Please contact sales@xcally.com to receive information on how to access the Beta program.

Advanced Release Notes - New database column:

campaigns

  • dialVersion

[XM-5532][XS-15977] Updated the database encoding to fully support emojis, allowing WhatsApp templates containing emojis to be created and synchronized successfully

Version 3.65.0

May 14, 2026

Updates & Improvements

[XM-5212] Improved information details in WhatsApp Meta Campaigns Hopper when attempting to contact a customer with an invalid phone number (that causes message failure due to external service/provider error):

  • If the invalid number has less than 20 characters, it is added to Hopper History with the reason “Message undeliverable”.

  • If the invalid number exceeds 20 characters, it is added to Hopper History with the reason “Number exceed length limit. Phone number must not have more than 20 digits” WhatsApp Outbound Campaigns | Hopper History

[XM-5413] Improved the agent experience when using the real-time translator for digital channels:

  • Translations are now displayed while typing, ensuring messages are sent only after translation is completed, and allowing agents to easily change or disable translation.

  • The selected language is preserved after page refresh.

  • Additional fixes improve message flow, handle delays, and prevent sending untranslated messages. → Real-time Translator | Improved Agent Experience

[XM-5476] Improved WhatsApp block lists: it is now possible to add multiple block lists to the same campaign. In addition, invalid numbers are no longer automatically added to block lists by default → WhatsApp Outbound Campaigns | Contacts Block List

[XM-5501][XS-15905] Improved Phonebar agent settings: for newly created Phonebar agents, the transport field is now automatically set to both UDP and TCP by default, ensuring compatibility with different communication needs --> Phonebar Agents Tipology | Voice

 

Version 3.64.0

Apr 16, 2026

Updates & Improvements

[XM-5104][XS-15055] Update on validation for the wrap-up time setting in Voice → Queues → Edit Settings. It is now possible to set the wrap-up time value to 0 when ACW is not enabled → Wrapup time and ACW

[XM-5052] Added Contact Batch Size Field in WhatsApp campaigns creation and editing, to define the number of contacts to be processed in each batch. In case of value set to 0, a warning message appears to users to guide them on correct input → Create WhatsApp Outbound Campaigns

Advanced Release Notes - New database column:

  • contactsBatchSize

[XM-5206] Added the possibility to import WhatsApp templates, already created and available on Meta (instead of recreating them manually), of Marketing-default and Utility-default without attachment tipologies. Unsupported templates are instead skipped Import of WhatsApp templates already created on Meta

[XM-5211] Added validation to prevent configuring multiple WhatsApp accounts with the same Meta number, showing an error message indicating which account is already using the duplicate number → Configure a WhatsApp Account on XCALLY

[XM-5226] Update on WhatsApp channel to handle polls messages, that are unsupported message types. When customers try to send Polls from their WhatsApp numbers, agents will receive the message configured under WhatsApp Account “Unsupported type of message text”

[XM-5295][XS-15787][XS-15397] Added support for parsing JSON output from "System" blocks in Digital Channels, allowing multiple variables to be extracted and assigned without needing multiple blocks → Support for parsing JSON output from System blocks for digital channels

[XM-5319] Added fields Privacy Policy URL, Terms of Use URL, Business Name and Business Address in the WhatsApp Channel account to ensure compliance requirements. The Privacy Policy and Terms of Use pages are generated dynamically for each WhatsApp account using Business name and Business Address inserted data (and any changes to these fields are automatically reflected in the Privacy Policy and Terms of Use) → WhatsApp Accounts | Privacy Policy and Terms of Use

Advanced Release Notes - New database columns:

  • businessName

  • businessAddress

[XM-5407] Improved internal messenger for agent and user collaboration, by adding desktop notifications for new incoming messages when the user is not actively viewing the tab. Moreover the chat list has been updated to properly show the chat order, showing the most recent conversations first → Internal messenger | Desktop notifications

[XM-5418][XS-15700] Implemented the HMAC-SHA256 token system authentication for recording download (instead of MD5 token based on the recording ID): new links are cryptographically signed with a server-side secret that is never exposed in the URL. Existing MD5 links remain functional for backward compatibility, while new recordings will automatically follow this strict authentication, preventing unauthorized access → Voice Recordings | Edit Voice Recordings

 

Version 3.63.0

Mar 19, 2026

Updates & Improvements

[XM-4618] Improved the WhatsApp template synchronization process in XCALLY: WhatsApp Templates deleted in Meta, are now deleted also in XCALLY

[XM-5023][XS-15156][XS-15299][XS-15394] Added new Whatsapp campaign configuration fields Loop campaigns, Clean hopper pending contacts and Default number of contacts to load per campaign batch sending under Settings → General → WhatsApp Campaigns → General Settings | WhatsApp Campaigns

Advanced Release Notes - New database columns:

  • whatsappCampaignsLoopInterval, default 10

  • whatsappCampaignsHopperCleanupInterval, default 60

  • whatsappCampaignsContactsBatchSize, default 20

[XM-5046][XS-14799][XS-15210] Update on WhatsApp channel to allow more flexibilty on contacts management: the button Send a recontact template is always available and the tooltip “Send a contact template to continue the conversation” has been added in case of Meta rejection due to the absence of an active customer service window → Customer service window management from version 3.63.0

[XM-5125][XS-15096] Added automatic contact creation in Contacts Manager when sending a new outbound WhatsApp message to a number that is not yet saved as a contact → Contact creation for outbound messages

[XM-5219] Implementation of contacts block list on WhatsApp channel to prevent them from receiving WhatsApp campaign messages → WhatsApp Contacts Block List

Advanced Release Notes - New database updates:

  • whatsapp_campaign_has_block_list: created junction table (both integer, primary keys, foreign keys)

  • whatsapp_hopper: updated enum in status field to include 'BLOCK_LIST'

  • whatsapp_hopper_history: updated enum in status field to include 'BLOCK_LIST'

[XM-5220] Implementation of reactions support on WhatsApp channel → WhatsApp | Reactions support

Advanced Release Notes - New database updates:

  • whatsapp_messages: updated enum in type field to include 'reaction', 'unsupported'

[XM-5225] Added support for Contact card messages on Whatsapp Channel → WhatsApp | Contact Card Messages

Advanced Release Notes - New database updates:

  • whatsapp_messages: new column specialData useful to support WhatsApp special data content

[XM-5227] Added advanced WhatsApp channel settings to enable “Text Only” mode and configure the “Unsupported type of message text” displayed to customers, when they send unsupported media messages → WhatsApp Accounts | TextOnly Channel

Advanced Release Notes - New database column:

  • textOnlyMode: default false

  • unsupportedMessageText

[XM-5230] Added a new WhatsApp Campaigns report under Analytics → Reports → WhatsApp Campaigns report

Advanced Release Notes - Analytics reports updates:

  • analytics_default_reports: added WhatsApp Campaigns report and fields

  • analytics_custom_reports: added WhatsApp Campaigns report and fields

 

Version 3.62.0

Feb 23, 2026

Asterisk major upgrade from 18.x to 20.x

The upgrade from Asterisk 18.26.0 to 20.18.2 (fully supported) is now available, ensuring improved security, stability, and performance.

Please check this page for upgrade instructions (Advanced wiki, Jira credentials required)

From version 3.62.0, a new XDR update is available.

It focuses on optimizing the product reporting system to standardize data across reporting tables and ensure accurate and reliable call history reconstruction.

The DB tables involved are: report_call, report_call_transfer, report_dial, report_queue, report_member, report_agent, voice_recordings, voice_conversations.

To apply the new XDR update, you must set before the update the XC_XDR_MODE variable to migration2026 in the .env file.

Read the documentation here (Advanced wiki, Jira credentials required)

 

Updates & Improvements

[XM-4686][XS-14365] Improvement to update plugins to new version, directly from the interface --> Upload a Plugin

[XM-4775] XDR - Refactory and improvements on tables report_call, report_call_transfer, report_dial, report_queue, report_member, report_agent, voice_recordings, voice_conversationsEnvironment variables - Advanced Wiki | XDR Updates - Advanced wiki
To apply the new XDR update, you must set before the update the XC_XDR_MODE variable to migration2026 in the .env file.

Advanced Release Notes - New ENV variable:
Remember to follow the guide at this link on Advanced wiki to add or edit environment variables

XC_XDR_MODE

Values:

  • migration2026: reports are generated with the new system available from version 3.62.0.

  • legacy-full: reports are compiled with the old system

  • legacy-withSafeguards: reports are generated with the old system. The new system runs in parallel and intervenes occasionally to prevent memory leaks. Default value.

[XM-5241][XS-15242] Added new mandatory NoResponseTimeout (ms) parameter for the Tilde integration in the Cally Square Tilde ASR Transcribe block to handle socket response timeouts → Tilde ASR

 

Version 3.61.0

Jan 22, 2026

Updates & Improvements

[XM-3778] Implementation of Quality Analysis Dashboards → Quality Analysis Dashboards

[XM-4976][XS-14740] Implementation of Chirp3 Voice Type in Google TTS Cally Square block for Spanish and English languages

[XM-5242] Update of the API returning the QR code to enable MFA

[XM-5284][XS-15156] Optimized database access in WhatsApp campaigns