Why did we enable these features?
Agents Could Only Import Form Data from One Policy at a Time - Previously, agents could only import form data from one policy at a time from Epic into an Indio submission. If a submission contained multiple policies or lines of business (LOB), the agent had to import policy data sequentially, which was inefficient. Additionally, each subsequent import of policy data would overwrite any common fields in the submission, potentially exposing the agent to unexpected E&O issues if the data from the last policy imported had conflicting data.
NOTE: Data conflicts often occur when policy data is imported from multiple policies and the values for common fields across policies are different. Indio only has a single field for conflicting values to flow into so the agent must decide which data (if any) they want to import in the submission.
Data Conflicts Were Present in Imported Form Data - In Epic, ACORD 125 data is stored separately for each monoline policy. When agents imported form data from more than one policy into an Indio submission, ACORD 125 data was overwritten on each subsequent data import since the Indio submission can only accept ACORD 125 data from ONE policy at a time. Submissions that contained form data from multiple imported Epic policies led to E&O exposure for agents and agencies when common ACORD 125 field data conflicted between the two policies being imported.
Agents Were Unable to Import Schedule Data Only - Previously, agents were only able to import form data, without an option to import only schedule data. Form data includes all form data plus the schedule data. In many cases, agents only need the schedule data imported.
Fake blanks in Indio forms were being exported back to Epic - Previously, if policy data existed in Epic for a given field, but that field had been left blank by the insured or agent in Indio, that “fake” blank would be pushed back to Epic upon export from Indio and would overwrite the previous value in Epic, creating additional E&O exposure for the agent.
Benefits of the Features:
Allowing agents to import form data for up to 3 policies at a time, will save agents significant time. Allowing agents to resolve common field data conflicts upon importing from multiple policies, we will ensure the data is accurate and reduce the possibility of an E&O exposure. Allowing agents to import schedule data only will save agents time. Preventing fake blanks from being pushed back to Epic will ensure the data is accurate and reduce the possibility of an E&O exposure as well.
How Do the Features Work:
Importing form data from up to 3 policies at a time
The agent clicks the New Submission button.
The agent is navigated to the Basic Info step of the create submission flow.
The agent completes all required fields and clicks the Next button.
The agent is navigated to the Import Policy Data step and clicks the Import Data button.
The new Import Policy Data from Epic modal is triggered.
We are now allowing agents to import data into either forms or schedules from the create new submission and renew submission flows.
The agent selects Forms and clicks the Next button.
The agent is navigated to the Select Policies step of the policy data import flow.
Agents can now import data from up to three policies at once.
The agent selects the policies they want to import policy data from and clicks the Next button.
The system fetches data and checks for policy data conflicts.
The next step leads into our next feature overview (resolving data conflicts).
Resolving data conflicts
The system has identified data conflicts. As such, a new Resolve Conflicts step is injected into the flow.
Default selection - The option for setting conflicting fields as blank in Indio should be selected by default.
If the agent opts to resolve conflicts with data from one of the to-be-imported policies, then all fields in conflict should be populated with data from the selected policy.
The agent clicks the View Data Conflicts button.
The Data Conflict Details modal is triggered. The agent clicks the Close button.
The agent proceeds with not importing data for fields that are in conflict (recommended) and clicks the Next button.
The agent is navigated to the Review Data step. The agent clicks on the Review Data button for Commercial Application Data.
The Review Data full-screen overlay is opened. The agent clicks on the View Details link for the “Is there a safety program in effect?” question.
A: If a field is set to blank due to the agent choosing not to import data for fields that are in conflict the message shown at right should display.
B: Clicking the View Details link triggers the Data Conflict Details modal.
The Data Conflict Details modal is triggered. The agent clicks the Close button.
Please note that in this context all questions that contain conflicts should be displayed in the modal.
The agent clicks the close button to dismiss the Review Data full-screen overlay.
The agent clicks the Proceed with Import button.
The Confirm Import modal is triggered. The agent clicks the Import button.
The import animation displays.
The agent is navigated to the Finish Import step.
The system should also surface ACORD forms that correspond with the policy types of the imported policy data.
The agent selects ACORD forms to add to the submission and clicks the Finish button.
The agent is navigated to the Submission Details page. The selected ACORD forms should display in the forms section and should be populated with imported policy data.
Importing Schedule Data Only
The agent clicks Import from Epic in the Actions menu.
The Import Data from Epic modal is triggered.
The agent selects Forms and clicks the Next button.
The agent is navigated to the Select Policies step of the import flow.
The agent selects the policies they want to import policy data from and clicks the Next button.
The system fetches data from Epic.
The agent is navigated to the Select Schedules page. Schedules are pre-selected. The agent clicks the Import button.
The Confirm Import modal is triggered. The agent clicks the Import button.
The system creates a schedule workbook and the agent is navigated to the submission details page.
Preventing fake blanks in forms from being exported to Epic
The agent clicks Export to Epic in the Actions menu.
The Export to Epic modal is triggered.
The agent opts to export to forms and clicks the Next button.
The agent is navigated to the Select Policy step in the export flow.
The agent selects a policy to export form data to and clicks the Next button.
The system checks for changes between Indio and Epic data.
The agent is navigated to the Review Changes step in the export flow and clicks the Review Changes button for the Commercial Application Data data category.
The Review Policy Data Changes full-screen overlay is triggered. The agent reviews the data and clicks the Close button.
NOTE: Only fields with values or fields explicitly set as blank by the agent or insured will be pushed back to Epic. Currently, if a field is blank in Indio and left blank by the agent or insured, a “fake” blank will be pushed back to Epic where it can potentially overwrite existing data for that field.
The agent clicks the Proceed with Export button.
The Confirm Export modal is triggered. The agent clicks the Export button.
The system begins exporting data to Epic.
The agent is navigated to the Finish Export step. The agent clicks on the Done button.
The agent is navigated to the submission details page.
Still have questions? Feel free to chat with our support team using the chat feature located in the bottom right-hand corner of the platform or email support@useindio.com.
Note: The Indio Technologies platform is most optimized on the browsers such as Google Chrome or Firefox. If you use Internet Explorer there may be limited functionality as a result.