Read more →

🚀 Acefone - August 2026 Product Release Notes

What's shipping this month: Granular call permissions, BYOS recording folder structures, webhook encryption, SIP Trunking enhancements, a new Flows workspace, and a comprehensive wave of security and reliability improvements across the platform.

📋 Table of Contents

• 🔗 Interaction Hub (UIX)
• 📊 Insights
• 📲 Dialer
• 🖥️ Console
• 🔗 Integrations
• 🌐 API & Webhook
• 🎙️ Voice Streaming & SIP Trunking
• 📋 Contacts & Campaigns

🔗 Interaction Hub (UIX)

✨ New Features & Improvements

1. 🗂️ Precise Time Group Deletion

Audience: Admin

Time Group deletion logic has been corrected so that removing a single time group no longer deletes every configured time group on the account.

Benefits:

• Admins can safely delete an individual time group without risking loss of other configured groups
• Reduces the need for support intervention or manual reconfiguration after accidental data loss

How to use:
Delete a time group as usual from the Time Group settings. Only the selected group will be removed.

2. 📁 Configurable Folder Structure for BYOS Call Recording Delivery

Audience: Admin / Supervisor

Customers using their own storage (AWS S3 or SFTP) can now choose how call recordings are organized: Default, Number-wise, or Department-wise directory structures.

Benefits:

• Simplifies compliance audits and recording management for enterprises handling large volumes of recordings
• Gives admins flexibility to structure storage in a way that matches their internal reporting or retrieval needs

How to use:
Navigate to your BYOS recording delivery settings and select your preferred folder structure: Default, Number-wise, or Department-wise.

3. 🚫 Restrict Hangup Access in Active Call Section

Audience: Admin

Admins can now disable the Hangup action for specific users or roles in the Active Call section, while keeping Listen, Transfer, and Copy Call ID available.

Benefits:

• Prevents unauthorized call disconnections without restricting an agent's other call handling capabilities
• Gives admins finer-grained control over call management permissions

How to use:
Go to User Roles → General Permissions and configure Hangup access for the required role.

4. 🔔 Sound Alert on Call Hangup

Audience: Agents

A beep sound now plays when a call is disconnected, giving agents a clear audio cue that the call has ended.

Benefits:

• Reduces the chances of agents missing a call disconnection when relying purely on visual cues
• Improves overall call handling awareness during active sessions

🛠️ Bug Fixes

📊 Insights

✨ New Features & Improvements

1. ⚙️ Client Teams Can Now Manage Their Own PCA Config

Audience: Admin / Supervisor

Client team members can now view and update PCA configuration directly, based on role and permission settings.

2. ✅ Accurate Call-Answer Detection for Click-to-Call (C2C)

Audience: Users / Admin / Supervisor

C2C calls are now marked "Answered" as soon as Leg 1 connects, instead of waiting for both legs.

3. 📋 CDR Now Displays Agent Number for C2C API Calls

Audience: Users / Admin

CDR records now show the agent's number for calls dialed via the C2C API.

4. 🔍 Filter Insights Call Logs by Agent or Team

Audience: Users / Admin / Supervisor

Call logs in Insights can now be filtered by individual agent or team group.

5. 🔐 Strengthened API Security — UserID Validation & SQL Injection Prevention

Audience: Admin

Insight/v3 APIs now validate user ID from the token, and queries are parameterized/sanitized to prevent SQL injection.

6. ⚡ Insights Iframe Load Time Optimized

Audience: Users / Admin / Supervisor

Visualization load time inside the Insights iframe has been reduced from 3+ seconds to near-instant.

🛠️ Bug Fixes

📲 Dialer

✨ New Features & Improvements

1. 📡 Add Inbound Queue Name in Webhook Response Payload

Audience: Admin

The webhook response payload for inbound calls now includes a queue_name field, returning the name of the ACD queue the call was routed through.

Benefits:

• Developers and integrations consuming webhook data can now identify which inbound queue a call originated from without making additional API lookups, making it easier to correlate call activity with specific queues in downstream systems such as CRMs, reporting tools, or custom workflows

How to use:
No configuration changes required. If you have an active inbound webhook, the queue_name field will appear automatically in the payload for calls routed through a named queue. Review your webhook listener or integration to map and use this new field as needed.

2. ⏱️ Resolve Inconsistent end_time in Activity Logs

Audience: Backend Optimisation

Activity logs now record a consistent end_time for all agent activity entries. Previously, certain activity records were missing or displaying incorrect end timestamps.

3. 🏢 Add Company Name to Scheduled Callback Reminder Notification

Audience: Agents

Scheduled callback reminder notifications now include the company name associated with the contact, alongside the existing callback details.

4. 🌐 Restrict Webform Launch to Connected Calls and Add Configurable Post-Call Availability Timer

Audience: Admin

The webform panel now launches only when a call is connected, preventing it from opening on unanswered or missed calls. Administrators can configure a post-call timer on a webform; once the call ends, the webform automatically closes when the timer expires.

Benefits:

• Agents are no longer interrupted by webforms on calls that were never answered, keeping their workspace focused and relevant
• The configurable timer ensures webform data is submitted or dismissed within a defined window after each call, reducing incomplete entries and supporting consistent wrap-up discipline

How to use:
When assigning a webform to a campaign or dialer configuration, select the webform with the timer enabled. No additional action is needed for the auto-restriction on unanswered calls — this applies automatically once a configured webform is in use.

5. 💬 Enable Automated SMS Triggering Based on Call Disposition

Audience: Agents

Agents can now trigger automated SMS messages based on the call disposition they select at the end of a call. When creating or editing a disposition, admins can attach an SMS template to it — so each time that disposition is applied, the configured message is sent automatically.

Benefits:

• Eliminates manual follow-up for routine post-call communications such as confirmations, callbacks, or next-step instructions
• Reduces agent wrap-up time and ensures consistent messaging regardless of which agent handles the call

How to use:

• Admins: When creating or editing a disposition, select the SMS option under custom settings and choose the SMS template to attach
• Agents: Select the relevant disposition at the end of a call — the linked SMS will be triggered automatically with no additional steps required

🛠️ Bug Fixes

🖥️ Console

✨ New Features & Improvements

1. 🔢 Number Destination to Streaming Service

On the Numbers edit page, admins can now assign a number directly to a Streaming Service destination from the "Select an Action" dropdown. Selecting this destination immediately links it to the number, and clicking through on the destination takes the admin straight to the Channels page to complete configuration.

Benefits:

• Faster setup — assigning a number to a streaming destination and reaching its configuration takes one click instead of navigating separately
• Reduces the chance of a number being assigned but left unconfigured, since the Channels page is just one click away

How to use:
Navigate to Numbers → select the number to edit → under "Select an Action," choose Streaming Service as the destination. The number is assigned instantly. Click the destination to go directly to the Channels page and complete setup.

2. 📦 Inventory Enhancement

The number inventory view has been enhanced to give admins a cleaner, more organized view starting right from number assignment, along with full visibility and audit history for every number.

Benefits:

• Easier to track how and when each number has been assigned or modified
• Full audit history improves accountability and troubleshooting for number-related issues
• Cleaner interface makes it faster to locate and review numbers in inventory

3. 💳 Manual Charge — Allow Negative Balance

The Manual Charge option now includes an additional setting that allows an admin to push an account balance into negative — even when the account has no remaining balance.

Benefits:

• Gives admins flexibility to process a charge in situations where waiting for a top-up isn't practical
• Avoids blocked transactions for edge cases where a manual charge needs to go through regardless of current balance

How to use:
Navigate to Manual Charge → [locate account] → enable the new "Allow Negative Balance" option → proceed with the charge as usual.

4. ⚙️ Login Pages — NextJS Migration

Audience: Backend Optimization

The login pages have been migrated to the NextJS framework as part of an ongoing move toward a more scalable, modular backend architecture.

5. 🔀 AdminSSO Redirection to Console SSO

Users who access the old AdminSSO route are now automatically redirected to the new Console SSO route.

🔗 Integrations

✨ New Features & Improvements

1. 🔁 Dialer Integration Events — Failed Logs Retry BETA

Audience: Admin / Supervisor

A new Integration Events tab on specific integration pages (for CRMs supporting backend call logging — Salesforce, Zoho, Freshsales, LeadSquared, etc.) shows failed ticketing/call-logging records with response code stats, filters, and retry options — plus a backend retry engine, clearer error messages, and 15-day retention.

Benefits: Faster diagnosis, self-serve recovery, zero disruption — isolated build and safe.

How to use:
No additional configuration required. Click Integrations icon → X CRM Dialer Integrations → Integration Events.

2. 🛍️ Integration Marketplace — Refactor

Audience: Admin / Supervisor

A visual and structural refresh of the Integrations — new style/format for CRM integration pages, an upgraded package download section, and richer, better-organized info per integration: overview & setup guides, settings, resilience notes, testing suite, and integration events — all consolidated under one unified view instead of scattered across separate pages.

Benefits: One-stop view, better onboarding, cleaner downloads, and modern look.

How to use:
Go to Integrations → Open any integration — all details (Info, Settings, Resilience Notes, Test Integration, and Integration Events) are now under one roof.

3. 📞 WebRTC in Standard App Integration BETA

Audience: Agents

The WebRTC Calling (Beta) capability introduces a fully embedded calling experience within the IAS Standard App Integration. Agents no longer need an external phone, hardphone, or third-party softphone to make or receive calls. Voice connectivity is now established directly inside the IAS iFrame using WebRTC, enabling the complete call lifecycle to be managed from a single interface. Available for all standard CTI integrations.

Benefits: More streamlined and efficient calling experience for both administrators and agents.

How to use:
Go to Integrations → Open any Standard integration — you'll find a new option of Webphone while integrating. Also, under Integration Settings → Agent Settings to switch between phone/extension/webphone.

4. ⚙️ Standard Integration Settings — Calling Method Switch and Auto Logging Control

Audience: Admin / Supervisor / Agents

Customers can now easily check the currently integrated calling mode and control it, along with Auto Ticketing/Logging, for all IAS integrations — without needing to reintegrate the user to switch to a different calling method or disable auto ticketing.

Benefits: Clears the overhead of reintegrating a user to achieve different modes, and surfaces the currently enabled mode — which was not visible before.

How to use:
Go to Integrations → Open any Standard integration → Settings → Agent Settings.

5. 🧪 Integration Testing Suite — HPBX

Audience: Admin / Supervisor / Agent

Enabled Admin/Users to execute integration health checks on behalf of already-authorized agents while preserving the existing ownership and authorization model.

Benefits: Provides more comprehensive validation of CRM permissions and entity accessibility. Improves the accuracy, reliability, and operational efficiency of integration diagnostics while minimizing support intervention.

How to use:
Go to Integrations → Open any Standard integration → Test Integration → Select Authorized User & Run Tests.

6. 🔐 HubSpot OAuth Upgrade and Enhancements

Audience: Agents

Migrated the HubSpot integration from the legacy OAuth v1 APIs to the new date-based versioned OAuth APIs for token issuance, introspection, and revocation. The CRM Settings page now also displays the connected HubSpot Account Name, allowing administrators to easily identify the linked workspace.

Benefits:

• Prevents service disruption caused by HubSpot's legacy OAuth API deprecation
• Improves the security and maintainability of the HubSpot authentication flow
• Provides clear visibility into the connected HubSpot account, reducing configuration errors

How to use:
No additional configuration required for the OAuth Upgrade. For the connected account name: Go to Integrations → Open HubSpot Standard integration → Settings → Agent Settings and click Fetch Profile Details.

7. 🔧 Refactored CTI App Improvements — Freshdesk, Freshsales, Zendesk, and Salesforce

Audience: Agents

CRM integration packages have been updated to the latest supported dependency versions, addressing identified security vulnerabilities. CTI applications for Freshdesk, Freshsales, Zendesk, and Salesforce have been refactored to improve code quality, maintainability, and long-term scalability. A banner for available upgrades is now available.

Benefits:

• Reduces security risks by addressing known package vulnerabilities
• Ensures continued compliance with evolving CRM marketplace standards
• Improves application stability and maintainability for future enhancements
• Delivers a seamless upgrade with no disruption to existing customer workflows

How to use:
Go to Integrations → Open X CRM Standard integration → Install Latest Package to CRM → Log into the new IAS experience.

8. 🔑 Dialer SSO Compatibility for CRM

Audience: Agents

Single Sign-On (SSO) support has been implemented across all supported Dialer CRM integrations. Validation for token persistence, session management, and logout behavior has been added, and authentication, session handling, and user access flows have been standardized across CRM platforms.

9. 🛡️ Internal Enhancements & Vulnerability Fixes

Audience: Internal

The Event Consumer Service has been replaced with a synchronous processing model to simplify the CRM authorization workflow and reduce processing dependencies. SQL Injection (SQLi) vulnerabilities within the Dialer and CRM authorization flows have also been resolved.

Benefits:

• Improves platform security by protecting against SQL Injection and unauthorized resource access
• Reduces operational complexity by eliminating the dependency on the Event Consumer Service
• Helps maintain compliance with secure development and application security best practices

🛠️ Bug Fixes

🌐 API & Webhook

✨ New Features & Improvements

1. 📇 Webhook Enhancement: Rich Contact Metadata for Video Meetings

Audience: Admin / Supervisor / Developer

The Video Meeting Webhook has been enhanced to include all customer-configured Contact Custom Fields within the contact_details object of the webhook payload. Previously, the payload contained only standard contact information such as Contact ID, Contact Name, and Contact Number. Any custom fields configured for contacts (e.g. Email ID, Company Name, Address, Alternate Phone Number, LAN Number) will now be automatically included whenever values are available.

Benefits:

• Eliminates the need for additional API calls to fetch contact custom field data
• Provides richer contact context directly in webhook notifications
• Simplifies integration with external CRM, analytics, and workflow automation platforms
• Enables customers to consume both standard and custom contact information from a single webhook payload
• Reduces integration complexity and improves overall processing efficiency

How to use:
No additional configuration required if you are already using the Video Meeting Webhook.

1. Ensure the required Contact Custom Fields are configured and populated in your Acefone account
2. Continue using the existing Video Meeting Webhook endpoint
3. Upon meeting completion, the webhook payload will include the configured custom contact fields within the contact_details object
4. Update your webhook consumer, if required, to parse and utilize the additional fields

Note: Only configured custom contact fields with available values are included. External Reference ID is not included as part of this enhancement.

2. 📡 Observability Enhancement: Kafka & Webhook Logs Enabled by Default for Existing Customer Accounts

Audience: Admin / Supervisor / Developer

Kafka has now been enabled by default for all existing customer accounts where it was previously disabled. As part of this change, Webhook Logs are also automatically enabled for these accounts, bringing them in line with the behavior already available for newly created accounts.

Benefits:

• Standardizes Kafka and Webhook Log availability across both new and existing customer accounts
• Eliminates manual enablement requests, reducing operational effort
• Provides immediate access to Webhook Logs for easier troubleshooting and debugging
• Improves observability and monitoring capabilities for webhook integrations
• Ensures a seamless experience without affecting existing customer configurations

Note: The Unique Caller Attempt (Webhook) setting will remain as-is — if currently disabled, it stays disabled; if enabled, its existing value is preserved. This enhancement applies only to legacy accounts where Kafka was previously disabled.

3. 🗑️ Click-to-Call Support API: Removal of Deprecated call_id Response Parameter

Audience: Admin / Supervisor / Developer

The Click-to-Call Support API response has been simplified by removing the deprecated call_id parameter, which was always returned with a null value. The API will continue to return ref_id as the supported unique identifier for tracking the call request.

Benefits:

• Removes redundant and unused response fields
• Eliminates confusion caused by the always-null call_id parameter
• Standardizes the API response by using ref_id as the single unique identifier
• Simplifies API integration and response parsing

How to use:
No changes required if your integration already uses the ref_id field. Remove any dependency on the deprecated call_id field and update your response parsing logic if applicable.

Updated Response Example:

{
  "success": true,
  "message": "Originate successfully queued",
  "ref_id": "7124bebd-3XXXXXXXXXaeb-f772080c8f01"
}

4. 🔒 New Security Center in API Connect for Webhook Payload Encryption (AES-256-GCM)

Audience: Admin / Supervisor / Developer

A new Security section has been added to the API Connect page, enabling you to configure and manage AES-256-GCM encryption for your Webhooks from a centralized interface.

Using the Security Center, you can:

• Generate and manage your AES-256-GCM encryption key
• Configure the Initialization Vector (IV) delivery method
• Automatically apply encryption to newly created Webhooks
• Assign encryption to existing Webhooks
• Manage all Webhook encryption settings from a single location

Note: AES-256-GCM encryption is currently supported only for Webhooks. API encryption is not included in this release.

Benefits:

• Protects sensitive webhook payloads with industry-standard AES-256-GCM encryption
• Provides centralized management of Webhook encryption settings
• Simplifies the process of enabling encryption for both new and existing Webhooks
• Reduces manual configuration with automatic application to newly created Webhooks
• Helps organizations meet enhanced security and compliance requirements

How to use:

1. Navigate to API Connect → Security
2. Open the AES-256-GCM configuration
3. Generate or configure your 256-bit encryption key
4. Select your preferred IV delivery method
5. Enable Auto-apply if you want encryption automatically enabled for all newly created Webhooks
6. Assign AES-256-GCM encryption to your existing Webhooks
7. Click Save

Important: Ensure your webhook endpoint is capable of decrypting AES-256-GCM encrypted payloads using the configured shared encryption key before enabling this feature.

5. 🔗 Call Operation APIs Now Support ref_id for Call Control

Audience: Developer

The Call Operation APIs now support ref_id as an additional identifier for performing live call operations. Previously, these APIs accepted only call_id, requiring customers to first map the ref_id returned by Click-to-Call APIs to a corresponding call_id. You can now use either call_id or ref_id to perform the following operations: Transfer, Conference / Barge.

Benefits:

• Eliminates the need to map ref_id to call_id before initiating call operations
• Simplifies integrations with Click-to-Call and Click-to-Call Support APIs
• Enables a consistent identifier (ref_id) across API responses, Webhooks, Call Logs, and Call Operation APIs
• Reduces integration complexity and development effort
• Provides clearer error messages when the referenced call is not in a valid state

How to use:

1. Initiate a call using the Click-to-Call or Click-to-Call Support API
2. Capture the ref_id returned in the API response
3. When invoking a supported Call Operation API (Transfer, Conference/Barge), provide either call_id (existing) or ref_id (newly supported)
4. The platform automatically resolves the ref_id to the corresponding active call and performs the requested operation

Note: If the ref_id does not correspond to an active call or the call has already ended, the API returns a meaningful error indicating the operation cannot be performed.

6. 🔐 Webhook Security Enhancement: Mutual TLS (mTLS) Support

Audience: Developer

Acefone now supports Mutual TLS (mTLS) for outbound Webhook requests, enabling certificate-based authentication between Acefone and your webhook endpoint. You can upload and manage client SSL certificates through the Security section in API Connect and configure mTLS for your Webhooks.

Benefits:

• Adds an extra layer of security beyond standard HTTPS by enabling certificate-based authentication
• Ensures only trusted webhook requests are accepted by endpoints configured with mTLS
• Helps meet enterprise security and compliance requirements
• Provides centralized certificate management, including certificate updates and rotation
• Supports seamless integration with systems that require mutual TLS authentication

How to use:

1. Navigate to API Connect → Security
2. Open the mTLS configuration
3. Upload your client SSL certificate and private key
4. Assign the mTLS configuration to the required Webhooks
5. Click Save

Note: If mTLS is not enabled for a Webhook, Acefone continues to deliver requests over standard HTTPS. Ensure your webhook endpoint is configured to trust the uploaded client certificate before enabling mTLS.

7. ⏳ API Token Expiry Configuration with Maximum Validity of 90 Days

Audience: Developer

API token management has been updated to support configurable token expiry with a maximum validity of 90 days. When generating a new API token, you can now choose from the following validity options:

Benefits:

• Strengthens API security by reducing the lifetime of API credentials
• Provides flexibility to choose a token validity period that aligns with your organization's security policies
• Encourages regular token rotation, reducing the risk of compromised credentials
• Aligns API authentication with industry security best practices

How to use:

1. Navigate to the API Tokens page
2. Generate a new API token
3. Select the required token validity (defaults to 90 days if none selected)
4. Replace expiring tokens in your applications before their expiry date to ensure uninterrupted API access

8. 🗂️ Introducing the New Flows Workspace for Call Flow Management

Audience: Admin / Supervisor / Developer

A unified Flows workspace has been introduced that brings together key call flow management capabilities into a single location. The following modules are now available under Flows:

• API Dialplan
• CDP List Management
• IVR
• Auto Attendant

This update consolidates call flow configuration into a centralized workspace while preserving the existing functionality and user experience.

Benefits:

• Provides a single, centralized workspace for managing call flows
• Simplifies navigation by grouping all call flow-related capabilities in one place
• Improves the overall user experience with a more intuitive and organized interface
• Reduces the need to switch between different modules when configuring customer call journeys
• Ensures a seamless transition without impacting existing configurations or permissions

How to use:

1. Navigate to the Flows module from the Acefone navigation menu
2. Access the required component: API Dialplan, CDP List Management, IVR, or Auto Attendant
3. Continue creating and managing your call flows as before — existing configurations, permissions, and functionality remain unchanged

Note: This is a navigation and workspace improvement only. There are no changes to the behavior or functionality of the underlying modules. Existing links and bookmarks will continue to work through automatic redirection.

🛠️ Bug Fixes

🎙️ Voice Streaming & SIP Trunking

✨ New Features & Improvements

1. 📁 Configurable Folder Directory Structure for BYOS Call Recording Delivery

Audience: Admin / Supervisor

If you use your own storage (BYOS — AWS S3 or SFTP) for call recording delivery, you can now choose how your recordings are organised inside your own storage — by number, by date, or both — instead of one flat folder. The folder structure is created automatically as recordings are delivered, with no manual setup needed on your storage.

Benefits:

• Enterprise-Ready Storage: Organise recordings into a structure that fits your compliance and storage workflows, instead of one flat folder
• Faster Retrieval: Locate recordings by number or by date directly in your own storage, cutting down retrieval time during audits and investigations
• No Extra Effort or Cost: No need to script your own reorganisation after delivery — recordings arrive already structured, and remain playable from the Acefone platform

How to use:

1. Go to Settings → Manage Settings → Recording Folder Structure
2. Review the available folder structure options and the preview shown for each
3. Select the structure that best fits your storage and compliance requirements
4. Click Save Structure to apply it

CRM Integration Compatibility: Selecting a recording folder structure other than Default increases the length of the call recording URL. CRM integrations that store this URL in a fixed-length field (e.g. Salesforce caps the relevant field at 255 characters) may reject URLs beyond their limit, causing call logs and recording links to fail to sync. If you rely on a CRM integration for recording links, please check with Acefone Support before enabling a folder structure.

📋 Contacts & Campaigns

✨ New Features & Improvements

1. 📡 Webhooks for New Broadcast Architecture

Audience: Admin

Voice Broadcast campaigns (New Architecture Voice Blasting) now support webhooks, allowing your systems to receive real-time HTTP notifications for key campaign events such as call initiated, call answered, campaign completed, and delivery status updates.

Benefits:

• Eliminate the need to poll the portal or download reports manually — your CRM, data warehouse, or automation tools receive campaign event data the moment it occurs
• Build real-time workflows such as triggering follow-up actions, updating contact records, or alerting teams based on live call dispositions

How to use:
Go to Webhook, select the trigger, and configure the Webhook.

2. 🔗 Add Webhook Support in Auto Attendant DTMF Entries

Audience: Backend Optimisation

Auto Attendant DTMF entries now support webhook configuration. When a caller presses a keypad digit, the system can send an HTTP callback to a URL you define — passing call data to your external application or CRM in real time. Webhook entries can be created, updated, and deleted through both the dashboard UI and the REST API.

Benefits:

• Connect your Auto Attendant directly to external systems without manual exports or polling — caller interactions trigger your own workflows the moment a DTMF key is pressed
• Teams using the API can manage webhook entries programmatically, making it straightforward to maintain configurations across multiple numbers or environments

How to use:
Go to Webhook, select the trigger, and configure the Webhook.

3. 🔒 Restrict Lead Upload and Delete to One File at a Time Per Lead List

Audience: Admin

Lead list file uploads and bulk deletes are now restricted to one active operation at a time per list. While a file upload or bulk delete is in progress for a given lead list, the upload control or delete action for that same list is disabled until the operation completes, fails, or is canceled. Other lead lists are unaffected and remain fully operational in parallel.

Benefits:

• Prevents data conflicts and partial or duplicate records that can occur when multiple uploads or bulk deletes run simultaneously against the same lead list. If you return to the page after a refresh, the system accurately reflects the ongoing operation so you always have a clear picture of your list's current state before taking further action.

4. ⚡ Optimize WhatsApp Broadcast Workflow for Better Delivery, Engagement, and Campaign Efficiency

Audience: Backend Optimisation

The WhatsApp broadcast workflow has been updated with optimizations across campaign setup, message delivery, and engagement tracking.

Benefits:

• Campaigns reach recipients more reliably, reducing drop-offs caused by delivery inefficiencies
• Improved engagement tracking gives clearer visibility into how recipients are responding to broadcast messages
• Faster campaign setup means less time configuring and more time acting on results