A new Loan Channel dropdown is available in the Transaction Creation popup - select the channel that best describes how the loan was originated (e.g. Banked - Retail, Banked - Wholesale, Brokered, Correspondent).

The selected Loan Channel is saved with the transaction and appears immediately under the Transactions section of the contact's individual profile page - no extra steps needed.

Loan Channel can also be updated when editing an existing transaction, keeping your records accurate over time.

The stored Loan Channel value opens the door for future filtering and reporting - making it easier to analyze performance by origination source.

The addition is fully integrated into the existing transaction workflow - nothing about the current experience has changed, just extended.

Loan Channel is now available as an End Condition in the Automation builder - select the channel value that should bring the automation to a halt.

When a contact's associated transaction matches the defined Loan Channel, the automation stops immediately for that specific contact.

The system checks the contact's transaction records automatically - no extra tagging or manual setup required on your end.

The Loan Channel field is now available in the Transaction Import flow at the Company level - include it as a column in your CSV or Excel file before uploading.

During import, map the Loan Channel column to the corresponding field - the values are saved and linked directly to each transaction and its associated contact or company profile.

Imported Loan Channel values are immediately available as Automation End Conditions - so your workflows can act on them right away without any extra setup.

Fully compatible with your existing import and automation configurations -  no changes to your current process, just one more powerful field to work with.

Full Control Over TBD Stages

Company Admins can independently activate or deactivate each default TBD stage—ensuring only relevant stages are used.

Create Custom TBD Stages

Build new stages tailored to your company’s workflow. These stages are instantly available across the TBD pipeline for all users.

Real-Time Pipeline Reflection

Any changes made by Admins are immediately reflected in the pipeline—keeping everyone aligned with the latest process.

Seamless Stage Assignment

Users can easily assign any active stage to a lead directly within the TBD pipeline, maintaining clear and consistent lead movement.

Individual Stage Control
Toggle each default Lead Stage active or inactive based on your company’s needs.

Custom Stage Creation
Create Lead Stages tailored to your qualification and sales process.

Instant Updates Across Teams
Changes are reflected immediately—no need for manual communication or updates.

Cleaner, Focused Pipeline
Users only see the stages enabled by the admin, reducing clutter and confusion.

Easy Stage Assignment
Assign any active stage to a lead directly within the Leads Pipeline.

Seamless Experience with Custom Stages
Newly created stages appear naturally alongside default stages—ensuring a consistent workflow.

Previously, there was a single toggle to activate or deactivate all lead sources at once. Now, each lead source has its own individual toggle — so you can activate only what's relevant to your team and deactivate the rest.

Company Admins can now create custom lead sources that reflect your company's unique acquisition channels — think referral programs, events, partnerships, and more.

Any active lead source — default or custom — instantly appears in the contact creation form for all your users, keeping everyone aligned from the moment a lead is added.

With cleaner, company-specific options at the point of entry, your team can categorize new leads more accurately — making your pipeline data more meaningful from day one.

Easily mark contacts as No Sale directly within the TBD pipeline to clearly define non-converted opportunities.

Users are prompted to provide a reason when selecting No Sale, ensuring every outcome is backed by meaningful context.

The No Sale status and its reason are reflected within the transaction creation popup, maintaining continuity across workflows.

Previously marked No Sale contacts will display their status and reason in future interactions—enabling smarter, more informed decision-making.

The existing Default KPIs list is removed and replaced with two sections:

KPIs such as Prequalified and Pre-Approved are removed from the activity recorder and handled via auto-logging based on TBD stage changes.

System-triggered KPIs implementation:

UI updates:

Clear KPI Segmentation- Separate B2C and B2B sections simplify performance tracking.

Real-Time Updates - KPI counts are updated instantly as actions occur.

Enhanced User Experience - Cleaner UI with better grouping improves usability.

Enhanced Visibility
Key activities like Prequalified, Pre-Approved, and new contacts are tracked seamlessly without missing data.

A toggle (Active/Inactive) is added to the Interest Rates configuration.

When the toggle is set to Active, the system evaluates the defined interest rate criteria during processing.

If the criteria are met, opportunities are created accordingly.

When the toggle is set to Inactive, the system skips interest rate-based evaluation and prevents opportunity creation based on those criteria.

The toggle state is stored at the configuration level and respected during CRON or real-time execution.

Proper validation ensures that only valid and active configurations are considered during execution.

Logging is implemented to track whether the toggle was active or inactive during processing.

Better Control: Easily enable or disable interest rate-based automation without removing configurations.

Flexibility: Allows temporary suspension of logic without impacting existing data.

Reduced Errors: Prevents unintended opportunity creation when not required.

Operational Efficiency: Eliminates the need for manual intervention or configuration changes.

Improved Monitoring: Helps track and manage system behavior based on toggle state.

The trigger listens for any changes made to the Lead Stage field of a contact in the pipeline.

It is executed only when there is a valid stage transition (i.e., from one stage to another).

The system validates all configured conditions associated with the automation before execution.

If the conditions are satisfied, the configured actions (e.g., sending emails, updating fields, assigning tasks) are triggered.

The trigger works at the CRM level and respects user permissions and visibility settings.

Duplicate or redundant executions are avoided by ensuring the trigger runs only on actual changes to the lead stage.

Improved Efficiency: Automates actions based on lead stage changes, reducing manual effort.

Better Lead Management: Ensures timely follow-ups and actions as leads progress through stages.

Consistency: Standardizes workflows across the pipeline, minimizing human errors.

Real-Time Updates: Instantly triggers actions when stage changes occur.

Enhanced Productivity: Allows users to focus on high-value tasks while routine processes are automated.

The trigger listens for the creation of a new transaction in the system.

It is executed when the Transaction Date Added field is set or updated during transaction creation.

The system validates all configured automation conditions before execution.

If the conditions are satisfied, the configured actions (e.g., sending emails, updating fields, assigning tasks) are triggered.

The trigger works at the CRM level and respects user roles and permissions.

The automation is executed only once per transaction creation to avoid duplicate triggers.

Automated Workflows: Reduces manual intervention when new transactions are added.

Timely Actions: Ensures immediate follow-ups or notifications upon transaction creation.

Improved Tracking: Helps in monitoring new transactions efficiently.

Consistency: Ensures standardized actions for every new transaction.

Increased Productivity: Saves time by automating repetitive tasks.

The trigger listens for changes to the TBD Stage field of a transaction.

It is executed only when there is a valid stage transition (i.e., from one stage to another).

The system validates all configured automation conditions before execution.

If the conditions are satisfied, the configured actions (e.g., sending emails, updating fields, assigning tasks) are triggered.

The trigger works at the CRM level and respects user roles and permissions.

Duplicate executions are prevented by ensuring the trigger runs only on actual stage changes.

Automated Stage-Based Actions: Triggers workflows automatically when transaction stages change.

Improved Process Tracking: Keeps users informed and actions aligned with transaction progress.

Consistency: Ensures standardized processes across all transaction stages.

Time-Saving: Reduces manual follow-ups and repetitive tasks.

Enhanced Productivity: Allows users to focus on critical tasks while automation handles routine updates.