We’re committed to keeping you fully up to speed with all of the features, enhancements and fixes we ship at Root. Here are all of the updates and improvements we shipped over the last month 🛠️

Features

We’ve introduced new features to improve flexibility and customisation:

• Filter claims by product module: You can now filter claims based on their product module, helping you quickly focus on relevant claims and streamline your workflow.
• New lifecycle hook: You can now leverage the beforeClaimSentToReview lifecycle hook to run custom logic or validations before a claim moves to review. This allows you to conditionally block claims from progressing if needed. Read the docs.
• Progress on notes tagging: We’re developing a new feature to enhance collaboration within notes on Dashboard.
• Additional relationship fields for beneficiaries: You can now capture more detailed information for beneficiaries and covered people through new, configurable fields on Dashboard and Embed.
• Support for new claim fulfilment event: We’ve added a new ClaimFulfilled event type with conditional webhook support. This allows for more granular tracking and integration as part of the broader claims lifecycle. Read the docs.
• We’ve introduced several enhancements to improve how you sell and manage policies on Root Embed:
  • Enhanced session management: You can now archive Embed sessions and specify expiration dates at session creation, providing improved control and security. Read the docs.
  • Persist beneficiaries in prefill data: Beneficiaries are now retained across Embed sessions, streamlining repeat interactions and improving user experience.
  • Configurable payment declaration: You can now customise the text shown in the payment declaration step. Read the docs.

Platform Enhancements

• Performance Enhancements

  We’ve introduced enhancements to improve stability, efficiency, and visibility across Root:

  • Minor UI enhancements to claims views: We’ve made several visual refinements to the claims interface to improve clarity and usability.
  • Access to execution logs for shared product modules: Organisations can now view execution logs for their own activity on product modules they do not own. This improves visibility when working with shared or third-party modules

• Billing Enhancements

  We’ve made several improvements to increase reliability, accuracy, and automation across Root’s billing processes.

  • Support for refunds through collection modules: You can now create refunds that are handled by collection modules. These refunds don’t require bank details up front and will appear as pending until processed via the collection module hook.
  • Configurable handling of payment failures: We’ve added support for configuring specific failure codes that should not automatically block a payment method. This gives you more control over how failed payments are handled across billing workflows. Read the docs.
  • Refined active status logic for payment generation: Policies with a pending status are no longer treated as active when generating premium payments, ensuring more accurate billing behaviour.
  • Improved validation for policy update requests: We’ve strengthened validation to ensure that all policy update requests are processed with the correct context, reducing silent failures and improving reliability in collections workflows.
  • Validation for billing config compatibility: We’ve introduced validation to ensure that only payment methods with matching billing configurations can be assigned. This helps prevent misconfigured payment flows and improves system reliability.
  • Improved billing config endpoint handling: The billing config endpoint now correctly returns a 404 for collection modules, which don’t have associated configuration.
  • Improved visibility for Nedbank DebiCheck errors: We now surface unknown system errors more clearly in our monitoring tools to support faster investigation and resolution.
  • Foundation for multi-provider DebiCheck support: We’ve made several behind-the-scenes updates to support future DebiCheck functionality, including configuration improvements, permission updates, and provider-specific logic. These changes lay the groundwork for more flexible mandate processing in future billing flows.
  • Foundation for the new policy ledger: We’ve made a series of structural and interface improvements in preparation for the new billing ledger. These updates include performance optimisations, simplified data structures, and enhancements to support more accurate financial tracking and future reporting capabilities.

• Bug fixes

  We’ve addressed key issues to improve system reliability:

  • Fixed broken members link: Resolved an issue where the members link on the policy details view was not working correctly.
  • Corrected bank branch code behaviour in Embed: We fixed an issue where selecting a bank in the Embed flow populated the incorrect branch code. This now aligns with behaviour in the dashboard.
  • Fixed payment method prefill in Embed: Resolved an issue where the payment method was being cleared from prefill values when returning to Embed a second time.
  • Corrected version history timestamps: Fixed an issue where version history dates were displaying incorrectly due to a bug. Dates now accurately reflect when product module versions were created and reviewed.
  • Resolved issue with duplicate external payments: Fixed an edge case where some policies were processed multiple times due to non-deterministic query ordering. Queries now use consistent ordering to prevent duplication during batch processing.

If you have any suggestions or feedback, please share them with your Client Success Manager or submit them via the Root product roadmap to make sure we always know what’s top of mind for you.