User Interface
      Back to home
      1. Knowledge Base
      2. User Interface

      Decision Engine

      Product Feature Guide

      Table of Contents

      Introduction

      Decision Engine Workflow

      Credit Card Products

      Steps for Managing Credit Card Offers

      Introduction

      Note: This feature is tenant specific and the contents of the guide are not applicable if it is not enabled in your environment.  

      FundMore’s Loan Origination System (LOS) has the capability to initiate both automatic or manual calls to the lender’s Decision Engine. With this feature, the LOS initiates a call to the Decision Engine. The Decision Engine automatically assesses the deal and makes product recommendations based on a predefined set of rules. These recommendations are then sent back to FundMore and displayed in the LOS. The initial assessment happens on application ingestion except when an application has been automatically declined for any reason (e.g. the Borrower is on a Block List or lives Outside of Ontario, etc. ). In addition to the initial call that happens automatically upon ingestion, additional calls can be made throughout the application process as changes are made to the application. This integration ensures swift, thorough, and informed decision-making processes on deals. 

      Decision Engine Workflow

      For deals that are not auto-declined on application ingestion, the LOS initiates an automatic call to the Decision Engine. The LOS will organize the data from the deal, along with all products listed in Requested Mortgages, and send it to the Decision Engine. Upon receiving the data from FundMore, the Decision Engine (DE) provides the following response:

      • An overall recommendation
      • One recommendation per product (Requested Mortgages)
      • Cross-sell options, including potential credit cards that can be offered with the mortgage

      The LOS will receive the response from the DE. To view the response, click on the DE icon located in the bottom right hand corner of your screen.

       

      This will open a pop-up window that displays the “Overall Application Decision” received. The response could be one of the following: Declined, Manual Review, Approved, and Pending. 

      To review the information related to the recommendation, click on the arrow next to the decision. 

      There is a tooltip at the top of the side bar that indicates the date last updated and the number of submissions to the Decision Engine. 

      Users can also manually resubmit to the DE as many times as they need to. 

      The ability to resubmit deals is permission-based. It is linked to users with a role where the “Submit application to decision engine” permission is enabled.

      When there are changes made on an application, it is necessary to resubmit it to the Decision Engine for reassessment. Our system includes a built-in mechanism to automatically detect any changes made since the last submission. Within the pop-up window, there will be a warning sign prompting users that a resubmission is necessary.

      To resubmit an application to the DE, click on the ellipsis at the top of the pop-up window and select Submit to Decision Engine. 

      When resubmitting multi-product applications, only the active products are pushed to the Decision Engine. If a product has been declined in a previous submission, it is automatically filtered out, and only the remaining active products will be assessed. This ensures that declined products are excluded from further submissions, streamlining the review process. For instance, if an application contains both a Mortgage and a Secure Line of Credit product, and the Secure LOC is declined, only the Mortgage will be resubmitted to the DE.

      After a resubmission, only the latest response will be displayed as indicated in the tooltip.

      If changes are detected, the system will prevent funding or conditional approval of the deal until the application is resubmitted to the Decision Engine for review. Users attempting to proceed with funding or conditional approval will see the following pop-ups:

      The results generated from the DE will not block conditional approval, it is displayed solely for informational purposes. Conditionally approve will be blocked only if the call to DE was not made (i.e. an error occurred), or if the application data (required fields from DE) have been changed since the last submission. In either case, the following pop-up will be displayed: 

      An in-app notification will be generated for each response received. 

      All calls to the DE and their corresponding responses will be logged in the application history. This includes any errors encountered during the process. 

      Credit Card Products 

      To complement the Decision Engine feature, we have included a Credit Cards tab in the Stakeholder Details widget. Any credit card results (per applicant) generated in the DE call will be displayed here. 

      Users can click on the ellipsis to view the details of each offer:

      To disable an offer, uncheck the Present offer option:

      A warning icon will appear beside the applicant’s name if there is an issue with the offer. Simply hover over the icon to view the identified issue:

      Steps for Managing Credit Card Offers

      To ensure a smooth process for handling credit card offers, follow these detailed steps:

      1. DE Submission and Presentation of Card Offer
        • The system processes the Decision Engine (DE) submission and generates credit card offers for the applicant.
        • These generated credit card offers are then presented in the Stakeholder Details widget under the Credit Cards tab.
      2. Underwriter Actions
        • The underwriter edits the Stakeholder details (i.e. Enter edit mode).
        • The underwriter clicks the "Present offer" checkbox to enable the offer for the applicant.
        • The underwriter approves the deal and changes the stage accordingly.
      3. VFSA Actions
        • After communicating with the borrower, the VFSA edits the Stakeholder details (i.e. Enter edit mode).
      4. The VFSA selects the appropriate card type by clicking the radial button beside it.
      5. The VFSA enters the "Amount to Request $" which can be lower than the approved amount.
      6. The VFSA clicks the "Offer Accepted" checkbox to indicate that the offer has been accepted by the applicant.
      7. Fulfillment Actions 
        • When an applicant wants the Credit Card, either before or at the point of deal ingestion, click on the ellipsis beside the Decline button. 

        • Click on Credit Card Fulfilled option. 

        • The system will provide a confirmation message at the top of the application dashboard i.e. "Marked as Credit Card Fulfillment on (date) with a credit card icon.” 
        • If there is an error, notification will appear indicating that the fulfillment failed. You will also see an orange bar across the top of the dashboard with the same warning. 

        To request for additional fields to be added to the call to DE, a ticket must be submitted to FundMore.ai. Please direct your request to the designated individuals within your company responsible for initiating support tickets.

        Our system records all activities related to credit card product recommendations generated by the decision engine. These will be tracked in the application history.