October 2026
๐ Smartflo โ October 2026 Product Release Notes
๐ Table of Contents
- ๐ข Hosted PBX
- ๐ Insights
- ๐ Dialer
- ๐ฅ๏ธ Console
- ๐ Integrations
- ๐ API & Webhook
- ๐๏ธ Voice Streaming & SIP Trunking
- ๐ Contacts & Campaigns
- ๐ฌ Messaging
๐ข Hosted PBX
โจ New Features & Improvements
1. ๐ง Interactions Hub Configuration Page via Admin SSO
Audience: Internal Teams (Admin SSO)
What's new?
The Interactions Hub Configuration page is now visible when internal teams log in to a customer account through Admin SSO. Earlier, this page only appeared with a direct client login.
What are the benefits?
- Support and onboarding teams can view and manage Interactions Hub settings without needing the customer's login details.
- Customer configuration requests are resolved faster.
How to use?
Log in to the customer account through Admin SSO and open Interactions Hub โ Configuration.
2. ๐ข Automatic "91" Prefix Based on International Calling Setting
Audience: Agents
What's new?
Outbound calls now add the "91" prefix based on the agent's International Calling setting:
- OFF: "91" is added automatically before the dialed number.
- ON: The number is dialed exactly as entered.
What are the benefits?
- Fewer failed calls caused by a missing country code.
- Agents don't need to remember to add the prefix themselves.
How to use?
No action required. The prefix follows the agent's International Calling setting.
3. ๐ Sticky WhatsApp Calling
Audience: Agents
What's new?
WhatsApp calls are now routed to the same agent.
What are the benefits?
- Customers reach an agent who already knows their conversation.
How to use?
No action required.
4. ๐ฅ Video Call Insights Linked to Interactions, Labels and Recordings
Audience: Admin / Supervisor
What's new?
Video call data sent to Insights now includes:
- The interaction and conversation the call belongs to.
- The labels applied to the call.
- Recording details for recorded calls: file location, file size and play time.
What are the benefits?
- Video calls can be traced back to their customer conversation.
- Teams can report on video calls by label.
- Teams can find the recording for any video call quickly.
- Existing reports keep working, because this change only adds new data.
How to use?
No action required on V3. On V4, recording details are sent only when the related setting is enabled.
5. ๐ Mobile App Security Enhancements
Audience: Agents
What's new?
These fixes address findings from a third-party security assessment:
- Developer Options detection (Android): The app now detects when Developer Options are enabled on the device and handles it as part of its security checks.
- Third-party keyboard restriction (Android): The app detects and restricts third-party keyboards on sensitive input fields.
- Secure login fields: Copy, paste and keyboard caching are disabled for the Email/Username and Password fields.
- Background screenshot protection (iOS): A privacy overlay hides app content in the App Switcher when the app goes to the background.
What are the benefits?
- Lowers the risk of app tampering and data extraction.
- Protects login credentials and customer information on the device.
How to use?
No action required. Update to the latest app version.
6. ๐ก๏ธ Platform Security Hardening
Audience: Internal
What's new?
Security and code-quality issues flagged by SonarQube were fixed across the Call Controller, Datahub, Event Handler, Call Flow (frontend and backend) and Softphone.
What are the benefits?
- Improves platform security and stability.
How to use?
No action required.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Consecutive Intercom Transfers Ringing Forwarded Mobile CBI-4955 | Fixed the second and later Intercom transfers ringing the agent's forwarded mobile number instead of their extension |
| 2 | Calls Stuck Due to "Default Recording" in Queue Announcements CBI-5049 | Removed the "Default recording" option from queue announcements in Add/Edit Department (queue). It pointed to a missing file, which made calls appear stuck and showed the wrong status and duration in the CDR |
| 3 | Contact Name Header for Unsaved Contacts CBI-5015 | Fixed the contact name header display for contacts whose name is not saved |
๐ Insights
โจ New Features & Improvements
1. ๐ Archive Report Upgrade: 4 Files Instead of 16
What's new?
Archive Report downloads have been restructured to consolidate data into 4 files instead of 16. Same data, far fewer files to handle.
What are the benefits?
- Faster and easier report downloads
- Less time spent merging and organising files
- Cleaner experience for teams handling large archives
How to use?
Download any Archive Report as usual; you'll receive the consolidated 4-file set.
2. ๐ Restart Mechanism for Failed CDRs
What's new?
A restart mechanism now automatically picks up CDRs that fail during processing and reprocesses them. Failed records no longer get left behind.
What are the benefits?
- More complete and accurate call records
- Fewer data gaps in reports
- Less manual follow-up on missing CDRs
How to use?
Applies automatically to all CDR processing.
3. ๐ Platform Security Strengthened with VAPT & SonarScan
What's new?
The platform has gone through VAPT and SonarScan assessments, with all identified fixes deployed. This strengthens protection across the system.
What are the benefits?
- Your data stays safer than ever
- Reduced exposure to vulnerabilities
- Stronger compliance and security posture
How to use?
Applied platform-wide, no action needed.
4. ๐ Agent ID Filter on Xtract Dashboard
What's new?
The Xtract dashboard now supports filtering by Agent ID. View analytics for a specific agent in just a few clicks.
What are the benefits?
- Focused, agent-level performance insights
- Faster coaching and evaluation
- Less manual data filtering
How to use?
Go to the Xtract dashboard and select the Agent ID filter.
5. ๐๏ธ Updated Domestic & International Numbering Database
What's new?
The numbering database has been upgraded with the latest domestic and international data. Number lookups are now more accurate and up to date.
What are the benefits?
- More accurate number identification
- Better reporting quality
- Fewer mismatches in call data
How to use?
Applies automatically across the platform.
6. ๐ Smarter Circle & Operator Detection
What's new?
Circle and operator detection is now driven by the actual customer number. This significantly boosts mapping accuracy.
What are the benefits?
- Correct circle and operator data in reports
- Better regional and operator-level analysis
- More reliable call records
How to use?
Applies automatically to all calls.
7. ๐ฎ๐ณ Indian Numbers with 0091 Prefix Now Recognised
What's new?
Indian numbers with the 0091 prefix are now recognised, along with +91, 91 and 0. All common formats are handled correctly.
What are the benefits?
- No missed or misclassified Indian numbers
- Cleaner and more consistent call data
- Accurate reports regardless of number format
How to use?
Applies automatically, no action needed.
8. ๐ท๏ธ Updated Disposition & Sub-Disposition Logic
What's new?
The logic for disposition and sub-disposition has been updated. Call outcomes are now captured and mapped more accurately.
What are the benefits?
- More accurate call outcome tracking
- Better quality reports
- Clearer view of disposition trends
How to use?
Applies automatically wherever dispositions are used.
9. ๐ฅ Complete Agent Details for External Transfer Calls
What's new?
Calls transferred to external agents now show complete agent details in Download CDR and Custom Reports. This uses the alternate ID captured by the Dialer.
What are the benefits?
- No more blank agent fields
- Full visibility on transferred calls
- Accurate agent-level reporting
How to use?
Download CDR or open Custom Reports; agent details appear automatically.
10. โน๏ธ Complete Info in "i" Buttons on Call Performance Dashboard
What's new?
The "i" buttons on Call Performance Dashboard widgets now show complete details. Each widget clearly explains what it measures.
What are the benefits?
- Easier understanding of each metric
- Less confusion for new users
- Faster decision-making from the dashboard
How to use?
Hover over or click the "i" button on any widget.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Accurate Call Duration in Portal CBI-5070 | Fixed an issue where call duration was not shown correctly in the portal. It now matches the actual length of every call |
| 2 | Missing Agent Call Logs in New CDR Fixed CBI-5026 | Fixed an issue where some agents' call logs were missing from the New CDR. All call logs now show up correctly |
๐ Dialer
โจ New Features & Improvements
1. โฑ๏ธ Wrap Time and Hold Time in Disposition Webhook
Audience: Admin / Supervisor
What's new?
The inbound and outbound call event webhook now includes time the agent spent in wrap-up or on hold.
What are the benefits?
- CRMs and workforce analytics tools can calculate true agent handle time from the webhook alone, without cross-referencing reports.
How to use?
- Login to Admin Console
- Click on API Connect and webhook
- Add
"wrap_time":"$wrap_time","hold_time":"$hold_time"keys in Disposition status updated webhook
2. ๐ Agent Phone Number in Schedule Callback API
Audience: Admin / Supervisor
What's new?
The assigned_to field in the Schedule Callback API now accepts an agent's phone number as well as the agent ID.
What are the benefits?
Integrations that only know an agent's phone number can route callbacks directly to that agent.
How to use?
Pass the agent's phone number in assigned_to when you create a scheduled callback.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Progressive Dialing Stuck After Alternate Number Call | Fixed Progressive Dialing not moving to the next lead after an agent dialed a lead's alternate phone number (APN) from the disposition page |
| 2 | "No Next Lead Found" With Leads Remaining | Fixed agents seeing "No Next Lead Found" when dialable leads were still available because some leads stayed stuck in the picked state |
| 3 | Agent Panel Freeze After Consult Transfer | Fixed the Agent Panel becoming unresponsive when the consulted party hung up before the call moved to feedback recording |
| 4 | Agent Stuck "On Disposition" in Real-Time Report | Fixed agents remaining in "On Disposition" status in the Real-Time Report after disconnecting a session call |
| 5 | Preview Dialing "This lead could not be dialed" Error | Improved Preview Dialing timeout handling to address this error. This is a probable fix, since the issue was not reproduced internally |
| 6 | External Transfer Showing Wrong Number | Fixed external transfers always showing the lead number. The receiving party now sees the lead number when CLI is enabled and the DID when CLI is disabled |
| 7 | Interaction Hub Redirecting to Console Login | Fixed the Message icon on a live call opening the Smartflo Console login page instead of the Interaction Hub |
| 8 | Add/Edit DND Lead API Returning 500 | Fixed the API returning an Internal Server Error even when the DND lead was saved successfully |
| 9 | Dropped Flag Missing for Ratio Calls on Queue Timeout | Fixed the dropped flag not being set in the CDR for ratio calls that hit queue timeout |
| 10 | Wrap-up Duration Overwritten in CDR | Fixed cancelled call-patch events overwriting the wrap-up duration in the CDR |
| 11 | Agent Panel CDR Pagination Not Resetting | Fixed pagination in the Agent Panel CDR sidebar not resetting to page 1 when the date was changed |
๐ฅ๏ธ Console
โจ New Features & Improvements
1. ๐ Assigned By and Released By in DID History
Audience: Admin
What's new?
DID History now shows who assigned and who released each DID.
What are the benefits?
Admins can see who made each DID change without checking logs.
The new columns are also included in the CSV export for audits and reporting.
How to use?
Login to Admin Console and open DID History (menu path to be confirmed).
Check the new Assigned By and Released By columns, or click Export CSV to download them.
Note: These fields are filled only for DIDs assigned or released after this release. Older records will show them as blank.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Invalid Redirect Link Allowed at Login | Fixed Console login going through with an invalid or unsupported redirect link. Login is now blocked and an error message is shown |
| 2 | Insecure Link in Inventory Emails | Fixed the Inventory mail service using HTTP links. It now uses HTTPS |
| 3 | Unused Google Analytics Cookies | Removed Google Analytics cookies that were no longer in use from the Console |
๐ Integrations
โจ New Features & Improvements
1. ๐ Integrations Updated App
Audience: Admin / Supervisor / Agent
What's new?
Integration App, featuring a modernized UI/UX, improved settings, platform upgrades, and enhanced observability. The new experience will be enabled for the portal phasing out the existing app.
Key enhancements include:
- Visibility Modes for a more flexible app experience
- Notifications & Alerts for better real-time awareness
- Call Controls & Availability Controls for improved call management
- Guided App Tour to help users get started quickly
- WebRTC Enhancements for a smoother calling experience
- Multi-Tab Session Detection to prevent session conflicts
- Session Transfer for seamless session handling once closing other sessions
- Cache Clearing for easier troubleshooting
- App & Session Diagnostics for improved issue identification
- Notes Syncing to keep call-related information aligned with CRM records
- New UI with Entity Support for a more intuitive and connected CRM experience
- Bitrix Backend APIs and Recording cron update: No action needed from users
What are the benefits?
Enjoy a simpler, more secure, and reliable integration experience with improved visibility, a unified CRM Web App, enhanced session and diagnostic capabilities, and a strong foundation for upcoming features and enhancements.
How to use?
Packaged Integrations: Upgrade to the latest package to access the new experience and enhancements.
Non-Package-Based Integrations: No action is required.
First-Time Access: After upgrading, clear your browser cache and cookies, then log in to the New Integration App to start using the enhanced experience.
Note: To avoid any interruption to your integration services, we strongly recommend completing the upgrade to the latest Integration package within the communicated timeline. This upgrade is required to move to the latest integration interface and ensure continued access to supported features, enhancements, and security updates. Since, previous version of the packages will get deferred and will go to EOL post this release.
2. ๐ HubSpot Desktop App Deprecation & New Web App Experience
Audience: Admin / Supervisor / Agent
What's new?
The HubSpot Desktop App is being deprecated and replaced with an enhanced Web App that brings a more complete calling and CRM experience directly within HubSpot.
The new Web App now supports:
- Inbound & Outbound Calling for a unified calling experience
- Phone-Type Contact Custom Fields, including fields such as Alternate Number, Number 2, or other saved contact numbers
- Enhanced Call Logs with Task Creation, allowing call activity to be logged and follow-up tasks to be created directly in HubSpot
What are the benefits?
The new Web App provides a more seamless and unified calling experience within HubSpot, while reducing dependency on the desktop application.
With the enhanced capabilities, users can:
- Manage inbound and outbound calls from a single Web App
- Call contacts using additional phone numbers saved in supported HubSpot contact fields
- Maintain better CRM activity tracking with call logs and task creation
- Access the calling experience directly through the browser without requiring a separate desktop application
- Benefit from a more scalable platform for future calling and CRM enhancements
How to use?
The Web App will be updated automatically. However, the behavior with Desktop app will be phased out. For new users, it will be there as per authorization of app done and added.
3. ๐ Documentation Updates for CRMs
Audience: Admin / Supervisor / Agent
What's new?
We've updated the documentation for our CRM integrations with clearer, more structured guidance covering setup, configuration, feature usage, and troubleshooting.
The updated documentation helps users and administrators quickly find the information they need to configure and use the latest integration capabilities.
What are the benefits?
Faster Setup: Follow clearer step-by-step guidance for configuring CRM integrations.
- Easier Feature Adoption: Understand the latest features and capabilities with updated documentation.
- Simpler Troubleshooting: Find relevant troubleshooting steps and guidance more easily.
- Improved Self-Service: Get answers and resolve common configuration issues without additional assistance.
How to use?
Visit the updated CRM integration documentation in knowledge base for the relevant CRM to access the latest setup guides, feature details, configuration steps, and troubleshooting information.
4. ๐ Meritto Connector Update with Response Transformer
Audience: Admin / Supervisor / Agent
What's new?
We've updated the details for our CRM integrations with Meritto, more structured guidance covering setup, configuration, feature usage, and troubleshooting.
The updated documentation helps users and administrators quickly find the information they need to configure and use the latest integration capabilities.
What are the benefits?
- Seamless CRM & Telephony Integration: Connect Meritto CRM with our telephony platform for a more connected calling experience.
- Easy Discovery & Access: Find and access the connector directly through the Integrations Marketplace.
How to use?
Go to the integration marketplace to see the connector available โ Refer to the Doc and response transformer events in Knowledge base to perform execution of get owner Api handling.
5. ๐ก๏ธ Security Updates and Enhancements
Audience: Admin / Supervisor / Agent
What's new?
The updates include improvements across authentication and sessions, injection protection, tenancy and request security, browser/desktop security, application builds, and origin validation.
What are the benefits?
- Stronger Account Security: Enhanced authentication and session controls help protect user access.
- Improved Application Security: Additional safeguards strengthen protection against common application-level security risks.
- Better Data Isolation: Enhanced tenancy controls help ensure data remains appropriately isolated.
- Safer Browser & Desktop Experience: Security improvements help protect application usage across supported environments.
- More Secure Application Access: Improved origin and build controls strengthen how the application is accessed and delivered.
- Greater Reliability & Trust: Ongoing security hardening helps provide a safer and more dependable integration experience.
How to use?
No action is required from users. These security enhancements are included as part of the latest application updates and are applied automatically for dialer. We recommend keeping your Integration App and supported packages updated to the latest available versions to benefit from the latest security improvements.
6. โจ New Experience for Freshsales & Freshdesk App Based Integration
Audience: Admin / Supervisor / Agent
What's new?
We've enhanced the Dial experience across Freshsales and Freshdesk, making it easier to manage calls, contacts, tickets, and activities directly from your CRM.
Freshdesk enhancements include:
- Ticket Selection During Calls: Select the relevant ticket while handling a call.
- Improved Screen Pop: Quickly access the relevant contact or ticket when a call comes in.
- Contact or Ticket Selection from Call History: Choose whether to view the associated contact or ticket directly from history.
- Ticket Management: Improved support for managing and updating tickets.
- Clearer Error Messages: More meaningful CRM error messages make it easier to understand and resolve issues.
Freshsales enhancements include:
- Reliable Call Logging: Calls are logged directly through the CRM for improved activity tracking.
- Multiple Contact Selection: Choose the relevant contact when a call is associated with multiple contacts.
- Click to dial and Redirection added
- Create New Contact: Create a new contact directly when no existing contact matches.
- Clearer Error Messages: More meaningful CRM error messages make it easier to understand and resolve issues.
What are the benefits?
- Faster Call Handling: Manage calls without switching between your telephony platform and CRM.
- Better Context During Calls: Quickly identify the right contact, ticket, or activity while handling calls.
- Improved Activity Tracking: Keep call activity and CRM records better organized and connected.
- Greater Flexibility: Select the appropriate contact or ticket when multiple records are available.
- Easier CRM Management: Create contacts, manage tickets, and update call-related information directly within the CRM.
- Better Troubleshooting: Clearer error messages make it easier to identify and resolve issues.
How to use?
Open the Freshsales or Freshdesk integration and ensure you are using the latest available version.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | During multiple login attempt in Integration app - Blacklisted token error was observed | Implemented a retry mechanism with exponential backoff before triggering the Profile API to for token replication and prevent authentication failures |
๐ API & Webhook
โจ New Features & Improvements
1. ๐ Click-to-Call API Security & Standardization
Audience: Admin / Supervisor / Developer
What's new?
- Asynchronous processing is now standardized: Click-to-Call and Click-to-Call Support APIs process all requests asynchronously, irrespective of the
asyncparameter value. - Legacy
call_idhandling deprecated: Theget_call_idparameter is no longer processed, andcall_idis no longer returned in the API response. ref_idis now the standard identifier for tracking calls and performing subsequent call operations.- Existing integrations remain backward compatible with
async: 0, omittedasync, orget_call_idin the request.
What are the benefits?
- Consistent API behavior across all Click-to-Call integrations.
- Simplified API processing by removing legacy synchronous and
call_idhandling. - Improved reliability and scalability through standardized asynchronous processing.
- A single, consistent identifier (
ref_id) for call tracking and subsequent operations. - Existing integrations continue to work without payload changes.
How to use?
- Continue using the existing Click-to-Call / Click-to-Call Support APIs.
- The API will automatically process every request asynchronously; no change is required even if
async: 0is currently being sent. - Use the
ref_idreturned in the API response for subsequent call operations and tracking. asyncandget_call_idparameters can be omitted from new integrations, as they are no longer required.
2. ๐ PII/SPI Classification for CDP List Fields
Audience: Admin / Supervisor / Developer
What's new?
- PII and SPI classification is now mandatory for every field added to a CDP List.
- Users must classify each field as either PII or SPI; both cannot be selected together.
- The existing Sensitive option remains available and optional.
- Sensitive can be selected along with either PII or SPI and continues to support the existing data-masking behavior.
- The system will validate the classification before allowing the CDP List to be saved or submitted.
What are the benefits?
- Ensures consistent classification of personal and sensitive data across CDP Lists.
- Improves data governance and compliance by clearly identifying PII and SPI fields.
- Prevents fields from being created without an appropriate data classification.
- Provides a clear distinction between data classification (PII/SPI) and data masking (Sensitive).
- Establishes a foundation for future data protection and access-control policies.
How to use?
- While adding a field to a CDP List, select either PII or SPI.
- Optionally select Sensitive if the field requires the existing masking behavior.
- Save or submit the CDP List once all fields have been classified.
- If any field is unclassified, the system will prompt you to select either PII or SPI before submission.
Examples:
| Combination | Allowed |
|---|---|
| PII + Sensitive | โ Allowed |
| SPI + Sensitive | โ Allowed |
| PII only | โ Allowed |
| SPI only | โ Allowed |
| Sensitive only | โ Not Allowed |
| PII + SPI | โ Not Allowed |
3. ๐ Voice Streaming Support in Update My Number API
Audience: Admin / Supervisor / Developer
What's new?
The Update My Number API now supports Voice Streaming as a destination type, enabling customers to configure a number with a valid Voice Streaming ID using the format voice_streaming||<voice_streaming_id>. All existing destination types and their functionality remain unchanged.
What are the benefits?
- Enables API-based configuration of Voice Streaming for inbound numbers.
- Simplifies automation and integration of Voice Streaming configurations.
- Provides a consistent destination configuration experience through the API.
- No impact on existing destination types or integrations.
How to use?
- Use the Update My Number API to update the destination of a number.
- Select Voice Streaming as the destination type.
- Provide the valid Voice Streaming ID in the format:
voice_streaming||<voice_streaming_id> - The API will update the number with the configured Voice Streaming destination.
4. ๐ Update Webhook Trigger Timestamp in Webhook Logs
Audience: Admin / Supervisor / Developer
What's new?
Webhook Logs now display the actual timestamp at which the webhook was triggered. The Call Time label in Basic Details and Request Time under Webhook Attempts have been renamed to Webhook Triggered At, with the underlying backend timestamp also updated to reflect the actual webhook trigger time across all webhook types.
What are the benefits?
- Provides accurate visibility of when a webhook was actually triggered.
- Eliminates confusion between call time, request time, and webhook trigger time.
- Improves debugging, monitoring, and troubleshooting of webhook events.
- Ensures consistent timestamp information across all webhook logs and attempts.
How to use?
- Navigate to Webhook Logs โ View Log.
- In Basic Details, refer to Webhook Triggered At for the actual webhook trigger timestamp.
- Under Webhook Attempts, refer to Webhook Triggered At for the corresponding trigger timestamp.
- No configuration or action is required from the user.
5. ๐ Enhanced: View History Option Added for API Tokens
Audience: Admin / Supervisor / Developer
What's new?
The API Token Action menu (โฎ) now includes a View History option, allowing users to access the complete audit trail of changes made to an API token.
The History view provides details such as:
- Event type, including Created, Access Control Updated, Name Updated, Blacklisted, Whitelisted, and Renewed โ Superseded.
- Date and time of the event.
- Channel/Source through which the action was performed, such as Dashboard or API.
- Actor who performed the action.
- Change details or differences, wherever applicable.
The history is displayed chronologically, making it easier to understand the complete lifecycle and changes associated with an API token.
What are the benefits?
The View History option provides better visibility and traceability of API token activities. It helps customers and support teams:
- Track changes made to an API token after its creation.
- Identify what changed, when it changed, and who or what performed the action.
- Differentiate whether an action was performed through the Dashboard or API.
- Troubleshoot token-related issues more efficiently.
- Maintain a clear audit trail for token lifecycle and configuration changes.
How to use?
- Go to the API Tokens section in the Smartflo Dashboard.
- Locate the required API token.
- Click the Action (โฎ) menu for the token.
- Select View History.
- Review the chronological history of the token, including the event, timestamp, source/channel, actor, and applicable change details.
6. ๐ Authorization Header Now Mandatory for Click-to-Call Support API
Audience: Admin / Supervisor / Developer
What's new?
The Authorization header is now mandatory for all Click-to-Call Support API requests for security and authentication purposes. The api_key will continue to be required in the request body, as it is used to determine the destination of the call. The api_key alone can no longer be used for authentication.
What are the benefits?
This enhancement strengthens API security by introducing mandatory Authorization-based authentication while retaining the api_key for identifying the call destination. This provides better protection against unauthorized API access without changing how the call destination is specified.
How to use?
Include a valid Authorization Token in the Authorization header and continue passing the api_key in the request body.
- Authorization header: Used for authentication and security.
api_keyin payload: Used to determine the destination of the call.
Requests with a missing, invalid, or expired Authorization Token will return 401 Unauthorized.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Internal AWS IPs Visible in Smartflo Activity Logs | Fixed the activity log IP capture mechanism to ensure the client's actual source IP address is captured and displayed instead of internal AWS IPs |
| 2 | IP-Restricted API Token Returning 403 | Updated the IP validation mechanism to forward and validate the actual client IP instead of the Cloudflare IP |
| 3 | Intermittent 500 Internal Server Error in Auth/Login API | Added a null check before converting the data into an array and updated the revision log handling to gracefully handle null/invalid data |
| 4 | "Call Missed by Customer" Webhook for Softphone Calls | Updated the webhook trigger logic to support all applicable call initiation methods, including Dashboard/UI, Click-to-Call API, and Softphone |
๐๏ธ Voice Streaming & SIP Trunking
โจ New Features & Improvements
1. ๐ง Multiple Instructions inside Gather in VPaaS SDK
Audience: Developers
What's new?
The Gather element in the VPaaS SDK now supports multiple instructions (Dial, Speak and Play) inside it.
What are the benefits?
Developers can build richer call flows in a single Gather step, for example playing a message and then dialling, without chaining separate steps.
How to use?
Add Dial, Speak or Play instructions inside the Gather element in your VPaaS SDK code.
2. ๐ Webhooks for Input Errors and Failed Playback
Audience: Developers / Admin
What's new?
The VPaaS plugin now sends a webhook when an instruction fails because of invalid input. A webhook URL can also be set for playback-failed events.
What are the benefits?
Integrations learn right away what went wrong, making failures easier to debug.
Playback failures are caught as they happen instead of when users report them.
How to use?
Configure the playback-failed webhook URL in the VPaaS plugin settings (menu path to be confirmed).
Handle the validation error webhook response in your application.
3. ๐ Smarter Failover for Voice Streaming
Audience: Admin
What's new?
Calls are now sent to failover for any error while connecting to the client WebSocket. Earlier, failover worked only for a few predefined errors.
What are the benefits?
Fewer dropped calls when the streaming connection fails, so callers still reach a fallback.
How to use?
No action required. This applies automatically to calls with failover configured.
4. ๐ Better Troubleshooting for Recordings
Audience: Admin / Support
What's new?
The Processing Log, Recording Reports and Recording Folder Structure pages now show more details for troubleshooting.
What are the benefits?
Quicker to find why a recording failed to process, is missing from a report, or is not in the expected folder.
Less need to dig through server logs.
How to use?
Open Processing Log, Recording Reports or Recording Folder Structure (menu path to be confirmed) to see the added details.
5. ๐ Auto-Reconnect for Recording Transfers
Audience: Admin
What's new?
The recording transfer service now reconnects automatically if its connection drops, for example after a network blip or server restart.
What are the benefits?
Recordings keep moving without a manual restart, lowering the risk of missing or lost recordings.
How to use?
No action required.
๐ ๏ธ Bug Fixes
| # | Issue | Resolution |
|---|---|---|
| 1 | Voice Bot Name Save Error | Fixed Voice Bot names with special characters failing to save. Special characters are now blocked when the name is entered |
| 2 | Security Fixes | Fixed security issues flagged by SonarQube across Voice services |
๐ Contacts & Campaigns
โจ New Features & Improvements
1. ๐ฒ DTMF Capture for TTS Broadcast Calls New Architecture
Audience: Admin / Supervisor
What's new?
Recipients of TTS broadcast calls can now press any key from 0 to 9. The key press is captured and included in the webhook and the CDR.
What are the benefits?
Turns one-way TTS broadcasts into simple interactive campaigns, such as confirmations, opt-outs, and surveys.
Responses flow straight into the CDR and connected systems through the webhook.
How to use?
No changes Required.
2. โฑ๏ธ Retry Interval Limits for Broadcasts
Audience: Admin / Supervisor
What's new?
Broadcast retry intervals in the new broadcast engine must now be between 1 minute and 10,000 minutes.
What are the benefits?
Prevents misconfigured retries that are too aggressive or effectively never fire.
How to use?
Set the retry interval within 1โ10,000 minutes when you create or edit a broadcast.
3. ๐๏ธ Faster, Safer Lead List Deletion
Audience: Admin / Supervisor
What's new?
When a lead list is deleted, its leads are now removed in batches instead of all at once.
What are the benefits?
Deleting large lead lists no longer causes slowdowns for other running campaigns.
How to use?
No action required.
๐ฌ Messaging
โจ New Features & Improvements
1. ๐ Structured Templates in Template Manager
Audience: Admin / Supervisor
What's new?
Template Manager now supports structured templates with separate Header, Body and Footer sections, in line with WhatsApp's template requirements.
What are the benefits?
- Templates are easier to create.
2. ๐ก๏ธ Security and Code-Quality Fixes
Audience: Internal
What's new?
Vulnerabilities, code smells and security hotspots flagged by SonarQube have been fixed and tested.
What are the benefits?
- Improves platform security and stability.
How to use?
No action required.