Root release update | August 2024

What's new this month? 🚀

  • Download attachments for supporting documentation

    This update allows you to download documents from the supporting documents section in the policies, claims, applications, and complaints domains. Read the Help centre guides.

  • Enhancements to group scheme functionality

    We’ve introduced several feature enhancements for group scheme products.

    • Custom data on members upload: You can now include custom module data in the members CSV upload. We've also updated the CSV format to require snake case headings.
    • Preview of members on CSV update: Before submitting a members update, you can preview the first 5 lines of the members file, allowing for better accuracy and review.
    • Member module data and events: Member module data is now displayed on the member view, and all member events, including notifications, are integrated into the member events sidebar.

  • Webhook updates

    We’ve implemented several improvements to webhooks. Enhanced management and monitoring tooling is now available on the dashboard, and the old view will be phased out on October 21, 2024. If you have any questions, please contact our support team. Read the docs.

    • Improved monitoring: You can now see all queue events for a webhook, grouped by status (successful, failed or are still queued), and filter by date range and subscription. You can also see your webhook’s success rate and response time. When Root didn’t get a response from your server, we now display a detailed error message. (Note that the new view will only show queue events and attempts created sinceJuly 19, 2024, and going forward data will only be available for the past 90 days.)
    • Ability to retry webhooks: You can now retry failed queue events individually or in bulk. Retries will be added to the low priority queue.
    • Enhanced management: You can now turn a webhook on and off. We store queue events for disabled webhooks so that you can retry them. The full webhook activation history is also available. If you no longer need a webhook, you can now archive it.
    • Prioritisation: If a webhook attempt fails or the endpoint takes longer than 5 seconds to respond, the webhook (and all future attempts) will be deprioritised. Once an attempt succeeds in less than 5 seconds, the webhook will be reprioritised. This ensures faster delivery of webhooks to healthy endpoints. (Note that production webhooks are always prioritised over sandbox webhooks).



If you have any suggestions or feedback, please share them with your Project Lead or submit them via the Root product roadmap so that we can take them into account.

Let's build this awesome new future of insurance together 💪