iGO Product Update – January 2021

  • iPipeline

Check out our new enhancements including improving the ability to assign a custom value to the applicant ID in ExamOne’s Paramed Solution, correcting the timeout issue between the iGo session and Munich RE AIS if a user is still active in the question screens, and creating an easier navigation to the Help page on our customer portal. There are also a number of fixes as described below.


  1. Allow for a custom value to be used for the applicantId for our Paramed Scheduling integration with ExamOne
    This enhancement allows carriers to choose a custom value to assign to the applicantID value in ExamOne’s paramed scheduling solution. Currently this value is set by iGO and is not configurable to a value based on the carriers requirements. This enhancement provides the carrier the capability to tie the identifier within the Paramed Scheduling solution to a value that is relevant to their operations. This enhancement is available to customers using our Paramed Scheduling integration with ExamOne.

  2. Session Timeout update for Munich RE AIS Integration
    This is enhancement improves timeout handling for implementations integrated with Munich RE AIS solution. With this enhancement iGO will determine if the user is still active in the Munich RE AIS question screens and if so it will keep the iGO session alive. Prior to this enhancement if the user was acting within the Munich RE AIS question screens for longer than the iGO session timeout the iGO case itself would timeout. This would cause the users to have to log back into iGO to complete the case. This enhancement now ensures the iGO session will not time out while the user is answering question within Munich RE AIS.

  3. Need Assistance Help Menu integration to the iPipeline Customer Portal
    This enhancement enables the Help Menu option to navigate the user to the Help page on iPipeline’s Customer Portal.

    Upon clicking the Help option the user will navigate to the Customer Portal Help page. By doing this the user will have access to material and content to help with them with any issues they may have encountered.

    On this page the user will have access to a substantial amount of information to help with any issue or question they may have. This page will provide Knowledge Base articles, FAQ, training materials and videos.


  1. Text My Pin multi-factor authentication screen locks after two failed attempts in Client Collaboration
    This fix resolves an issue where the screen used to enter the pin sent to the consumer’s mobile phone locks upon entering the correct pin on the third try after two unsuccessful attempts. This fix allows to the user to try a third attempt to enter the proper pin before locking the user out. If the correct pin is entered on the third attempt the user will be allowed to proceed. If an incorrect pin is entered again on the third attempt the user will see the proper screen and message notifying the user they have exceeded the allowed login attempts. This issue only occurs for carriers using Text My Pin for authentication into Client Collaboration. Carriers using Text My Pin for access to eSignature were not impacted by the issue.

  2. Screen content cutoff in Client Collaboration when using custom CSS
    This update resolves an issue where the screen content in Client Collaboration did not fully load. This would only occur for carriers using the original client collaboration solution who have also utilized their own custom CSS. In this instance the custom CSS did not include an element used by iGO. With this fix iGO was updated to handle the use of the customers custom CSS to enable the content to fully display.

  3. Consumer accessing Client Collaboration for a case created through a BGA
    This fixes resolves an error encountered when a consumer accesses Client Collaboration to complete their portion of a case when the case was created by an agent who accessed iGO through a BGA. Prior to this fix when the consumer would click on the link in the email to access the case the consumer would see an error. With this fix the consumer can now successfully click on the link and navigate to the landing page to authenticate into their application for completion.