Welcome to Quandri! This is your guide to setting up your Quandri Renewal Reviews capability. At the successful completion of this easy-to-follow checklist, we can begin the testing stage. 

Epic Configuration

Employee Account/Login Setup

1. Epic Employee Account Setup
   1. Set up a new email account for each Quandri capability (eg. Renewal Reviews, eDoc Management, Policy Requoting)
      1. For your first capability, you can use reporting@quandri.io. 
      2. For subsequent capabilities, they will need their own email address for login. For example: reviewer@yourbrokerage.com, renamer@yourbrokerage.com, requoter@yourbrokerage.com 
      3. You do not need to create a full-fledged MS365 account, just an email address that is able to be associated with an Epic user account. 
   2. MFA/2FA/SSO
      1. If your brokerage uses MFA/2FA, you will need to use a self-hosted email account (eg. reviewer@yourbrokerage.com) for the Epic login to ensure that it will be compatible with your MFA provider settings. 
      2. If your brokerage uses MFA/2FA, please follow the steps here for setting up the MFA/2FA integration. You will need to set this up for the ability to use third-party OATH tokens 
      3. If your brokerage uses SSO, please follow the steps here for setting up the SSO integration
2. Epic Login Setup
   1. Assign an Epic license to this email address and provide it with a distinct User Code and Name such as QUAND01 and Quandri Bot. Make sure to assign an Employee Code to the new Epic user as well. 
      1. Subsequent capabilities can use sequential User Codes such as QUAND02, QUAND03, etc. 
   2. Remove check from “Force password change”
   3. Ensure User type is “User”
   4. Ensure correct Database access is granted
3. Epic User Permissions
   1. Ensure the Employee Code is entered
   2. All Structure combinations related to personal lines need to be added
   3. We recommend creating a security group to be added to the bot user(s)
   4. Follow the below guide to set the appropriate permissions.

User Permissions

Provide Quandri’s Epic user with the following permissions. 

Under Program Access

1. Area: General-Sub Area-Activities
   1. View
   2. Add 
   3. Edit 
   4. Close
   5. Note Access for each of the areas Personal lines would use
   6. Add a notes
2. Area: General-Sub Area-Attachments
   1. View
   2. Attachment View Access: Financials 
   3. Attachment View Access to other applicable departments
3. Area: General-Sub Area-Contacts
   1. View
4. Area: General-Sub Area-General
   1. Change Password
   2. Display in List view Regardless of Confidential Client Access
   3. Access Account Regardless of Confidential Client Access
5. Area: Insured Clients-Sub Area-Claims
   1. View
6. Area: Insured Clients-Sub Area-Insured Client
   1. Locate
   2. View
   3. Confidential Client Access
   4. Contacts
   5. Attachments
   6. Activities
7. Area: Insured Clients-Sub Area-Policy
   1. View
   2. View Servicing/Billing
   3. View Application
   4. Area: Prospective Clients-Sub Area-Claims
   5. View
8. Area: Prospective Clients-Sub Area-Policy
   1. View
   2. View Servicing/Billing
   3. View Application
9. Area: Prospective Clients-Sub Area-Prospective Client
   1. Locate
   2. View
   3. Confidential Client Access
   4. Contacts
   5. Attachments
   6. Activities

Password Policy

1. Change Password Policy
   1. To manage password changes, the Maximum Password Age needs to be set to 90 days
   2. Navigate to Configure>Security>Logins
      1. Select Actions from the Options Bar and click ‘Password Policy’
      2. On the History/Date tab ensure the “Maximum Password Age” is set to 90 days
          

Home Base

1. Home Base Select Columns (this must be done for the Quandri user)
   1. Add to the activities area: 
      1. “Code” 
      2. “Entered On” 
   2. Remove from the activities area columns: 
      1. “Contact Via” 

Policies Screen

1. Policies Screen Select Columns (this must be done for the Quandri user)  
   1. Add to the Policies Screen Columns:
      1. “Line Downloaded Premium” 
      2. 

The following settings relate to the activity code we will use to trigger the Renewal Reviewer. It should be specifically for Renewals documents. The following information will reference an “EREN” activity, which may or may not be the current activity code you use for this purpose. If you use an EDOC activity for these, it will need to be replaced with an EREN for renewals documents specifically. Please reference this page for creating a new activity if you do not have one dedicated to renewals documents specifically.

Additionally, if Commercial Lines or other documents are using the same activity code, these will need to be separated from the EREN into their own activity code. Please reference this page for setting up a new activity code specifically for Commercial Lines or other non-Personal Lines documents.

1. Under Company settings, select your master company file to update.
2. If specific branches, departments or profit centers will be used for the Renewal Reviews capability, you can configure the activity to just those dedicated structure combinations.
3. Ensure all Renewal codes are configured as Accept.
4. All other codes will require a separate activity code if they are being accepted.
5. If you find carriers are sending renewals as Reissues or Rewrites then you will want to configure these codes to the EREN activity also.
6. Under the eDocs & Messages tab, the EREN activity needs to be assigned to all renewal related codes;
   1. RED-Renewal Policy Declaration
   2. RNC-Renewal (Change Format)
   3. RNI-Renewal (Image Format)
   4. RWC-Renewal Change
   5. RWI-Renewal Notice (Image Format) *see note below 
   6. RWL-Renewal *see note below
   7. RWN-Renewal Notice (Change Format)
   8. RWQ-Renewal Quote
   9. RRQ-Renewal Re-Quote

      Be mindful of the new CSIO eDoc codes, as insurers adopt these, you may be require to monitor for adjustments. For example, Economical has implemented the new eDoc codes but continue to use the old RWL code for the “OK eDoc delivery” document sent when clients are set up in portal to receive digital documents directly from Eco. Currently, if you map Eco’s RWL code to EREN it may result in duplicate activities to the Quandri bot, potentially leading to duplicate notifications/activities for your teams. Another example is with CAA who are on the old codes still however, they use RWI for membership letters, you will not want to code RWI for CAA as EREN either. You can monitor these codes and what are being sent under them by running interface reports within Epic. These examples are subject to change but are accurate as of 02/27/2025

       

CSIO Scorecard for insurer statuses

New CSIO eDoc Codes

Quandri Configuration

Quandri Platform Access

1. The Quandri platform can be accessed at: https://app.goquandri.io/. Please bookmark this link for future access 
2. Email invites
   1. Each member of the project team will receive an invite to set up your user account via email 
   2. Please let your Implementation Manager know if you did not receive this invite 

Integrating Quandri with Epic

Please enter your bot’s login credentials for Epic on the Login Setup page (also listed in General Configuration below). 

Renewal Reviews Configuration

Follow the below steps for the general configuration of the Renewal Reviews capability.

General Configuration 

1. Configuration: 
   1. Login Setup: Add the Epic user credentials 
   2. Habitational/Auto/General Attributes: Review and adjust to your preference
2. Activities & Workflow:
   1. Renewal Activities: Add the Epic user code for the bot (eg. QUAND01)
   2. Add the activity code for PL renewal dec pages (eg. EREN)
   3. Policy Type:
      1. Add in all policy type codes that you want Quandri to process 
      2. Decide whether or not non-specified policy types get closed or reassigned
   4. Reassignment:
      1. Decide whether the successful activities should be closed or reassigned to someone
      2. Decide who the successful activities should be assigned to: whether that is a user code (eg. SMIJO1) or a Policy level contact (eg. Producer)
      3. Note that you can set up an initial reassignment flow for testing purposes (such as a workgroup with core testing team members) and adjust it later for the actual production workflow (such as Policy Level Contact, Client Service Rep) 
         

         Make sure the user code or servicing contact title is exactly as spelled in Epic 

          
   5. Exceptions Assignment:
      1. Decide who the unsuccessful activities (known as exceptions) should be assigned to: whether that is a user code (eg. SMIJO1) or a Policy level contact (eg. Producer)
          
   6. Secondary User Code:
      1. Set a backup user for successful or unsuccessful activities to be assigned to, in case the specified users from either of the above two steps cannot be found 
3. Schedule:
   1. Confirm what time the download is normally complete. Taking into account the changes during your busy season is important.
   2. All Quandri capabilities should run at least 30 minutes after the scheduled start of the EDI process. If you have your EDI set up for continuous download, you do not need to schedule the Quandri bots around it. 
   3. All Quandri capabilities should run outside of local working hours. If the bots are looking at documents or activities at the same time as a person is, the person may delay or interrupt the bot’s progress. 
4. Daily Reports:
   1. Daily Reports are the daily emails that the bot sends to present information on the bot results and the list of policies that were processed. 
   2. Add email addresses of team members that you wish to receive the daily email.

Additional Activities

“Additional activities” are Epic activities that can be created upon the triggering of certain criteria that are decided by you. This is an optional feature that you can choose to use or not use. This is a powerful feature that will give you more flexibility and control over how Quandri integrates with your team’s renewals workflow. This feature can also replace an existing activity creation generated by a premium increase in Epic, with more flexibility to trigger upon missing coverages or other attributes. 

There will only be one additional activity created for all triggers met. For example, if the premium increased above the threshold, as well as a coverage being missing, and third party liability limit being below a target $2M, all three of these triggers being met will only create one additional activity mentioning all triggers met. 

1. Additional Activity Reassignment:
   1. Decide whether the original activity (EREN) should be closed in the event that an additional activity is triggered
   2. Decide the activity code for the additional activity that will be created
   3. Decide who the additional activity should be assigned to
2. Additional Activity Triggers:
   1. Choose one or more triggers that will prompt the creation of an additional activity
       

Next Steps

1. Reviewing Configuration
   1. During the first weekly sync following the Quandri Kickoff, your Implementation Manager will review your configuration and Epic integration and ensure that everything is set up properly. 
   2. If you are not able to complete the above steps prior to your first scheduled sync following the Kickoff, or if you have questions about any specific details, your Implementation Manager will work through it with you during the meeting. 
2. Beginning Testing
   1. Once we have confirmed that the configuration is correct, we can begin testing. 
   2. To begin the testing process, please assign 5-20 EREN activities to Quandri’s Epic Who/Owner code manually.
   3. As we go through testing, we will make adjustments to the configuration as needed, to ensure that the output results match your needs. When we are satisfied with the results, we can turn on automated activity assignment. 
3. Concluding Testing
   1. Testing will continue for as long as necessary to see satisfactory results
   2. When we have seen successful results through testing, we can begin automatically assigning activities to your Quandri capabilities
   3. Instructions to turn on automated activity assignment for Renewal Reviews here.
      
      

      We are looking for 80%+ successful processing across multiple days in a row, with the Quandri output meeting your requirements