This guide should walk you through the successful setup and configuration of Quandri and the integration with Applied Epic. 

Part 1 and 2 can be completed prior to the Kickoff meeting, with the exception of 1.3, which usually requires some discussion first. If you have any questions, please contact your Implementation Manager. 

Part 1: Epic 

Who: Epic Administrator 

When: Pre-Kickoff if possible 

1.1 Epic user setup 

Quandri Policy Checking requires at least one Epic user/employee to function. Please check your agreement with Quandri to see how many users are required for your agency. 

Employee Account Setup 

The first step is to set up the Employee account. 

If you do not require MFA or SSO to sign into Epic, you do not need to set up a new email account for the Quandri Epic user(s). You can use our generic email address for all Quandri Epic user(s) if this is the case: reporting@quandri.io. 

If you do require MFA or SSO to sign into Epic, please follow the MFA/SSO section below to set up the email accounts and logins. 

Login Setup 

The next step is to set up the Epic login. 

• Assign an Epic license to this email address and provide it with a distinct User Code and Name such as QUAND01 and Quandri Analyze.
• Make sure to assign an Employee Code to the new Epic user as well. 
• Subsequent Quandri users can use sequential User Codes such as QUAND02, QUAND03, etc. 
• Remove check from “Force password change”.
• Ensure User type is “User”.
• Ensure correct Database access is granted.

User Permissions 

Provide Quandri’s Epic user with the following permissions under ‘Program Access’.

1. Area: General-Sub Area-Activities
   • View
   • Add 
   • Edit 
   • Close
   • Note Access for each of the areas Personal lines would use
   • Add a note
      
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
       
8. Area: Prospective Clients-Sub Area-Claims
   1. View
   2. Area: Prospective Clients-Sub Area-Policy
   3. View
   4. View Servicing/Billing
   5. View Application
       
9. Area: Prospective Clients-Sub Area-Prospective Client
   1. Locate
   2. View
   3. Confidential Client Access
   4. Contacts
   5. Attachments
   6. Activities
       
10. Temporary access to the following areas is needed for a view-only mode for us to complete the setup of your Quandri tools.
    1. Area–Employees--Sub Area-Employees
       1. Add Locate & View
    2. Area–Configure–Sub Area-Activity
       1. Add View Codes
       2. Add Work Groups
    3. Area–Configure–Sub Area-Security
       1. Add Login
       2. Add Users
       3. Groups
    4. Area-Configure-Sub Area-Interface
       1. Add Company

Password Policy 

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

MFA/SSO 

Note: If you do not use MFA or SSO to sign into Epic, you can skip this part. Does Epic redirect you to a Microsoft, Duo, or Okta login page to enter your credentials? If so, this part is required. Please share these instructions with your IT team, whether they are internal or external to your agency. 

If your brokerage uses MFA/2FA, you will need to use a self-hosted email account for the Epic login to ensure that it will be compatible with your MFA provider settings. This means that you will need to create a new email address and account for every Quandri Epic user you are creating. We suggest naming them according to the Quandri capabilities that you are setting up. For example: QuandriAnalyze1@YourAgency.com, QuandriAnalyze2@YourAgency.com

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.

If your brokerage uses SSO, please follow the steps here for setting up the SSO integration.

Once you have completed this section, please notify your Implementation Manager, as they will need to close the loop by completing the final MFA or SSO configuration steps. 

1.2 Activity and Interface Setup 

Note: This step can wait until some details are confirmed. Your Implementation Manager can guide you through this stage during the early stages of the project. 

You will need to decide: 

• Which activity code can be used for Quandri activities. This is typically a net new activity code (such as QREN) which will act in a similar way to the commonly used DREN (renewal download). 
• Who activities should be reassigned to after Quandri processes them. This is often a Workgroup during the implementation period, and then a Servicing Role (such as Client Service Rep) afterwards. 

Configure Activity 

Create the activity you plan to use for Quandri with the following settings. We will refer to the activity as the QREN; if you choose to use something else instead, please make a mental note to replace it whenever it is mentioned. 

• Code: QREN 
• Owner Type
  • Specific Owner: QUAND01 
• Default as Open/Closed
• Start Activity
  • 0 days
• When closing manually
  • Default successful
• Further Actions (if applicable)
• Tasks (if applicable)

• Please ensure under “Event” that it displays as “User generated” (under the Basic Settings Tab).

Configure Activity Workgroup, if applicable

You may want to use a workgroup for the reassignment of Quandri activities. If so, set it up now, add the relevant people, and use it as the default owner for the above configured activity. 

• Code
• Description
• Members

Interface Setup 

The following settings relate to the activity code we will use to trigger Quandri Policy Checking. It should be specifically for renewals policy downloads. The following information will reference a “QREN” activity as an example. 

• Under Configure > Interface > Company/Broker - Status Codes tab, select your first carrier to be updated. If you have a Default Company, you can use that one and copy it to the other carriers. 
• Add/update the RWL download activity with the appropriate activity code.
• If specific branches, departments or profit centers will be used for the Policy Checking capability, you can configure the activity to just those dedicated structure combinations.
• All other status codes will require a separate activity code if they are being accepted.
• If you find carriers are sending renewals as Reissues or Rewrites then you will want to configure these codes to the QREN activity also.
• This will need to be completed for EACH ICO and ICO/PPE combination that is supported by Quandri. You can copy the configuration on the Default Company to all relevant carriers. You can find the Quandri-supported carrier list under FAQs. 

Note: For Progressive, replace “RWL” with “RWQ” in the steps below. This is because Progressive sends a Renewal Quote (RWQ) prior to the renewal date, and then only sends the Renewal (RWL) on the effective date IF the policy renews. This is unique compared to most carriers. 

1.3 Adjusting Views 

Home Base 

When signed into the Quandri user(s), under Home Base, click Select Columns 

• Add to the activities area: 
  • “Code” 
  • “Entered On” 
• Remove from the activities area columns:
  • “Contact Via” 

Policies Screen 

When signed into the Quandri user(s), under the Policies screen for any policy, click Select Columns 

• Add to the Policies Screen Columns:
  • “Line Downloaded Premium” 
  • “Policy Estimated Premium”
  • “ICO”
  • “PPE”

1.4 Reports 

There are some important reports that we need in order to process your data properly. These can be exported from Epic per the instructions below. 

Book of Business report 

Please see here how to export a Book of Business report

The purpose of this report is to understand the distribution of policies per carrier and what our coverage currently looks like versus which carriers are missing. 

Company List report (aka Carriers report) 

Please see here how to export a Company List Report 

The purpose of this report is to correctly map all of the various carrier codes (PPE and ICO) to the correct carriers. For example, there may be over a dozen different ICOs that all tie back to Travelers. 

Part 2: Quandri 

Who: Project Lead 

When: Pre-Kickoff if possible 

2.1 Quandri Access 

The Quandri platform can be accessed at: https://app.goquandri.io/. Please bookmark this link for future access 

Email invites

• Each member of the project team will receive an invite to set up your user account via email.
• Please let your Implementation Manager know if you did not receive this invite.
• Additional users can be added by navigating to “Team & Permissions” in Quandri, and adding their email address.
  • “Admin” provides configuration access, whereas “User” only provides Connect end-user access.

2.2 Integrating Quandri with Epic 

• Login Credentials 
  • Navigate to Policy Checking > Configuration > Login Setup and add the Epic license credentials (this may be the Employee Code and password, or the email address and password if using SSO/MFA). 
• SDK 
  • Navigate to Integrations and add the Epic SDK credentials. 

2.3 Configuring Quandri 

Navigate to Policy Checking and review the available settings. Your implementation manager will walk you through how all of this will get set up. 

Some key considerations: 

• Does your agency have a standards checklist? If so, we should set the content under Habitational and Auto to match. 
• What time does your download occur? We should schedule Policy Checking to run shortly thereafter. 
• Who should receive the Daily Report processing summary email? You can add those email addresses to the Daily Reports page. 
• Do you want Quandri to create Additional Activities? If so, what triggers would you like to set to generate these? 
• Who do you want activities to be reassigned to after Quandri processes them? This may vary from testing to production workflows. 

Part 3: Configuration Review 

Who: Quandri Solutions Team 

When: After Part 1 and 2 are completed 

Please notify your Implementation Manager once you have completed Part 1 and 2, and Quandri will conduct a review of your configuration so far. There may be additional changes required if anything above is not set up correctly. 

3.1 Quandri Configuration Audit 

The Quandri Solutions Team will conduct a review of the Epic configuration to ensure it is set up correctly. They will provide a report of their findings with any major changes that need to be made. 

3.2 Reviewing Configuration Audit 

Subsequent configuration updates may need to be made depending on the findings in the report. Your Implementation Manager will discuss these with you. 

Part 4: Testing

Who: Project Lead and Testers 

When: After Configuration Audit is approved by Quandri  

4.1 Initial End-to-End Test

Once configuration is complete, turn on the schedule and activities will start to process. Review the activity notes in Epic, and/or the Quandri Dashboard, and/or the output in the Daily Report emails. Compare this against the reality of the policy. Testing feedback should include anything Quandri missed or reported on incorrectly. 

4.2 Ongoing Testing 

Make a copy of the Quandri Testing Feedback template. Share it with anyone who will be involved in the testing process. 

Once the testing team is set up with everything they need, they should be submitting items to Quandri in the spreadsheet. Quandri will review these and they will get discussed during each weekly meeting. 

4.3 Testing Feedback 

Testers will receive daily reports via email, where the Excel file contains a few tabs:

• Successes: Policies that were reviewed/processed successfully by Quandri
  • Your team should focus its efforts on reviewing these successes to ensure Quandri is accurately reviewing these policies as a broker would
  • These should account for the 80-90% processing rate we are striving for by the time you go live with Quandri
     
• Failures with AMS errors: These are "known exceptions" where Quandri does not have sufficient data to review/process the policy
  • You do not need to review these.
  • These are not counted towards the processing rate. However, our Product team regularly deploy changes to address commonly occurring exceptions across multiple customers.
     
• Other Failures: These are "Quandri errors" such as data extraction issues, bugs, timeouts, etc. 
  • Our team will monitor and address these, as they account for the 10-20% of policies we are not processing.

The same information will be found on the Quandri Dashboard.

4.4 Testing Best Practices

1. Review the Quandri configuration with your team to make sure you understand what attributes & logic will be applied in the summary.
2. Feedback must be provided using the Testing Feedback template linked above.
3. Always include: the policy number, policy type, carrier, processing date, issue found, what is expected and where we can find that information 
   What to Report:
   1. Only report issues: not every single policy we process. If it’s good - no need to list it there.
   2. No duplicates - if something has already been reported, don't report it again (unless it's a different carrier).
   3. Separate each issue - one row per issue, even if it's the same policy
4. Address feedback by:
   1. Adjusting configuration to address feedback items
   2. Submitting product feedback to Quandri for successes only (identify what was missed or reported inaccurately)
   3. Logic Update: We didn’t recognize an endorsement, package, etc.
   4. Bug: Unexpected behaviour
   5. Feature request: New feature that we don’t currently have  
5. Work with Quandri team to prioritize feedback and discuss the resolution timeline
6. Whenever you submit feedback think about the impact and let us know how important this is to your day to day 

4.4 Gathering Requirements 

Quandri won’t be able to fix every single thing reported, at least during the implementation period, so the customer Project Lead will need to help Quandri identify the priority level of each item. Some items will be fixable with Coverages and Rules. 

Part 5: Production Workflow 

Who: Project Lead

When: After Testing is complete and requirements are met 

5.1 Adjusting Workflow 

Once we reach the end of the testing stage, we will need to make some adjustments to the workflow. Primarily, there are two settings that will need to be adjusted: 

1. Reassignment: If the activities are currently getting assigned to the testing team (whether this is a specific user or a workgroup), we should update this to have activities be reassigned to a Servicing Role such as the CSR on the policy. 
2. Test Mode vs. Live Mode: Test Mode reassigns activities after Quandri processes them, but does not add an activity note in Epic. Live Mode reassigns activities, as well as adds an activity note in Epic. If you started in Test Mode, now would be the time to switch to Live Mode. 

Part 6: Team Training and Adoption 

Who: Project Lead, Training Lead

When: Around the time of switching to Production Workflow, whether shortly before or shortly after. 

6.1 Knowledge Sharing Session

Around the time that we switch to the Production Workflow, your Implementation Manager will lead a Knowledge Sharing Session with your frontline team. The content of this session will revolve around how Quandri works and how it applies to the frontline's day-to-day workflows. 

6.1 Ongoing Adoption and Training 

Following the Knowledge Sharing Session, there may be additional training required. This usually gets more granular or agency-specific. This is best led by the customer due to the unique nature of each agency. We will leave it to you to provide additional training as needed to your team.