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’re working on new features to expand what you can do on Root:

• Activity log change tracking: New functionality tracks and displays field-level changes on policy and claim update events, making it easier to see exactly what changed and when. Planned for rollout in April.
• We've made several updates to User Groups functionality:
  • User groups expanded to all domains: User groups now cover applications, policies, claims, complaints, and product modules, including all write actions.
  • User group filter on applications list view: A filter for user groups has been added to the applications list view, making it easier to find and manage applications by user group.
  • User groups on API keys: API keys can now be tied to a specific user group, restricting access to data within that group's scope where user group restrictions are enabled.
• Dynamic select schema component: A new dynamic-select schema component allows select field options to be retrieved directly from product module code, giving you more flexibility when building product module forms.
• Nested list components in Root schema: Support was added for nested lists in Root schema components.
• AI claims assistant now supports Word documents: The AI claims assistant can now process Word documents in addition to previously supported file types. Follow the setup guide to enable this feature.
• Move start date on Embed | Management: Policyholders with pending or pending-initial-payment policies can now preview and apply start date changes directly from the Embed.
• Custom module data display for applications: Product modules will soon be able to customise how application data is displayed on Dashboard. When enabled, application views will show tailored, human-readable data instead of raw module fields.
• Publish collection modules via the CLI: The rp publish command now supports publishing collection module drafts directly from Workbench. Available in workbench v1.4.26.
• Markdown support in Embed confirmation screen: The confirmation screen description field in embed flows now supports markdown rendering, giving you more control over formatting.

Platform Enhancements

• Performance Enhancements

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

  • Support for additional South African banks: Bank of China, Bidvest Bank Alliances, and VBC Mutual Bank have been added across the platform.
  • SMS-based two-factor authentication restricted to local numbers: Users with foreign phone numbers are no longer offered SMS-based 2FA, preventing failed OTP attempts and ensuring a smoother login experience.
  • Data export date range caps: Exports will soon be limited to the last six months of data, with new date range options available when creating exports. Custom date ranges will also be capped at six months.
  • Improved handling of duplicate policy update requests: A deduplication safeguard was added to prevent the same policy from being processed multiple times in a single batch, improving data integrity.
  • Prevent duplicate policy documents: A check is in development that will prevent identical policy documents from being generated on a policy.
  • Improved internal monitoring and reliability: Several updates were made to improve how the platform monitors system activity and surfaces issues, helping detect and investigate problems more quickly.
  • Improved internal development tooling: Updates were made to internal development workflows to support faster and more consistent delivery.

• Billing Enhancements

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

  • New failure code handling for Nedbank: A previously unrecognised Nedbank failure code is now automatically handled, ensuring affected payments are resolved without manual intervention.
  • Improved payment processing reliability: Backend updates were made to improve how large payment files are processed, reducing the risk of errors when handling high-volume batches.
  • Lapse requests now cancel pending NTU: When a lapse request is created, any pending not-taken-up request on the policy is now automatically cancelled, preventing conflicting lifecycle actions.
  • Ongoing optimisation of billing alerts: Several improvements were made to billing alerting and payment batch handling to reduce false positives and improve accuracy.
  • Continued work on the new policy ledger: Ongoing improvements including validation, verification, and rollback support. This work remains in development and is not yet available for client use.

• Bug fixes

  We’ve addressed key issues to improve system reliability:

  • Fixed billing day change calculation: Resolved an issue where changing a policy's start date on the same day it was issued could result in a double-counted pro-rata adjustment, leading to an inflated first premium.
  • Fixed pro-rata calculation for non-UTC organisations: Resolved an issue where pro-rata calculations for billing day changes defaulted to UTC instead of the organisation's configured timezone, which could cause off-by-one day errors.
  • Claim view now refreshes after policyholder update: Editing a policyholder's details on the claim view page no longer requires a manual reload — data now refreshes automatically after saving.
  • Fixed input data on alteration packages: Resolved a bug where input data returned by product module code for an alteration package was being ignored.
  • Fixed policies not lapsing when expected: Resolved an edge case where certain policies were incorrectly excluded from lapse processing, even when they met the criteria based on consecutive failed or reversed payments.
  • Fixed batch size configuration not saving: Resolved an issue where batch size values were silently dropped when creating or updating a configuration, due to a field naming mismatch between the Dashboard and the platform.
  • Details view improvements on smaller screens: Resolved an issue where notes were cut off on policy, claims, and application views on smaller screen sizes.
  • Product module timeout errors now logged: When product module code exceeds the execution time limit, the error is now handled explicitly and a clear message is added to the run logs.

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.