This month’s Release Notes are focused on the great work performed by our Forth Development and Quality Assurance Teams to enhance your user journey. Get ready to elevate your CRM Experience with Forth!
What's New (6)
User Interface to Control Client Refund Type
This new feature provides an easier and cleaner user experience over Client Refund Types. Now, you no longer have to scroll through options to select a refund subtype that applies to you. The Client Refund Subtype dropdown menu will now ONLY offer the refund payment options configured for your client.
NOTE: This update only impacts clients that utilize Forth Pay and does not affect any other gateways.
The following client refund transaction subtypes (which now default to “ACH Credit”) are available:
-
ACH Credit
-
Bank Wire
-
Check
-
Check 2nd Day
-
Check Overnight
Replace Debts After Credit Pull
This new feature controls system behavior around debt handling after credit is pulled to merge or delete existing debt information. You will now find a brand-new Credit Pulls section on the Debt Settings page, accessible via the Admin tab. When you activate the checkbox provided in this section, your system will automatically eliminate outdated contact debt data and replace it with the most current information from credit reports, but only for new unenrolled contacts.
We also updated our credit pull process to account for this new setting (which is turned off by default). If enabled, the system checks that the contact has no enrollment date. If there is no enrollment date, the system deletes all debt information and re-inserts data from the credit report.
Finally, we rebranded the Add/Edit Debt Status permission to Modify Debt Settings.
NOTE: This feature is designed for contacts who have never been enrolled in a debt settlement program and requires that credit is pulled through Forth CRM using one of our credit pull integration providers.
Forth DataHub
Introducing Forth DataHub, the ultimate tool to enhance your data exploration within the Forth ecosystem. Developed in partnership with Secoda, Forth DataHub is your AI-powered companion to the Forth Managed Data Cloud (MDC), tailored towards efficient documentation, cataloging, and seamless data object discovery.
DataHub empowers you to delve deeper into the core system objects, such as contacts, debts, offers, transactions, and more. With its user-friendly interface, you can easily navigate tables, common queries, frequently asked questions and other valuable resources. We also removed the old Entity Relationship Diagram (ERD) as DataHub provides a more intuitive, comprehensive, and powerful solution.
Benefits of Forth DataHub include gaining insights into the structure of key system objects required to build performance reporting; easily searching and referencing data objects including all metadata and object properties; and with a large collection of frequently asked questions, saving you from the hassle of opening tickets and searching the list in case the community has already answered your query.
Allow DRSP to Process Refunds for Dropped Forth Pay Clients
Traditionally, you have been required to contact Forth Pay if you need to reverse fees or process a refund to a consumer after cancellation. Never again!
We developed a solution to this challenge that provides greater control over refund processing. We introduced the capability to schedule advances and refunds yourself for a dropped or canceled Forth Pay client. This feature speeds up refund processing time and reduces the need for re-enrollment or Forth Pay intervention.
With this solution, you may initiate these refunds only when a client has been canceled from the program, you can only schedule client refunds and no other transaction types, and you can only schedule ACH Credit refunds to the account on record, nor do you have the ability to update the banking information before scheduling a client refund.
Processing a Refund Payment for Dropped Clients starts with selecting a Canceled client via the Enrollments Tab, and selecting “Refund Payment” (see red highlight in the image below).
NOTE: This update only applies to Forth Pay Clients using the Forth CRM who have dropped from the program and have an Account Closure & Balance Refund Request Form in place.
In addition, these pre-approved client refund options are readily available via a Sub-Type dropdown menu on the Transactions page.
Loanosity DSL Updates
Several improvements were made to the Loanosity DSL Integration. These include:
Transmit Gateway Information (DPP-17391) - This update to the Loanosity DSL integration significantly expands the eligibility of consumers that can be submitted via the integration. We revamped the mappings page for the Loanosity DSL integration, introducing a dedicated section for payment gateway settings. There are now mappings for the following payment gateways: FORTH Pay, RAM, CFT Pay, and GCS. This new feature is designed to allow DRSPs to submit contacts that are enrolled in the gateways that are supported by Loanosity, where previously, only FORTH Pay Gateway contacts were able to be submitted to Loanosity DSL via the integration. Each payment gateway section now includes mappings for key fields associated with FORTH Pay, RAM, CFT Pay, and GCS. These fields are Routing Number, Account Number, and Dedicated Account Number
Sending Payment Frequency (DPP-17155) - We updated the integration to send the payment frequency of the program to Loanosity DSL as part of the enrollment process. This will be done by sending payment frequency saved on the enrollment plan.
Add Settled Balances (DPP-17389) - We added the settled account balances (not the calculated balances) of enrolled debts to the API transmission between FORTH and Loanosity DSL
Add Client Savings (DPP-17390) - We updated the Loanosity DSL integration to include the client escrow account balance that is currently saved in the API transmissions/requests that get sent to Loanosity.
Settlement Offer Tags via Webhooks
Formerly, when DSRPs attempted to webhook settlement offer details and map it to the client's notes, the information came over as the tags. This new feature updates the "Settlement Status Change" event trigger to support the transmission of fully rendered settlement offer details into a readable text format via webhook which can be used to update affiliate accounts of the offer details.
Upon any settlement status change, the system now initiates the webhook in which the system now transmits settlement offer details where placeholder tags are replaced with actual client data.
This feature streamlines the communication of settlement offer details between the CRM system and external affiliates or integrated systems; reduces data processing requirements for recipients by ensuring webhooks transmit fully rendered information; and enhances data accuracy and efficiency in updates communicated through webhooks.
What's Improved (6)
Push Estimated / Requested Loan Amount with the New Credit America (NCA) Integration
With this update, the NCA integration now includes a mappings page in the integration settings to map the EstimatedLoanAmount field in the NCA API to a CRM custom field. The estimated loan amount value is then transmitted based on the custom field it is mapped to. This lets a customer map their internal value for the estimated loan amount. Ultimately this allows the NCA integration to include the estimated loan amount value in the application request that is sent. When transmitting the EstimatedLoanAmount field to NCA it sends in the correct format (any price/dollar fields are converted to numeric).
New Source for Revolving Credit Limit in Xactus360
This improvement (available for all Xactus 360 customers) updates a specific field related to the revolving credit limit in the XML received from Xactus360. This changes the mapping for this field from the PORTCBL field to the RevolvingCreditLineUsed field attribute for the revolving credit limit mapping. This new value will be expressed as a percentage in the score models section of the Contact Dashboard.
Note: No previous customers will be updated as part of this change, only new credit pulls going forward.
Email Lender Submission with Multiple "To" Addresses
For Centrex Business Finance Accounts - Until now, when you submitted an advance via email to a lender that had multiple submission contacts, the system sent separate emails to the contacts. With this update, the system now sends a single email, so multiple representatives at the lender organization can view and respond to submissions in the same email thread.
Move Process Date and Process Next Business Day with Supervest
For Centrex Business Finance Accounts that use Supervest, we are moving transactions to the next business day and also processing transactions one day in advance. This change updates a transaction’s process date that is being created for Supervest from today to the next business day. In addition, it updates the back-end logic for processing transactions to process transactions from today to the next business day.
Add SAVE Plan for Student Loan Accounts
With this update, Forth now offers the “Saving on a Valuable Education (SAVE) plan for student loan accounts. The SAVE Plan is the newest income-driven repayment (IDR) plan offered by the U.S. Department of Education. This plan will replace the existing “Revised Pay As You Earn" (REPAYE) Plan. We updated the “Retrieve Loans and Programs” page of the system to add SAVE as a new student loan repayment plan option within Forth’s student loan calculator.
In addition, a modification was made to our Student Loan Calculator in the background to account for updated poverty line percentage values used in the SAVE plan (compared to the existing REPAYE plan).
API Updates (1)
Pausing a Contact via API
This new feature adds the ability to pause a client via the API which would pause all payments from being initiated from that client. We created a new endpoint to update a contact to the ‘paused’ state in the system. When a contact is paused in this fashion their payments will not process just as if they were paused manually via UI and the UI will reflect the paused state. Contacts may also be un-paused at the UI when paused from the API. API Documentation on this feature is available by clicking HERE.