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 (1)
Allow Clixsign Requests to be sent to Linked Sponsor Contacts
This new feature allows the sending of Clixsign requests to a linked sponsor contact from the original contact account so that the linked sponsor can collaborate with the contact they are sponsoring and electronically sign on important documents. "Sponsor" has been added as a signer type (allowing users to select it for any assigned signer slot (1-9)), available in the dropdown menu option. In addition, the system now pre-populates the sponsor's information, i.e., Name and Email from the program sponsor field when selected from the dropdown. Such Clixsign documents are now displayed on both the original contact and the sponsor’s contact dashboard. This new feature was released to enhance collaboration and document management within the CRM application, as well as to streamline and improve the signing process by requesting signatures from sponsor contacts and improving workflow efficiency.
What's Improved (5)
Creditor Selection for SMS
This update facilitates the use of individual creditor information with the SMS feature. With this update, the Forth system allows the pre-filling of a designated creditor’s information using creditor-specific tags for SMS templates. This enables broader capabilities with our SMS feature and allows us to send specific creditor/settlement-related updates to the customer.
We added a new dropdown menu option within the ‘SMS’ subtab of the contact dashboard (accessible via the Contacts tab) to select a creditor (see the image below).
You may type in a creditor’s name and the option will auto-fill (see left below) or use the dropdown to make your selection (see right side of the image below). This new dropdown organizes the options as enrolled creditors listed at the top and unenrolled creditors after that for easier searching, and each listing includes the creditor name followed by the Creditor ID.
When a creditor is selected, any template that gets loaded from this point forward and contains the correct tags will populate that creditor’s information.
Lastly, making a creditor selection within this new process now appears in the History / SMS log.
Settlement Rebalance after Reversal Transaction
This new feature enhances Forth Pay accuracy in rebalancing settlements following Unauthorized Return/Reversal transactions. In addition, we noticed that settlement payment transactions remained in a Pending status instead of being updated to Low Balance if and when the Unauthorized Return caused a consumer's dedicated account to have insufficient funds for the said transaction(s). This refinement ensures that settlement payments are correctly matched on the Decisions page, avoiding accidental payments when funds within Forth Pay are insufficient.
The changes included backend coding and script updates, updates to existing queries to extend how far back we search for pending settlement transactions, and a new automatic trigger of a low balance payment to be visible in a settlement transaction.
Update CFT Integration to Retrieve Client Escalations
This new feature offers a real-time view of CFTPay escalation reasons directly from the Forth CRM dashboard, This requirement outlines the integration of the escalations API with CFT based on the provided API documentation. The aim is to efficiently retrieve and store escalation details and subsequently display these details on specific pages of the platform, including the Enrollment Details page and the Client Dashboard, to make informed decisions and act accordingly without switching between platforms.
Required Address Entry for Settlement Payments via Check
We performed an update to our system that streamlines your settlement payment process. With this update, the Forth system displays the mandatory address fields (address 1, city, state, and zip code) in the payment information section when the user selects a check, check overnight, or check 2nd day as the settlement payment method.
If any mandatory address fields (indicated via asterisk) are left incomplete, the system will prevent the settlement offer from being saved and will display an error, highlighting the field(s) that need attention.
To rectify this, the field in question will be highlighted with an exclamation mark indicating that it is necessary to fill in the field. When all mandatory address fields are filled out, the settlement offer will be saved with the entered address information. The system saves the now-completed address information with the settlement offer data for future reference and reporting purposes.
Benefits of this update include the elimination of the hassle of settlement payment checks being returned due to incomplete or missing address information, the accurate and timely receipt of settlement payments (boosting client satisfaction and trust), and the improvement of the efficiency and accuracy of the settlement payment process.
Update CREDITSCORE tag to Work with Xactus360
With this new feature, the Forth system has been updated to allow the {CREDITSCORE} tag used to render the credit score saved on a credit pull from the Xactus360 integration. This update enables proper tagging functionality to allow clients to populate the credit score on document, email, or SMS templates. If multiple scores are present, the highest score will be chosen.
API Updates (4)
Publish Contact Lists Endpoint
This new feature adds the ability to pull contact lists from the system. We published our lists endpoint so that clients can export a list of contacts by list ID and get the contacts they need for their relevant campaign. This enables the contact lists endpoint to be visible on the FORTH API documentation and enables service-type users to interact with this endpoint.
Multiple Schedules for a Specific Settlement Offer via API
This update was made as part of an overall Marketing Automation Project for our clients to help drive value.
This feature allows the retrieval of the Amortization Schedule, Settlement Schedule, and EPF Schedule for a specific settlement offer through the {{settlement_offers/{id}}} endpoint. This enhancement will provide a more comprehensive view of each settlement offer. This feature enhances the current endpoint to return additional schedule information for each settlement offer and improves the efficiency of our backend system by combining two endpoints into one. When a GET request is made, the server should respond with the appropriate schedules. API Documentation on this feature is available by clicking HERE.
Modify, Create, and Update Debt API Endpoints to Accept ECOA Values
This feature allows the passing of standardized ECOA codes to the Forth CRM API to create and update debts in the CRM. This modification to the “Create Debt Record” and the “Update Debt Record” endpoints will allow users to standardize the passing of fields between systems and reconcile and sync data between them. In addition, this feature will accept ECOA standardized values for debt ownership (i.e. Who’s Debt), as well as be able to create and update debts with the ECOA values. API Documentation on this feature is available by clicking HERE and HERE.
Add Permissions for Service Users Accessing API Endpoints
This new feature is another enhancement to your API management experience! This enhancement gives you granular control over which API endpoints your automations and integrations can access. These capabilities enable you to apply security best practices and limit how much data can be accessed by a specific party. This allows you to restrict access to API keys generated using various credentials sets, limiting what third parties using those keys have access to and further enhancing CRM security. In other words, you can control who can access what on the API. Benefits of this feature include the broadening of security capabilities around your API, restricting API keys to certain endpoints, and improving overall governance of API access by CRM users and administrators.
NOTE: This feature is available only for service user API keys
A dropdown menu can now select those credentials generated and tied to a service user. The listing of available API endpoints is grouped by their object type (advances, authorizations, calls, etc.), with checkboxes available to allow or block access (see example page below).
When an endpoint is enabled for a particular credential set, external services using that credential set may interact with the chosen endpoint. When disabled, the system returns an Invalid Access error, indicating that those credentials do not have proper access. API Documentation on this feature is available by clicking HERE.