Release Date: 2nd June 2026

Key versions included in this release are:

Note - Release marked in bold has the change only, other releases have no change and are the same as delivered in last patch cycle.

EN-1519 || Enable Priority reordering for Call Routing profiles in MultiCC UI

MultiCC Managers can now set the evaluation order of System Routing profiles directly from the MultiCC UI, so the routing rules that matter most are applied first on inbound calls. Managers can reorder Call Routing profiles on the System Routing screen (Call Routing → System Routing) using Up/Down controls. Apply saves the new order with confirmation and password authorization. List order = routing priority: the profile at the top is evaluated first.

EN-1110 || Call Context Distribution at CC level in MultiCC Manager

MultiCC Managers can view, assign, and unassign Call Contexts to Contact Centers from the MultiCC Manager web UI. Call Contexts are the SIP channels used for voice traffic. Previously this could only be done through the legacy Java Client. This release moves the workflow into the MultiCC Manager UI for faster, auditable context assignment.

EN-1333 || Hybrid Log Rotation and Retention

Ameyo ECC now rotates and compresses application logs automatically and retains them for 10 days, reducing disk-full risk and making troubleshooting easier. The platform uses a hybrid log rotation policy with automatic 10-day retention so logs stay available for troubleshooting without uncontrolled disk growth.

EN-1335 || Tenant-Level Channel Restriction in ECC to Prevent Misuse - 4x

Ameyo introduces tenant-level channel restrictions so customers operate within their purchased or allocated channel capacity. Administrators can configure channel limits at the tenant level, and the platform enforces those limits in real time when calls are initiated. This improves platform reliability in multi-tenant deployments and reduces misuse/overutilization.

EN-936 || Publish Micrometer Based Appserver Business Metrics

Ameyo now exposes business metrics from the App Server using a Micrometer-based metrics framework, integrated with Prometheus and Grafana. This provides operational visibility into live contact-center activity: faster incident detection through real-time business KPIs, better capacity and traffic monitoring (calls, campaigns, channels), and improved platform stability tracking.

EN-2080 || Hiding Columns with Only Null Values in Interaction Details Reports

The Interaction Details Report now automatically hides columns that contain only null or NA values. Reports and CSV exports include only columns with meaningful data, making analysis faster and exports more enterprise-ready.

EN-2081 || Displaying Deleted Custom Fields in Interaction Details Reports

The Interaction Details Report now uses historical field accuracy when building report output. Reports reflect the fields that were active when the interaction data was captured, including deleted custom fields in historical date ranges.

EN-1711 || User ID Masking in Amplitude

Analytics events now use a masked (hashed) user identifier instead of raw user IDs, with tenant and domain stored as persistent user properties for safer, more consistent reporting. This strengthens privacy and security in product analytics (Amplitude) across Ameyo CCaaS, Voicebot, and Platform.

EN-1753 || Queue-Level Custom Field Assignment

Queue-level control over custom field assignment is now available, enabling contextual data capture and reducing manual effort. Admins can assign custom fields to specific queues so fields are only available where relevant. A "Copy Custom Fields to all queues" option is available in campaign settings (on by default), with system auto-assign to all queues by default.

EN-2324 || CRM Popup After Connected During Conference

For conference participants, the CRM panel now opens only after the call is answered and reaches the Connected state. CRM is no longer triggered when the conference invitation is received. This eliminates unnecessary CRM/API activity for unanswered conference invitations and prevents CRM from appearing before a participant joins the live conversation.

SL-18173 || Team Members' Lunch Break Auto Removed Issue

Agents in Break status (Lunch, Tea Break etc.) were incorrectly subject to the inactivity timeout mechanism. In certain race-condition scenarios, inactivity timers were not properly cleared, resulting in inactivity warnings and automatic logout during valid breaks. Enhanced the inactivity timeout handling to correctly exclude agents in Break status from inactivity monitoring.

SL-18067 || Error While Transferring to Feedback

Reopening the Transfer popup during an active call could cause issues reinitializing the campaign selection component. Improved the Select2 component initialization and cleanup logic with safer handling during component destruction, preventing errors when reinitializing across repeated popup open/close actions.

SL-18074 (SL-18047) || Interaction Details Report Issue

Users were unable to execute the default Interaction Details Report because the Run button remained disabled. The report validation and button state handling have been corrected, allowing the Run button to become active when the required report criteria are met.

SL-18267 || Email Body Could Not Be Displayed

Some emails failed to display their content because the mail server returned an invalid BODYSTRUCTURE response. A fallback mechanism was introduced to fetch and parse raw email content directly, allowing the system to process affected emails even when standard body structure parsing fails.

SL-18178 || Unable to Download Voicelogs from VLA When Encryption is Enabled

Encrypted voicelog downloads were generating empty (0 KB) ZIP files due to a filename handling regression where encrypted audio files were always assigned an .mp3 extension during processing, causing the decryption process to overwrite its own input. Enhanced the decryption workflow to use a temporary intermediary file during processing.

EN-1119 || Issue in Format of Number in Rule Engine

Fixed an issue where large numeric values (greater than 2,147,483,647) in rule conditions could be automatically converted to scientific notation (e.g. 2.147483647E9) when saved. Numeric values are now converted and stored according to the field's data type, so large numbers remain in the expected format.

SL-18120 || Auto-Correct Issue in WhatsApp Chat

Fixed an issue where auto-corrected text could be sent incorrectly when agents used the Enter key immediately after selecting a spelling correction. The message editor now ensures that auto-corrected text is synchronized before sending.

EN-1126 || Lead Tagging with Different ID

Fixed a bug in auto-dial with preview where using Click-to-Dial (CTD) from CRM while a preview call was in progress could dial a different contact but attach it to the wrong customer. While a preview call is active, CTD from CRM is now blocked with clear UI feedback.

SL-18065 || Ameyo Call Back to Our System

Fixed to ensure the resolved DID (caller ID) can be passed to CRM URLs during manual dialing when using custom nodeflows, improving CRM context and integration accuracy.

SL-18063 || Unable to Login in Ameyo Post Patch Upgrade Activity

Fixed a login issue that could occur after upgrading to newer builds on deployments using custom startup configurations. Users can now log in successfully after upgrade activities, including deployments configured with custom ports and non-default startup environments.

EN-956 || VAPT | Sensitive Info in URL

Addressed a VAPT finding where sensitive session information (session ID and related identifiers) could appear in the browser URL when agents opened embedded applications. Session identifiers can now be omitted from the application URL when a contact-center preference is enabled.

EN-1006 || Implement Debouncing and Button Disable on Email Send Reply Action

When an agent clicks Send Reply, the button is disabled immediately, and debouncing ensures only one send request is processed per action—even if the agent clicks multiple times quickly.

SL-17979 || i18n Japanese Language Support in C019 DOS

Several Japanese language translations identified by the IPS team have been corrected to improve localization accuracy across the platform. The corrected language strings are included in both Application (App Server) UI components and Reporting (ART) components.

EN-1523 || ECC 4.x – SAST Re-Scan Findings

Security improvements based on a third-party SAST (Static Application Security Testing) re-scan. The re-scan initially reported 41 open findings (27 medium, 14 low). All have been reviewed, remediated, or dispositioned, and the vendor re-scan (SecIQ) confirms all issues are closed.

EN-1714 || Routing Issue

Fixed an issue where custom configuration data saved through the Custom Configuration APIs could be altered in the database when values contained single quotes or similar special characters.

SL-18042 (EN-1735) || Supervisor Dashboard | Total Ticket Count Mismatch | Petromin

Fixed a ticket count mismatch on the Supervisor dashboard for email setups. The issue occurred when agents sent outgoing emails including the campaign media profile email address in To, CC, or BCC, which could create invalid interactions counted as tickets.

SL-52 || Customers Mobile Numbers Visible in Ameyo

Customer numbers remain masked on agent toolbar during click-to-dial and dispose when campaign client-side masking is enabled. Fixed a privacy issue where customer mobile numbers could appear in clear text even when campaign client-side masking was enabled.

EN-1544 || Dialers Not Dialing Due to CallManagerConfiguration Single-Threaded Queue Blocking | Traya

Fixed a reliability issue where predictive dialers could slow down or stop placing calls when the platform was under heavy load (e.g., during bursts of voice resource state changes or telephony resets). Predictive dialers no longer stall when handling large volumes of voice-resource and telephony events.

SL-18236 || Data Inconsistency in Queue Details (Missing queueName for Unanswered Calls) | Ather Integration

Fixed to ensure that queueName and agentQueueId are correctly populated in post-processing global variables for missed and transferred call scenarios, including Transfer-to-Campaign calls that went unanswered, Auto Dial missed calls, and Click-to-Call missed calls.

SL-18128 || get-userDetails-by-userName API Failing - Receiving 2 CRM URLs | IIITB

Fixed: When User A transfers a call to User B, only one CRM push is sent with User B's correct credentials. When User A confers with User B, one CRM push is sent with both users' details. When call ownership is subsequently transferred, a new CRM push is sent with only User B's details.

EN-1659 || Extend Lead-to-User Dialing to Support Progressive Mode - 4.x

Progressive outbound campaigns can now use lead-to-agent mapping so each lead is dialed to the assigned agent. When Lead-to-User Dialing is enabled on a Progressive campaign, the system routes outbound calls to the agent mapped to each lead, instead of using standard Progressive distribution.

EN-1688 || Caller Leg Disconnects if Agent Disposes the Call During Re-ACD Phase

Fixed an issue where the customer's call could disconnect if disposeCallForUser was used for an agent who had not yet answered the call (during ringing or Re-ACD). The platform now validates that the agent was connected before allowing disposition. The customer call continues when dispose is requested for a non-connected agent, and Re-ACD/post-ACD IVR behave as designed.

EN-2315 || CRM Push Behavior During Conference

Fixed CRM integration when an agent conferences a call to another user. When User A conferences an active call to User B, the platform now sends one CRM push with the correct details for User B (Session ID, User ID, User CRT Object ID), and also retains additional CRM URL parameters that were present when the call was first connected with User A.

Chrome Version: Version 148.0.7778.179 (Official Build) (arm64)