You can now download a messaging billing detail records report, which includes message charges and surcharges, in Messaging Insights. 

We have added new location, subaccount, and campaign ID filters, and enhanced the report so that large data sets will automatically break down into multiple files (or you can select to download separate files for subaccount or location). For more information, check out our support article.

Bandwidth is pleased to announce a new Messaging Health Monitoring page in Messaging Insights. This page allows for enhanced visibility to health metrics for traffic in US messaging channels. 

You can see the status of three key metrics: 10DLC registration, carrier rejections, and internal rejections at a glance, or view a breakdown of these metrics to determine where to make changes to improve the overall health of your messaging traffic, including the ability to view the exact numbers associated with any unregistered or blocked traffic.For more information on messaging health metrics, check out our support article.

Effective March 14, 2024, Bandwidth supports the automatic disablement of messages on telephone numbers (TNs) that have been moved to another provider.

Effective November 9, 2023, the Messaging Insights menu features a new region drop-down that allows you to see your data filtered by either “US” or “EU” as the data origin. This change allows us to continue providing direct access to your data while also maintaining compliance with regional and international data privacy and security laws and regulations. 

By default, the drop-down displays US, which populates Messaging Insights with message data originating in the US and Canada. When you select EU, you will see all other data including data from other supported countries and alphanumeric messages.

For more information on Messaging Insights, check out our support article.

On July 25, 2023, Bandwidth released a new Short Code Management feature in the Bandwidth Dashboard. 

Customers who choose to have Bandwidth manage their short code lease will be able to self-manage:

• The opportunity to select from various lease lengths (3, 6, or 12 months)
• Automatic lease renewal
• Subscribing to automatic notifications via email

Effective May 31, 2023, Campaign ID is available in Message Logs. You can view the campaign associated with a given message and filter by Campaign ID, as well as change the timezone that data is displayed in and configure the fields available in the Message Logs table. 

For more information on Messaging Logs, check out our support article. 

Our Messaging Monitoring pages have been updated to include new configurations, filters, and functionality. Some of these key changes include:

• New Campaign ID, Location ID, and To and From Phone number filters (Usage and Delivery pages)
• Search from Today to 13 months ago (Usage and Delivery pages)
• Explore Delivery % by Carrier, Message Type, and Message Product 
• Monitor peak capacity for MMS and SMS traffic on the updated Capacity (formerly MPS) page

Bandwidth now offers a Business Associate Addendum (BAA) for messaging and voice channels to extend HIPAA obligations to Bandwidth as a service provider, enforcing the HIPAA Security Rule to safeguard Protected Health Information (PHI) that may be exchanged by Covered Entities over our platform.

Please visit our HIPAA-eligible products and services page for an up-to-date list of currently eligible products and services, as we continuously expand the list of products covered by our BAA.

Effective March 7, 2023, Bandwidth will begin selecting “Secondary DCA Sharing Status” for all carriers including AT&T, Verizon, T-Mobile, US Cellular, Interop, and Clearsky in The Campaign Registry (TCR). 

This will allow customers registering through TCR to receive the CAMPAIGN_DCA_COMPLETE webhook which indicates that the campaign has gone through vetting and been accepted by all submitted DCAs.

On January 6, 2023, we will perform a messaging release that may cause changes to the letter case of HTTP headers within HTTP responses and callbacks. For instance, the “Content-Type” header may be changed to “content-type.”

Please validate that your applications are parsing these headers in a case-insensitive fashion in accordance with RFC 9110.