Release Notes 2.7.2 - UAT

Sprint Duration: June 22 – July 10, 2026
Planned Release Date to UAT: Monday, July 20, 2026

---

Quick Peek – What We Delivered

Sprint 2.7.2 focused on expanding the white-label experience, improving Display Identity management, and making notifications and reporting more intuitive for OSPs.

During this sprint, we:

• Introduced customizable notification branding for OSPs
• Added new Display Identity dashboards and activity history
• Improved settlement report notifications
• Fixed Display Identity telephone number count synchronization

---

Detailed Changes

⭐ High Impact Updates

These updates deliver the biggest day-to-day improvements for OSPs managing branded calling.

1. Customizable Notification Center (Phase 1)

Summary: We completed the first phase of a new Notification Center that will give OSPs greater visibility and control over platform email notifications. The remaining functionality will be completed in Sprint 2.8.1.

During this sprint, we completed the initial UI experience and supporting backend work, establishing the foundation for notification management.

The new Notifications page has been added under Settings, where OSP administrators will be able to:

• View all platform notifications in one location
• See which notifications are sent to OSP users and which are sent to enterprise users
• Configure branding for notification emails
• Preview how branded emails will appear before saving changes

When complete, OSPs will be able to customize notification branding, including:

• Company logo
• Accent color
• Email footer
• Support email
• Support phone number

To ensure important compliance communications remain accurate, notification content and subject lines will continue to be managed by the platform while branding elements remain customizable.

Phase 1 Delivered

• New Notifications page under Settings
• Initial UI for notification management
• Backend foundation to support notification branding and configuration

Coming in Sprint 2.8.1

• Completion of notification branding functionality
• Notification recipient management
• Email preview experience
• Save default branding across notifications

Why this matters:

By delivering this feature in phases, we're able to release the underlying framework first while finalizing the remaining functionality. Once complete in Sprint 2.8.1, OSPs will have a fully branded notification experience that further enhances the white-label portal.

2. Settlement Report Email Notifications

Summary: OSPs using SFTP can now receive an email whenever a new settlement report is generated.

Previously, settlement reports were only available by:

• Accessing the SFTP container
• Downloading the report from the portal
• Using the APIs

With this enhancement, whenever a new report is generated according to your configured delivery schedule (daily, weekly, or monthly), an email notification will also be sent with a direct download option.

The report will continue to be delivered to your SFTP container as before.

Why this matters:

This provides faster access to settlement reports while maintaining existing SFTP delivery for automated workflows.

🔹 Additional Improvements

These enhancements improve usability and provide better visibility across the BCID platform.

3. Display Identity Dashboard Summary Panels

Summary: We enhanced the Display Identity page with new dashboard panels that provide an at-a-glance overview of your Display Identity activity.

The new dashboard includes:

• Active Display Identities — Total number of active Display Identities
• Open Change Requests — Total pending Display Identity change requests
• Participating Enterprises — Number of enterprises with at least one active Display Identity

These summary panels are available to both OSPs and enterprise users, displaying information based on each user's access level.

Why this matters:

Important Display Identity information is now immediately visible without having to review the full table.

4. Display Identity Activity Timeline

Summary: Every Display Identity now includes a complete activity history.

A new Activity Timeline option has been added under the Display Identity Actions menu.

The timeline records important lifecycle events, including:

• Display Identity creation
• Change request submissions
• Telephone number additions or removals
• Logo updates
• Caller Display Name updates
• Call Reason updates
• Approval and rejection history
• Deactivation requests and outcomes

OSP users can view activity for all Display Identities under their account, while enterprise users will only see the history for their own Display Identities.

Why this matters:

The new timeline provides a complete audit trail, making it much easier to understand when changes occurred and track the history of every Display Identity.

5. Display Identity Telephone Number Count Fix

Summary: We corrected the Display Identity table to accurately reflect telephone number totals after approved change requests.

Previously, when telephone numbers were added using the spreadsheet upload option, the numbers were successfully activated within the BCID ecosystem, but the Display Identity table continued showing the previous telephone number count.

With this fix, the table now automatically updates to display the correct number of active telephone numbers after the change request is approved.

Why this matters:

This ensures the portal accurately reflects the current state of your active Display Identities while confirming that telephone numbers continue to be provisioned correctly in the BCID ecosystem.

---

Why It Matters to You

This sprint helps OSPs:

• Deliver a more branded white-label experience through customizable notifications.
• Access settlement reports more quickly through automated email notifications.
• Monitor Display Identity activity with new dashboard summaries.
• View a complete history of every Display Identity through the new activity timeline.
• See accurate telephone number counts after approved Display Identity updates.

---

Questions or Feedback

For questions about these updates or anything else related to the platform, please contact:

Daniela Villamar
[e-mail]