Welcome to the February 2026 update! We’ve hit the ground running this year with a series of updates focused on automation precision, data security, and enhanced visibility. These improvements are designed to streamline your daily operations and provide a more intuitive experience across both the Forth CRM and Forth Pay platforms.
Automations and Triggers
Automate Post-Settlement Actions Upon Completion
You can now set triggers to fire the moment a final settlement payment clears. This allows your team to automate critical end-of-journey tasks - like sending congratulatory emails or generating final documents - the second a settlement is officially fully paid.
Trigger Events Based on Script Completion
Enhance your workflow continuity with the new "Contact Script Finish" event. Triggers can now be configured to fire specifically when a user clicks "Finish" in a script pop-up, allowing for seamless transitions to post-call automations or webhooks.
Enhanced Trigger Logic with Plan Status Visibility
The trigger condition dropdown now organizes enrollment plans by "Active," "Inactive," and "Shared Plans." This ensures your automations can accurately reference and evaluate plans regardless of their current status, providing greater flexibility for historical data and edge-case scenarios.
Greater Transparency in Contact History
To make troubleshooting a breeze, the system now records both the Trigger ID and Execution ID directly in the contact history. This allows users and support agents to trace automated actions back to their specific source with zero guesswork.
Data Management and User Experience
Self-Service Package Deletion for Support
We introduced a new utility that allows authorized users to delete document packages and their associated templates via CSV upload. This reduces the wait time for backend updates and gives your administrative teams more independence.
Self-Service Contact Recovery with the Recycling Bin
We introduced a Recycling Bin that stores deleted contacts for 30 days. It also tracks the "Deletion Source" (UI, API, or Bulk), giving your team the power to review and recover records independently without needing to contact support.
Streamlined Program Snapshots on the Dashboard
Agents can now see payment frequency and draft patterns (e.g., "Monthly – 15th") directly in the Program Snapshot. This eliminates the need to dig through payment schedules during live calls, significantly reducing call handling time.
Introducing the Consumer Loans File Type
Tailor your dashboard to your specific business model with the new "Consumer Loans" file type. This version removes business-centric fields while keeping all relevant loan and advance tabs, ensuring a clean and focused workspace for consumer lending.
Feature Flagging for AI Call Summaries
To support controlled testing of our upcoming BlueRock AI integration, we’ve placed AI-generated call summaries and transcripts behind a feature flag. This allows for seamless enablement and testing of automated call documentation within the contact record.
Compliance and Security
Detailed Clixsign Signing Certificates
We updated our signing certificates to include notification methods (SMS/Email), standardized timestamps, and sender time zone information. This provides a more robust audit trail for improved legal compliance and accuracy.
Flexible Certificate Download Options
Admins can now choose to download Clixsign-signed documents without the completion certificate attached. This saves time for teams who previously had to manually parse PDFs for creditors who reject documents containing third-party certificate pages.
New Dynamic Debt Type Tags
The new {DEBT_TYPE} tag allows you to dynamically insert the specific type of debt into your documents and emails. This ensures that communications sent to clients, attorneys, or credit bureaus are accurate and professional, especially when a contact has multiple different types of debt on file.
Enhanced ACH and API Security
In our ongoing commitment to security, we have updated ACH file security standards and migrated to the newest USPS API catalog. These updates ensure your data transfers and address verifications remain secure and uninterrupted by industry retirements.
Strict Webhook Access Controls
Webhook visibility now follows company hierarchy and explicit sharing rules. Users will only see, edit, or delete webhooks they created or those shared with their specific role, enhancing overall data security.
Financials and Integration
Recognizing Pending Escrow Closures for CFT
The system now accurately identifies CFT accounts in "Closure Initiated" status. Instead of incorrectly marking these as cancelled, Forth CRM displays a non-blocking informational banner, ensuring you stay aligned with the actual state of the escrow account.
Consolidated Accounting Reports
Gain a complete financial picture by including both Active and Inactive transactions in a single Accounting Report. This eliminates the need to run multiple reports to track down every applicable fee or payment, ensuring no revenue is left on the table.
Financial Parity with CFT "Adjust" Transactions
Forth CRM now supports and syncs "Adjust" transaction types from CFT. This ensures that balance corrections made at the gateway level are automatically reflected in your CRM and accounting reports for total financial accuracy.
Rebalancing for Negative Balance Accounts
The Rebalancer tool now functions even when a consumer has a negative balance. This allows you to reschedule skipped fees to future dates when funds are available, ensuring you can still collect earned performance fees as soon as the client's balance recovers.
One-Click Amortization Exports
Negotiators can now export the amortization schedule directly from the Settlement Offer screen to a CSV file. This allows for quick external calculations and data sharing without manual entry.
Improved Tag Accuracy for All Gateways
We’ve refined our dynamic tags:
- {LASTTRANS_DATE} now works accurately for "Other" gateway types.
- {LOWBAL_SETTLEMENT} now correctly identifies settlement payments in "Low Balance" status.
- Logic fixes ensure these tags only populate for the correct transaction types.
Automated OCR Data Capture for FCNA
The automatch job now captures OCR information (Creditor, Consumer, and Trace numbers) and saves it directly to the settlement table, further automating the reconciliation process for FCNA users.
Required Payee Fields for Direct Pay
To prevent processing errors, the "Payee" field is now a required field for all direct pay settlement transactions. This ensures all necessary data is captured before a payment is initiated.
To access other monthly release notes, click Here.