Can't find what you're looking for?

Tell us what you were searching for and we'll get back to you.

  • Contact Us
CA
CA English (Canada)
US English (US)

Quandri Knowledge Hub

Can't find what you're looking for?

Tell us what you were searching for and we'll get back to you.

Browse topics

  • Welcome to Quandri
    • Renewal Intelligence Platform
      • FAQs
        • Support
          • Updates

            Can't find what you're looking for?

            Drop us a message
            • Knowledge Hub
            • Renewal Intelligence Platform
            • General
            • Enabling Multi-Bot Processing for Renewal Reviewer

            Enabling Multi-Bot Processing for Renewal Reviewer

            Updated March 30th, 2026 · 3 min read

            On this page

            Overview What you'll do Before you begin Step 1: Create additional Epic users Step 2: Add credentials in Quandri Step 3: Create an Epic workgroup Step 4: Update Epic activity settings Validation checklist

            Overview

            Quandri can run using multiple Epic user logins in parallel (also known as “multi-bot”). This increases processing throughput for high-volume teams by having multiple processes work from the same shared pool of activities.

            What you'll do

            • Create additional Epic users (one per login)
            • Add each Epic login to the Quandri platform, setting up MFA if applicable
            • Create an Epic workgroup containing all users
            • Update Epic activity configuration so activities are assigned to the workgroup, not an individual user

            Before you begin

            You will need:

            • An Epic admin who can create users and workgroups
            • Epic usernames and passwords for each user
            • An IT admin if your Epic login requires MFA/2FA

            This guide references the Renewal Reviewer Implementation Guide.


            Step 1: Create additional Epic users

            Create one Epic user login per process you want running in parallel.

            Recommended approach:

            • Copy an existing working Quandri user — this is the fastest way to keep permissions consistent.
            • Give each new user a distinct User Code (for example: QUAND02, QUAND03).

            Minimum setup checklist (per new user):

            • Assign an Epic license
            • Set User type to "User"
            • Ensure correct database access
            • Uncheck "Force password change"
            • Ensure an Employee Code is assigned
            • Ensure required permissions are granted — copy permissions from the original Quandri user to ensure they are identical
            • Ensure the columns visible on every user's Home Base include "Entered On" and "Code," and that the column "Contact Via" is removed
            • Ensure the columns visible on every user's Policies screen include "Line Downloaded Premium," "Policy Estimated Premium," "ICO," and "PPE"

            Reference the Employee Account/Login Setup section in the Implementation Guide.


            Step 2: Add credentials in Quandri

            In the Quandri platform on the Login Setup page, add each Epic login as a separate set of credentials under the product's Epic-related settings.

            For each Epic credential set, enter:

            1. Login
            2. Password
            3. Leave the OTP Secret Key field blank

            Note: If your Epic environment requires MFA or SSO, you'll need a self-hosted email account compatible with your authentication provider instead of using the default Quandri reporting address. Reference the MFA/SSO section of Part 1.1 in the Implementation Guide.

             

            Step 3: Create an Epic workgroup

            In Epic, create a workgroup that contains every Epic user added in Step 2.

            The workgroup acts as the shared queue Quandri will pull activities from. Create one workgroup per pool or product.


            Step 4: Update Epic activity settings

            Update Epic so the Quandri activities are assigned to the workgroup, not a specific individual user.

            For each activity code Quandri should process, update the activity's owner/assignment settings so the owner is the workgroup (not "Specific Person").

            Reference the Interface Settings section in the Implementation Guide.


            Validation checklist

            After completing the steps above, confirm the following:

            • Each Epic user can log in successfully
            • Activities are appearing under the workgroup's queue
            • The new user(s) can see the required columns

            Was this article helpful?

            Yes
            No
            Give feedback about this article

            Related articles

            • What types of policies can be processed?
            • Can the Renewal Reviews process policies where the carrier has changed year on year?
            • What does the Renewal Review Capability do?

            • Customer Stories
            • Blog
            • Newsroom
            • Quandri.io

            Copyright © Quandri 2026

            Privacy policyTerms and conditionsCookies Policy

            Knowledge Base Software powered by Helpjuice

            Expand