DONNA Blog

DONNA & AMS Data Integrations

Written by Shashank Dixit | Jul 21, 2022 3:59:33 PM

DONNA integrates with various management systems to gather data about agency operations. DONNA uses this data to run various algorithms such as:

  1. SentiMeter®
  2. Recommendations
  3. Foresight
  4. Renewal Predictions
  5. RoundOut Predictions
  6. Retention Predictions
  7. PIF Retention Calculation

However, all management systems do not provide data with the same level of details or consistency. This causes various numbers to be reported as inconsistent with what is seen on the management system dashboard. Following are the know issues and their impact on the various features of DONNA.

NowCerts

DONNA users who use NowCerts as a Management system are sometimes concerned with the mismatch of numbers of DONNA Dashboards and numbers reported on NowCerts. A few examples below:

  1. Active Premium on DONNA does not match with the premium reports on NowCerts
  2. The count of policies does not match

The primary reason for the mismatch on both the counts is as follows:

  • NowCerts is considering all policies (active, inactive) which have incepted or expired during the last 1 year (year to date - YTD) for reporting the above numbers.
  • DONNA takes into consideration only active policies for reporting the above numbers

For example; if we are viewing the report on 9-17-2021,

  1. NowCerts would consider all active policies between 9-18-2020 and 9-17-2021. This would also include policies that are EXPIRED or CANCELLED as of 9-17-2021.
  2. DONNA Dashboards would consider only ACTIVE policies as of 9-17-2021.

Rather than being inaccurate, the mismatch is different ways of looking at the same data. Though the data reported on the dashboards look mismatched, the algorithms are not impacted.

QQCatalyst™

DONNA users who use QQCatalyst have encountered only 1 issue. The API from QQCatalyst does not expose the policy cancellation date; therefore, the policy cancellation events are missed. As a consequence, cancellation events are not available in the events ecosystem.

HawkSoft

Currently, DONNA users who use HawkSoft do not have access to commission/revenue data on DONNA.

AMS360

DONNA users who use QQCatalyst have encountered the following issue. Policies that are due for renewal and have been provided by the carrier in the download are future date policies, meaning policies with an inception date in the future.

AMS360 reporting factors these policies in calculating policy count and premium, while DONNA considers them only after the existing policy expires and the renewed policy comes into force.

For example; if we are viewing the report on 9-17-2021,

  1. Carriers, some if not all, make "future versions" of policies, which are due for renewal in the next few days, available for download. The AMS360 system, once such policies are downloaded, considers all downloaded "future dated" policies as active.
  2. DONNA Dashboards would consider only ACTIVE policies as of 9-17-2021. The active policies with a downloaded renewed policy are seen as "Active" (let's call these 'FA), while the same policies come up as "Renewed" (let's call these 'R') on AMS360. AMS360 reports the numbers with FA + R while DONNA reports only R. The FA policies are marked as "Invalid" in DONNA. Once the "Date of Expiry" of R and "Date of Inception" of R becomes past, R policies become Inactive, and FA policies are marked as Active.

The mismatch is different ways of looking at the same data, not inaccuracy. Though the data reported on the dashboards look mismatched, the algorithms are not impacted.

General Note Across All Systems

DONNA's recommendation engine scans through the policy holding for each insured to generate recommendations. To check a customer's current status and eligibility for a specific recommendation, DONNA relies on the "Coverage" information from the AMS. Some AMSs provide standard ACORD-based coverage data, while some AMSs have kept it flexible and allow users to update in specific or enter these values into the AMS.

This can cause some recommendations to be missed or some recommendations to be generated even when the policyholder has that recommendation.