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:

• Assign and reassign policies to user groups via API: You can now assign a user group when issuing a policy through the API, as well as use the Update user group policies permission on an API key to reassign user groups on policies. This new capability makes it easier to manage policies based on team or organisational structure. Read the docs.
• New lifecycle hook: You can now use the afterPolicyPaymentMethodAssigned hook to run custom logic when a payment method is assigned to a policy. This fires after the afterPolicyIssued hook if the assignment happens during issue. Read the docs.
• Additional beneficiary fields in Web and Embed: You can now configure address fields on the beneficiary form, with support added to both the dashboard and embed flows. We’ve also added the date of birth field to Embed to ensure consistency with the dashboard experience. Read the docs.

Platform Enhancements

• Performance Enhancements

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

  • Improved styling and formatting in claim alerts: We’ve upgraded the claim alert blocks to support markdown and aligned them with our latest Rootstrap styling. This makes alerts more readable, with support for elements like line breaks and lists. Read the docs.
  • Centralised logging service: Platform logs are now routed into Datadog’s centralised logging service, providing a unified, searchable view across services. Structured logging improves clarity and helps surface issues faster.
  • Queued processing for lifecycle and collection module hooks: We’ve added SQS queues for handling lifecycle and collection module hooks to improve processing reliability.

• Billing Enhancements

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

  • Improved error output on calculateBillingChange: We’ve enhanced error handling on calculateBillingChange to return clearer messages and structured metadata when billing information is missing. This makes debugging easier and helps identify the affected policy more efficiently.
  • Preventing duplicate communications on unchanged payments: We’ve updated the payment processing logic to avoid triggering communications when there are no actual changes to the payment record. This reduces noise and prevents duplicate communications being sent unnecessarily.
  • Optimised debit premium processing: We’ve improved the debit premium job by introducing batching and a queuing mechanism for concurrent processing. This enhancement is designed to increase speed and reliability, particularly for high-volume billing operations.
  • Improved lapse and NTU prevention logic: We’ve enhanced the policy lapse and NTU prevention experience with more accurate date checks and clearer UI behaviour. The visibility of actions like “Prevent” and “Resume” now correctly reflects policy settings, current date, and user permissions.
  • More flexible handling of payment failures: We’ve updated our billing logic to support configuration of failure codes that should not trigger blocking of a payment method. This allows us to prevent unnecessary disruptions for edge-case failures while maintaining overall payment reliability. Read the docs.

• Bug fixes

  We’ve addressed key issues to improve system reliability:

  • Fixes to cancel policy modal: We resolved unintended bugs that affected the cancel policy modal, including fields being marked as required incorrectly and the modal not resetting correctly when closed.

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.