Communications overview

Configure automated notifications to policyholders

Overview

🚧

Communications tooling is shared across sandbox and production

Within an organisation, the communications configuration is shared across sandbox and live. Even if you are in sandbox mode, your changes will affect the live communications configuration for your organisation.

Root supports automated email and SMS notifications for a range of standard policy and other lifecycle events. You can also create your own custom events, which can be triggered from the product module code or via the API. Read more about how to configure your own custom events in the custom notification events guide.

For each event, an email and/or SMS notification can be enabled or disabled separately.

To view the available notification events, and to start configuring notification templates for your product module, head to the "Communications" tab under the "Workbench" menu on the Root management dashboard.

28782878

The customer notifications tooling on the Root management dashboard.

Configuring email and SMS templates

Email and SMS templates are customised for each event. Email templates are configured in MJML, and you can dynamically inject policy and policyholder information into the message body for both email and SMS using handlebars. These templates also allow you to configure the email subject and sender details like the "from" and "reply to" email addresses. You can define organisation-wide layout templates to re-use the same header and footer layouts and branding across different email templates.

28782878

Configuring an email template for the "policy issued" event.

The notifications configuration is product specific. For each product module you can enable or disable different events, and use different message templates.

🚧

Master templates vs. product module specific templates

Root enables you to define master templates that apply across all your organisation's product modules.

Note: If you disable a notification that uses as master template for one product module, that notification will also be disabled for other product modules in your organisation that use the same master template.

To disable an event for one specific product module without affecting your other product modules, make sure to use a product module specific template.

Email notifications and attachments

Email notifications for certain events include attachments. You can read more about the different policy documents, how to configure templates for them, and when they are first generated in the policy documents guide.

The tables below show which documents are attached to standard notification events. For custom notification events, you can configure which attachments are included in the email for each event.

πŸ“˜

Not all emails include attachments

The events listed under the following categories do not include attachments: payment events, claim events, and complaint events.

Standard policy events

The following policy events are not currently supported, and are excluded from the table: covered people updated, sum assured updated, policy requoted. We recommend disabling these events.

EventTerms filePolicy scheduleWelcome letterAnniversary letterCertificate
Policy issuedβœ…βœ…βœ…
Beneficiaries updatedβœ…βœ…βœ…
Debit orders activatedβœ…βœ…βœ…βœ…
EFT activatedβœ…βœ…βœ…βœ…
Policy cancelled
Policy lapsed
Policy not taken up
Policy expired
Policy updatedβœ…βœ…βœ…
First premium payment
Policy reactivated
Policy anniversaryβœ…βœ…βœ…βœ…
External payments activatedβœ…βœ…βœ…βœ…
Alteration package appliedβœ…βœ…βœ…

Standard payment Method events

EventTerms filePolicy scheduleCertificate
Payment method blocked
Payment method failed verification
Payment method updatedβœ…βœ…βœ…

Standard application events

EventQuote summary (application PDF)
Send application pdf to policyholderβœ…