Sprint Duration: March 9 – March 27, 2026
Planned Release Date to Production: Monday, June 1st, 2026
Quick Peek – What We Delivered
Sprint 2.4.1 focused on improving platform stability, expanding webhook visibility, and enhancing usability across the BCID workflow and reporting experience.
During this sprint, we delivered:
- Improvements to reference verification reminders
- Prevention of duplicate Display Identity records
- Enhancements to enterprise user management
- Fixes to Contact Us attachment handling
- New webhook events
- Improvements to the Settlement Report
- Updates to BCID application status logic
- Introduction of a new Step 0 in the BCID application flow
- Security improvements for credential management
Detailed Changes
1. Reference Verification Reminder Fix
We fixed a scenario where reminder notifications could continue even after a BCID application had already been completed.
This occurred when an internal business reference was verified manually rather than through the email verification link. In those cases, the application could already be complete, but reminder emails were still being sent.
The platform now stops sending these reminders once the application is marked as Complete.
Why this matters:
OSP users will only receive notifications when action is actually required.
2. Duplicate Display Identity Prevention
We resolved a rare issue where the system could create duplicate Display Identity records after a BCID application was approved.
In these cases, one Display Identity contained the correct data while another duplicate record appeared empty.
We implemented safeguards so the platform now only creates the number of Display Identities actually submitted in the application.
Why this matters:
This improves data accuracy and prevents confusion in the BCID ecosystem.
3. Enterprise User Assignment Improvement
We improved how OSPs manage users in the portal.
You can now:
- Assign user roles (OSP Admin or Enterprise User)
- Link enterprise users to a specific client account
- Control access based on role and client association
Why this matters:
OSP admins now have full control over user access and can properly assign users to the correct enterprise accounts.
4. Contact Us Attachment Handling Fix
We fixed an issue where certain file types submitted through the Contact Us form could not be opened by our support team.
This included:
- Images (JPG, PNG)
- Word documents
- Spreadsheets
- Other common file types
This fix has already been pushed to production.
Why this matters:
Support can now review your attachments immediately without requesting resubmissions.
Hotfixes Released During This Sprint
7. Logo Upload Validation (32-Bit Requirement)
We updated logo validation requirements to ensure compatibility with carrier networks.
New requirements:
- Format: BMP
- Size: 256 × 256 pixels
- Bit Depth: 32
If a logo does not meet these requirements, the platform will reject it and display a clear error message.
We also updated instructions in Step 7 of the BCID application.
Why this matters:
Ensures logos display correctly during branded calls and avoids carrier-related issues.
8. Appeal of Vet Webhook
This webhook triggers when a rejected BCID application is resubmitted.
Why this matters:
Allows OSPs to track when an application re-enters the vetting process.
9. Display Identity Creation Webhooks
New events notify when:
- A Display Identity is submitted
- Vetting is completed (approved or rejected)
- The Display Identity becomes active
Why this matters:
Provides real-time visibility into Display Identity lifecycle events.
10. Display Identity Deactivation Webhook
New webhook events notify when:
- A deactivation request is submitted
- The request is approved or rejected
Why this matters:
Gives full visibility into when Display Identities are removed from the ecosystem.
UI / UX Enhancements
11. Settlement Report Date Sorting
Users can now sort the Settlement Report by:
- Oldest to newest
- Newest to oldest
12. Excel-Style Date Filter for Settlement Report
Added a column-level filter to allow selecting specific dates within a time range.
Why this matters:
Provides more flexibility when analyzing confirmed call data.
BCID Workflow Enhancements
13. BCID Application Status Logic Update
We updated how statuses behave when flagged steps are corrected.
Now:
- Fixing flagged steps returns the application to Pending Review
- Then it moves back to In Progress
- Resubmitted is only used for rejected applications that are appealed
Why this matters:
Ensures statuses accurately reflect the real workflow.
14. New Step 0 – Application Type Selection
We introduced a new Step 0 at the start of the BCID application flow for OSP users.
This step allows you to specify whether the application is:
- For your own company, or
- On behalf of a client enterprise
If submitting for an enterprise:
- You must select the company from your registered deals
- If it doesn’t exist, you can create a deal directly from this step
- You can choose whether to send an invitation email to the enterprise
Important:
- This step is only visible to OSP users
- It does not appear for enterprise users
Why this matters:
This ensures applications are correctly tied to the right enterprise and prevents reporting and API mismatches.
Why It Matters to You
- More accurate and relevant notifications
- Improved Display Identity consistency
- Better user access control
- Real-time webhook visibility
- More flexible reporting tools
- Clearer application status tracking
- Easier submission of applications on behalf of enterprises
Questions or Feedback
For questions about these updates or anything else related to the platform, please contact:
Daniela Villamar
dvillamar@numhub.com
Comments
0 comments
Please sign in to leave a comment.