Configure Policies Notifications
(Doc ID 2413901.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Health Insurance Enterprise Policy Administration - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124 version, Processing
Configure Policies notifications
The system should automatically send notifications (mail/sms) prior to the current policy's expiration date. The time in which this notification will be sent (i.e. how many days before the expiration) should be configurable.
System will have the ability to configure:
◾the event that will trigger the notification (i.e. 30 Days before renewal)
◾the receiver(s) of the notification (i.e. customer, broker, sales team etc.)
◾the content of the notification per receiver (i.e. the upon receiving a request notification should carry information to enable customer to follow-up, such as reference number).
Process will be initiated automatically 60 days (configurable number) before the policy expiry date or manually upon customer's request.
Renewal process will notify and assign the proper tasks to the related departments (i.e. Underwriters, Sales Team and Sales Operation).
The Notification Mechanism should notify the customers for expiring policies and potential renewals.
The number of days (usually it is 60 but it should be dynamic and configurable) prior to the policy expiry and the way of communication (sms, mails) should be configurable by the user based on various configurable criteria. This notification will be referred to as renewal notification.
Apart of the aforementioned external notification , another internal notification will have to be sent within Daman Sales Operations department, 30 days prior to the Policy Renewal in case the original external notification was not followed up or there was no reply.
Daman Requirement ID: SAL126.96.36.199
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document