Planned official release schedule and content:
Timing:
Region | Start Date & Time | End Date & Time |
APAC | Sep 14th, 2025 at 12 pm EDT | Sep 14th, 2025 at 6 pm EDT |
EMEA | Sep 14th, 2025 at 8 pm EDT | Sep 14th, 2025 at 2 am EDT |
NAMR | Sep 14th, 2025 at 12 am EDT | Sep 14th, 2025 at 6 am EDT |
What's New?
Fraud Prevention
Movius announces a new feature to help prevent international long-distance fraud. Using a dedicated MMP web page, a carrier can temporarily restrict an Enterprise’s numbers from placing international calls.
Local Routing and Charging Prefixes for Toll-Free Calls
Movius announces a new call routing capability. Movius can now prefix outgoing toll-free calls with a prefix if required for charging or local routing purposes. The prefix can be assigned based on the NPA of the MultiLine number.
Law Enforcement Line Seizure
Movius announces a new feature to support law enforcement efforts. Using a new API a carrier can temporarily provision an existing MultiLine number to only call a specified police number, regardless of what number is dialed in the MultiLine App. This is important for hostage negotiations, domestic violence situations, etc.
User Interface Update for Message Activity Report
The user interface for the message activity report has been updated to clearly display which content is available for download from the report.
Server-Side Support for WhatsApp Bulk Messaging
Server-side support for Bulk Messaging on the WhatsApp channel. This enhancement is designed to streamline communication by enabling the dispatch of multiple messages through a single action.
- Key Capabilities:
- Enables sending multiple messages in one go via WhatsApp, improving operational efficiency.
- The server now supports compound messages, allowing clients to send text and images together for bulk messaging.
- MMP administrators can enable or disable this feature at both the organisation and user level.
- Messages sent via the bulk messaging feature will be supported by CDR and Digital Safe for compliance and archival purposes.
- Provisioning APIs are updated to manage enable and disable Bulk Messaging.
- CDR and Digital Safe APIs are updated to retrieve bulk messages sent via WhatsApp.
Note: This release includes only server-side support. The client-side interface for bulk messaging is not yet available. We will communicate separately once the client-side functionality is ready for use.
WhatsApp Capture - Transparent Mode
The platform has been enhanced with new capabilities to facilitate native WhatsApp messaging support.
Account Deletion Support:
MMP administrators can now delete Native Social account types directly from the MMP portal. If WhatsApp Capture is enabled for the account, the feature will be automatically disabled upon account deletion.
Enhanced Account Creation Fields:
New fields—First Name, Last Name, and Account ID—have been added to the account creation page to ensure complete and accurate data collection during onboarding.
WhatsApp Device Monitoring and Alerts:
- An email notification will be sent to the organisation administrator when a WhatsApp device is unlinked from the Movius platform for any user in their organisation.
- An email alert will also be triggered if a user has not accessed their WhatsApp device for 12 consecutive days, helping administrators stay informed about inactive usage.
Email Delivery of Authentication Code
- The OTP code necessary for WhatsApp user authentication will be sent to users via email along with SMS.
API Enhancements for NMC Provisioning - MDE-5546
This release introduces enhancements to the Create PTN and Patch PTN APIs to support automatic configuration of inheritable properties based on the SOC (Service Offering Code) provisioned by T-Mobile. These changes ensure accurate and consistent enablement of flags at the organization level when new NMC numbers are provisioned.
Key API Changes- Create PTN API
- When a new NMC number is provisioned by T-Mobile:
- The API will evaluate the SOC included in the provisioning request.
- Based on the SOC, the system will enable the corresponding inheritable flag at the organization level.
- Patch PTN API
- When updating an existing PTN with a new SOC:
- The API will check the SOC in the patch request.
- It will then enable or disable the respective inheritable flag based on the SOC provided.
- When updating an existing PTN with a new SOC:
- Org-Level Flag Behavior
- T-Mobile provisions numbers using the top-level org_id.
- The Enable flag for NMC is now inheritable and org-scoped:
- If any number within the organization is provisioned with a qualifying SOC, the org-level flag must be enabled.
- This ensures consistent behavior across all accounts under the same organization.
Notes for Integrators
- SOC-based flag logic is centralized at the org level, not per individual PTN.
- Ensure SOC mappings are up-to-date to reflect accurate flag behavior.
- These changes are backward-compatible and do not affect existing provisioning flows outside of SOC-based enablement.
MMP Portal UI Update: Suspended Account Indicator -MDE-2907
Feature Overview: To improve administrative visibility and streamline account management, the MMP Portal now displays a visual identifier for Suspended accounts directly on the List Accounts page.
Suspended Account Icon Display- When an MMP Admin logs into the portal and navigates to the Accounts section:
- The List Accounts page will now show an icon next to accounts that are in a Suspended state.
- This enhancement allows Portal Admins to:
- Quickly identify suspended users
- Take appropriate action without needing to drill into individual account details
User Story Reference
- As an MMP Admin, I want to see an identifier on the List Accounts page so that I can easily recognize suspended users.
- Given the admin logs into the MMP Portal
- When they click on “Accounts” and the List Accounts page loads
- Then the system displays an icon for any account marked as Suspended, based on the UX specifications.
Notes: This is a UI-only enhancement; no changes were made to backend account status logic.
Bug Fixes:
CS-234308 | Fixed an issue with the users/list API for Digital Safe. The JSON response now correctly shows SIPREC recorded users. |
CS-234701 | Fix to update PTN Delete error |
CS-234721 | Fix to resolve getOTP via PIN issue |
Version History
Date | Description |
---|---|
09/03/2025 | Created |