Sprint Duration: January 5 – January 23, 2026
Release Date to Production: Sunday, March 8th, 2026
Quick Peek – What We Delivered
Sprint 2.2.1 focused on expanding webhook automation, improving dashboard clarity, and laying the technical foundation for future customization across white-labeled platforms.
During this sprint, we:
Enhanced the Enterprise Onboarding and Vetting Status Widget for better clarity and usability
Delivered multiple new webhook notifications for compliance, flagged steps, and deal registration
Finalized internal alignment on a major API ID standardization update (coming soon)
Completed technical spikes for customizable notifications and display identity configuration
Detailed Changes
1. UAT Bug Fixes and Pre-Release Cleanups
As with prior sprints, our team is actively resolving issues found during UAT testing. These are critical pre-production fixes designed to ensure your upcoming features behave as expected once live.
2. Dashboard Enhancement: Enterprise Onboarding & Vetting Status Widget
We improved the onboarding and vetting status widget available to both OSP and enterprise users on the dashboard.
Enhancements include:
Removed the Submitted status, as it duplicated Pending Review
Updated the widget color scheme for clearer visual distinction
-
Added a tooltip icon that opens a pop-up explaining each status definition, including:
Pending Review
In Progress
Complete
Rejected
Resubmitted
This ensures users clearly understand the lifecycle stage of their BCID applications without confusion.
3. New Webhooks: Expanded Automation and Alerts
We’re introducing new webhook events this sprint. These additions bring even more visibility to your branded calling operations and reduce the need to poll APIs manually.
A. Webhook – 180-Day Attestation and Annual Re-Verification Notifications
This webhook sends alerts when your BCID applications are due for compliance updates.
-
180-Day Attestation Reminder
Message: Action Required – 180-Day Attestation is Due
Includes: Company name, EID, last modified date
Prompt to confirm existing data or submit updates
-
Annual Re-Verification Reminder
Message: Action Required – Annual Re-Verification Needed
Includes: Company name, EID, last modified date
Prompt to complete a full re-verification of all data
Why it matters:
Get notified in advance when compliance deadlines are approaching so you can act before they become urgent.
B. Webhook – Flagged Steps on BCID Applications
This webhook notifies you when one or more steps in a BCID application are flagged during the vetting review process.
Message: Application Requires Your Attention – Flagged Steps Detected
-
Includes:
Company name
EID
Step numbers flagged
Flag comments explaining required changes or missing data
Why it matters:
This runs in parallel with the general vetting update webhook and gives you specific detail about what needs fixing without delay.
C. Webhook – Deal Registration Notification
This webhook is triggered when a new deal is registered in the portal.
-
Includes all deal details submitted, such as:
Parent ID
Deal ID and Deal Name
Vetting Fee, Retail Fee, Platform Fee
Call Volume
Enterprise contact name, email, and phone
Enterprise address (city, state, zip)
Enterprise last login date
Why it matters:
Instead of relying on the API to retrieve deal data, you’ll get an automatic notification each time a new deal is submitted.
Note:
Only the webhook types you’ve opted into will be sent. NumHub has built an internal dashboard to manage which webhook events are enabled per OSP. Let us know if you’d like to activate or deactivate specific webhook types.
Webhook Testing Acknowledgment
We would like to recognize one of our OSP partners who has been instrumental in testing these webhook implementations. Their collaboration helped validate payload accuracy, identify integration gaps, and ensure alignment between webhook events and API responses.
This partnership allowed us to strengthen both webhook reliability and API clarity before broader rollout.
API ID Standardization Update – Now Live (Hotfix Applied March 4, 2026)
As part of our effort to remove ambiguity between OSP-level and enterprise-level identifiers, we implemented an important API update that standardizes how IDs are returned in payloads.
This update was pushed to production on March 4, 2026.
What changed
API payloads now include both identifiers so integrations can clearly distinguish between the OSP and the enterprise.
Parent ID – Represents the OSP (your organization)
Deal ID – Represents the enterprise associated with the deal
You may still see Client ID temporarily in API responses during the transition period. However:
Client ID will be deprecated on March 31, 2026
What you should do
We recommend reviewing your API payloads and confirming your integrations recognize the following structure:
Parent ID = OSP identifier
Deal ID = Enterprise identifier
If your integrations currently rely on Client ID, please begin transitioning to Parent ID and Deal ID before March 31 to avoid any disruption once the field is fully removed.
This update ensures a clear parent–child relationship between OSPs and their enterprise clients, making integrations more consistent and easier to manage.
4. Spike: Customizable Notifications for OSP White-Labeled Portals
We’re exploring options that will allow OSPs to personalize the notifications sent from the platform to their enterprise clients.
Goals of this investigation:
Let OSPs add branding (logo, colors) to email notifications
Customize subject lines, email body text, and signatures
Ensure branding aligns with your white-label experience
This is still in research phase, but we’re committed to giving you more control over how your communications appear to clients.
5. Spike: Custom Display Identity Configuration Per Enterprise
We’re also researching ways to allow OSPs to control which brand attributes are available to each enterprise during step 7 of the BCID application process.
Example configurations:
Allow/disallow logo uploads
Require/disable call reason entry
Enforce only caller display name in certain deals
Why it matters:
Some OSPs offer different BCID packages depending on the enterprise. This enhancement would ensure each client only sees the branding options included in their specific agreement.
Why It Matters to You
Improved Visibility: The enhanced dashboard widget makes application status easier to understand at a glance.
Real-Time Automation: New webhook notifications reduce manual API polling and provide instant alerts for compliance, flagged steps, and deal registration events.
Cleaner API Structure: The upcoming Parent ID and Deal ID standardization will eliminate ambiguity and simplify integration logic.
Stronger White-Label Control: Future customization options for notifications and display identity configuration are now technically validated and ready for roadmap consideration.
Questions or Feedback?
As always, we’d love to hear from you.
For questions, feature suggestions, or webhook activation requests, contact Daniela Villamar at dvillamar@numhub.com.
Thanks for partnering with us as we continue to build a more intelligent, transparent, and customizable branded calling ecosystem.
Comments
0 comments
Please sign in to leave a comment.