Summary:
- New fields let sales staff record consultancy fees, payment plans, installment amounts and dates, and any payments already received directly on a lead.
- The system automatically calculates the remaining balance based on the total fee and payments made.
- Dates entered in various formats are normalized, ensuring consistent storage and display on contracts.
- When generating a BoldSign contract, the captured payment details are automatically pre‑filled, reducing manual entry and errors.
- A simple “Installments” vs “Paid in full” option guides which installment fields are shown, streamlining the user interface.
- The contract entry form layout has been adjusted so amount and due‑date fields share a single row for clearer presentation.
Changelog:
Added:
- Fields for consultancy fee, payment plan, installment amounts and dates, prior payments, and remaining balance.
- Dropdown list for selecting payment plan (Installments or Paid in full).
- Automatic calculation of remaining balance.
- Date‑normalization logic to handle different input formats.
- UI layout that groups amount and due‑date fields together for better readability.
- Logic to pre‑fill BoldSign contracts with the new payment details.
Changed:
- Integration of the new fields into the contract pre‑fill process.
- Updated contract‑sending workflow to store the new consultancy payment information.
- Adjusted form behavior to hide irrelevant installment fields based on the selected payment plan.
Fixed:
- Ensured that only relevant payment fields are sent for contracts, preventing incorrect data from being saved.
Summary:
- The system now automatically copies the lead’s business name into the second company name field on BoldSign documents.
- This eliminates the need for users to manually enter the same information twice.
- Reduces the risk of mismatched or missing company names across generated contracts.
- Streamlines the document preparation workflow, saving time for sales and operations teams.
Changelog:
Added:
- Mapping that links the lead’s business name to the second company name field in BoldSign.
Changed:
- Prefill process now includes the second company name when populating documents.
Fixed:
-
Removed:
-
Summary:
- The login process now clearly separates admin and lead authentication, making it easier to understand which path a user follows.
- Session creation records activity in a central log, improving auditability and security monitoring.
- Validation of email, phone numbers and referral codes has been tightened, providing more accurate error messages for users.
- Unnecessary helper functions and legacy CRM calls have been eliminated, reducing maintenance overhead and potential points of failure.
- Error handling across the authentication flow is now consistent, ensuring that failures are reported uniformly.
Changelog:
Added:
- Clear distinction between admin‑type and lead‑type login handling.
- Centralized session‑log recording when a token is issued.
- Standardized validation steps for email, phone numbers and referral codes.
Changed:
- Authentication flow logic reorganized for better readability and maintainability.
- Error responses now use uniform messaging and status codes throughout the service.
- Token generation now includes explicit marking of impersonated sessions.
Fixed:
- Incorrect or ambiguous error messages for invalid email, duplicate registrations, and unsupported virtual phone numbers.
- Scenarios where missing partner referral data caused silent failures have been addressed.
Removed:
- Several unused utility functions and legacy CRM interaction code that were no longer needed.
- Redundant console debugging statements that cluttered logs.
Summary:
- Legal page links are now managed centrally, making future updates easier and more reliable.
- The logo in the header now directs users to the main homepage instead of a sub‑page.
- A clear disclaimer is displayed with loan offers, providing users with important legal and financial information.
- Offer cards now show detailed loan information (amount, payment, term, etc.) in a more readable format.
- Users can accept, decline, or continue to an external lender site with confirmation prompts, improving decision control.
- Real‑time updates keep the offer status current without needing a page refresh.
- Loading placeholders and refined formatting give a smoother, faster‑feeling experience.
- Unused code and constants have been cleaned up to keep the application tidy.
Changelog:
Added:
- Centralized constants for privacy policy and terms URLs.
- Comprehensive disclaimer text on the loan offer page.
- New, richer offer card design with detailed loan metrics.
- Buttons for accepting, declining, and continuing to external lender offers, each with user confirmations.
- Real‑time socket integration to instantly reflect offer status changes.
- Loading skeleton component to improve perceived performance while data loads.
- Visual icon for external links to clarify when users will leave the site.
- Integration with user data store for personalized experience.
Changed:
- Footer links now reference the centralized URL constants instead of hard‑coded strings.
- Header logo link updated to point to the main website URL.
- Offer wall now includes additional information fields (e.g., external offer URLs, timestamps) and uses improved number formatting.
- Layout and styling adjustments enhance responsiveness across devices.
Fixed:
- Added validation to ensure external URLs are correctly formatted before navigation, preventing broken links.
- Removed outdated stage handling logic that was no longer used.
Removed:
- Hard‑coded privacy policy and terms URLs from the footer.
- Unused stage constants and related copy text from the offer wall component.
Summary:
- Email sending now records which service (SendGrid or Nodemailer) was used, giving a clear audit trail.
- The system can send emails via either SendGrid or Nodemailer, providing more flexibility and redundancy.
- Lendflow integration automatically selects the correct production or sandbox endpoint and can use a pre‑provided access token, reducing configuration errors.
- New capabilities let users list Lendflow applications and add notes directly, improving visibility and communication.
- Generated sandbox phone numbers are now guaranteed to be dialable, making test data more realistic.
- Application processing automatically advances stages and schedules follow‑up actions, speeding up the loan workflow.
- Enhanced logging and error handling capture issues without disrupting users.
Changelog:
Added:
- Tracking of the email service provider in send‑email responses.
- Support for both SendGrid and Nodemailer as email providers.
- Utility to generate valid US sandbox phone numbers, with accompanying tests.
- Functions to read stage names, borrower details, and application rows from Lendflow data.
- Ability to list Lendflow applications and create application notes.
- In‑memory lock to prevent duplicate stage‑advancement actions.
- Logging of delivery‑scheduling failures.
Changed:
- Email response now includes the provider field.
- Lendflow client now chooses the correct API URL based on environment and accepts a configured access token.
- Application creation flow now records SMS consent and schedules a delivery sequence.
- Phone number generation in Lendflow data now uses the sandboxPhone utility for valid numbers.
- Offer handling now captures continue URLs from multiple possible fields.
Fixed:
- Corrected production URL selection for Lendflow.
- Prevented invalid sandbox phone numbers.
- Avoided duplicate stage‑advancement calls during processing.
Removed:
- No functional components were removed.
Summary:
- The lead information sent to GoHighLevel now includes the Redtrack click identifier.
- This identifier is tracked for changes, ensuring updates are captured automatically.
- Marketing teams can now match leads to the exact ad click that generated them, improving attribution accuracy.
- Enhanced data completeness supports better reporting and ROI analysis for campaigns.
Changelog:
Added:
- Redtrack click ID field to the data sent to the external webhook.
Changed:
- Included the Redtrack click ID in the list of fields monitored for changes.
Fixed:
-
Removed:
-
Summary:
- When a user’s redtrack click ID is recorded, the same ID is now also stored on the related lead profile.
- This creates a direct link between leads and the original marketing click, improving attribution and reporting.
- The update runs only if a lead identifier exists, so it does not affect users without associated leads.
- Any failure while saving the ID to the lead profile is caught and logged, preventing the operation from disrupting other processes.
- Overall data completeness is enhanced, giving the business clearer insight into campaign performance.
Changelog:
Added:
- Automatic saving of redtrack click ID to lead profiles.
- Error handling that logs failures during the lead update.
Changed:
- The redtrack click ID saving routine now includes lead profile synchronization.
Fixed:
- Prevented potential crashes by catching and logging errors when updating lead data.
Removed:
- (none)
Summary:
- Introduces a new optional attribute for storing a RedTrack click identifier with each user.
- Enables the system to capture and retain marketing click data for better campaign attribution.
- Supports more detailed analytics without affecting existing user information.
- The field is optional, so current users and processes remain unchanged.
- Lays groundwork for future features that rely on click‑tracking data.
Changelog:
Added:
- Optional RedTrack click ID attribute to the user data model.
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- Introduces a new field for storing Redtrack click identifiers on lead records.
- Makes the Redtrack Click ID visible and editable within the lead entry form.
- Allows the value to be imported from external sources and included in reports.
- Supports better tracking of marketing campaign performance by linking leads to specific click events.
Changelog:
Added:
- New Redtrack Click ID field definition for leads.
- User‑facing label for the Redtrack Click ID.
- Capability to capture, store, and report on the click ID data.
Changed:
-
Fixed:
-
Removed:
-
Summary:
- Users can now request a login link sent to their email, allowing them to sign in without remembering a password.
- After clicking the emailed link, the system automatically validates it, creates a secure session token, and redirects the user to the appropriate dashboard or onboarding flow.
- The login flow includes clear loading indicators and concise error messages, improving the overall sign‑in experience.
- The existing email OTP verification page has been refactored to use a shared component, reducing duplicated code and simplifying future updates.
- Old, complex OTP handling code and related UI elements have been removed, making the codebase cleaner and easier to maintain.
Changelog:
Added:
- A new email‑based “send me a login link” page.
- A page that processes the magic link, sets a secure authentication token, and redirects users.
- Reusable UI components for displaying loading states, notes, and error messages in the new flow.
Changed:
- The email OTP verification page now leverages the new shared component instead of containing its own extensive logic.
Fixed:
- Improved handling of errors and loading states during both login‑link request and magic‑link consumption.
Removed:
- The previous large inline implementation of email OTP verification, including timers, duplicate cookie handling, and related imports.
Summary:
- The system now records a marketing click identifier during sign‑up and login, enabling accurate attribution of user acquisition campaigns.
- A new “onboarding source” field is captured and stored, allowing the business to distinguish between different lead entry points (Apply V2 and Lendflow) and report on their performance.
- The magic‑link login flow has been extended to carry the onboarding source, ensuring downstream processes have the correct context.
- Integration with the Lendflow platform has been added, providing the ability to create and manage loan applications directly from the product.
- Validation rules have been updated to accept the new click‑tracking and onboarding data, preventing errors when this information is supplied.
- Lead records are now automatically updated with onboarding status and source information, improving data quality for sales and reporting teams.
- Overall, these changes enhance tracking, reporting, and the ability to process loan applications without manual intervention.
Changelog:
Added:
- Capture and storage of a marketing click identifier for each user.
- New onboarding source handling that supports both Apply V2 and Lendflow entry points.
- Full Lendflow API client and controller to create, retrieve, and advance loan applications.
- Validation support for the new click‑tracking and onboarding fields.
- Logic to automatically update lead profiles with onboarding status and source.
Changed:
- Authentication and Google login flows now include the click identifier and onboarding source in their processing.
- Magic‑link consumption now returns the onboarding source alongside existing data.
- Lead‑signup completion checks now recognize Lendflow as a valid onboarding source.
Fixed:
- Corrected onboarding source detection to work for both Apply V2 and Lendflow entries.
- Ensured onboarding completion flags are set appropriately when the source changes.
Removed:
- (none)
Releaseddc763-repo/dc_crm
#4924 ProductionBilal Alam
Change Overview
Summary:
- New fields let sales staff record consultancy fees, payment plans, installment amounts and dates, and any payments already received directly on a lead.
- The system automatically calculates the remaining balance based on the total fee and payments made.
- Dates entered in various formats are normalized, ensuring consistent storage and display on contracts.
- When generating a BoldSign contract, the captured payment details are automatically pre‑filled, reducing manual entry and errors.
- A simple “Installments” vs “Paid in full” option guides which installment fields are shown, streamlining the user interface.
- The contract entry form layout has been adjusted so amount and due‑date fields share a single row for clearer presentation.
Changelog:
Added:
- Fields for consultancy fee, payment plan, installment amounts and dates, prior payments, and remaining balance.
- Dropdown list for selecting payment plan (Installments or Paid in full).
- Automatic calculation of remaining balance.
- Date‑normalization logic to handle different input formats.
- UI layout that groups amount and due‑date fields together for better readability.
- Logic to pre‑fill BoldSign contracts with the new payment details.
Changed:
- Integration of the new fields into the contract pre‑fill process.
- Updated contract‑sending workflow to store the new consultancy payment information.
- Adjusted form behavior to hide irrelevant installment fields based on the selected payment plan.
Fixed:
- Ensured that only relevant payment fields are sent for contracts, preventing incorrect data from being saved.
Releaseddc763-repo/dc_crm
#4922 ProductionBilal Alam
Change Overview
Summary:
- The system now automatically copies the lead’s business name into the second company name field on BoldSign documents.
- This eliminates the need for users to manually enter the same information twice.
- Reduces the risk of mismatched or missing company names across generated contracts.
- Streamlines the document preparation workflow, saving time for sales and operations teams.
Changelog:
Added:
- Mapping that links the lead’s business name to the second company name field in BoldSign.
Changed:
- Prefill process now includes the second company name when populating documents.
Fixed:
-
Removed:
-
Releaseddc763-repo/dc_crm
#4918 ProductionBilal Alam
Change Overview
Summary:
- Introduces a new field for storing Redtrack click identifiers on lead records.
- Makes the Redtrack Click ID visible and editable within the lead entry form.
- Allows the value to be imported from external sources and included in reports.
- Supports better tracking of marketing campaign performance by linking leads to specific click events.
Changelog:
Added:
- New Redtrack Click ID field definition for leads.
- User‑facing label for the Redtrack Click ID.
- Capability to capture, store, and report on the click ID data.
Changed:
-
Fixed:
-
Removed:
-
Releaseddc763-repo/dc_crm
#4920 ProductionBilal Alam
Change Overview
Summary:
- The lead information sent to GoHighLevel now includes the Redtrack click identifier.
- This identifier is tracked for changes, ensuring updates are captured automatically.
- Marketing teams can now match leads to the exact ad click that generated them, improving attribution accuracy.
- Enhanced data completeness supports better reporting and ROI analysis for campaigns.
Changelog:
Added:
- Redtrack click ID field to the data sent to the external webhook.
Changed:
- Included the Redtrack click ID in the list of fields monitored for changes.
Fixed:
-
Removed:
-
Summary:
- The login process now clearly separates admin and lead authentication, making it easier to understand which path a user follows.
- Session creation records activity in a central log, improving auditability and security monitoring.
- Validation of email, phone numbers and referral codes has been tightened, providing more accurate error messages for users.
- Unnecessary helper functions and legacy CRM calls have been eliminated, reducing maintenance overhead and potential points of failure.
- Error handling across the authentication flow is now consistent, ensuring that failures are reported uniformly.
Changelog:
Added:
- Clear distinction between admin‑type and lead‑type login handling.
- Centralized session‑log recording when a token is issued.
- Standardized validation steps for email, phone numbers and referral codes.
Changed:
- Authentication flow logic reorganized for better readability and maintainability.
- Error responses now use uniform messaging and status codes throughout the service.
- Token generation now includes explicit marking of impersonated sessions.
Fixed:
- Incorrect or ambiguous error messages for invalid email, duplicate registrations, and unsupported virtual phone numbers.
- Scenarios where missing partner referral data caused silent failures have been addressed.
Removed:
- Several unused utility functions and legacy CRM interaction code that were no longer needed.
- Redundant console debugging statements that cluttered logs.
Summary:
- Email sending now records which service (SendGrid or Nodemailer) was used, giving a clear audit trail.
- The system can send emails via either SendGrid or Nodemailer, providing more flexibility and redundancy.
- Lendflow integration automatically selects the correct production or sandbox endpoint and can use a pre‑provided access token, reducing configuration errors.
- New capabilities let users list Lendflow applications and add notes directly, improving visibility and communication.
- Generated sandbox phone numbers are now guaranteed to be dialable, making test data more realistic.
- Application processing automatically advances stages and schedules follow‑up actions, speeding up the loan workflow.
- Enhanced logging and error handling capture issues without disrupting users.
Changelog:
Added:
- Tracking of the email service provider in send‑email responses.
- Support for both SendGrid and Nodemailer as email providers.
- Utility to generate valid US sandbox phone numbers, with accompanying tests.
- Functions to read stage names, borrower details, and application rows from Lendflow data.
- Ability to list Lendflow applications and create application notes.
- In‑memory lock to prevent duplicate stage‑advancement actions.
- Logging of delivery‑scheduling failures.
Changed:
- Email response now includes the provider field.
- Lendflow client now chooses the correct API URL based on environment and accepts a configured access token.
- Application creation flow now records SMS consent and schedules a delivery sequence.
- Phone number generation in Lendflow data now uses the sandboxPhone utility for valid numbers.
- Offer handling now captures continue URLs from multiple possible fields.
Fixed:
- Corrected production URL selection for Lendflow.
- Prevented invalid sandbox phone numbers.
- Avoided duplicate stage‑advancement calls during processing.
Removed:
- No functional components were removed.
Summary:
- When a user’s redtrack click ID is recorded, the same ID is now also stored on the related lead profile.
- This creates a direct link between leads and the original marketing click, improving attribution and reporting.
- The update runs only if a lead identifier exists, so it does not affect users without associated leads.
- Any failure while saving the ID to the lead profile is caught and logged, preventing the operation from disrupting other processes.
- Overall data completeness is enhanced, giving the business clearer insight into campaign performance.
Changelog:
Added:
- Automatic saving of redtrack click ID to lead profiles.
- Error handling that logs failures during the lead update.
Changed:
- The redtrack click ID saving routine now includes lead profile synchronization.
Fixed:
- Prevented potential crashes by catching and logging errors when updating lead data.
Removed:
- (none)
Summary:
- The system now records a marketing click identifier during sign‑up and login, enabling accurate attribution of user acquisition campaigns.
- A new “onboarding source” field is captured and stored, allowing the business to distinguish between different lead entry points (Apply V2 and Lendflow) and report on their performance.
- The magic‑link login flow has been extended to carry the onboarding source, ensuring downstream processes have the correct context.
- Integration with the Lendflow platform has been added, providing the ability to create and manage loan applications directly from the product.
- Validation rules have been updated to accept the new click‑tracking and onboarding data, preventing errors when this information is supplied.
- Lead records are now automatically updated with onboarding status and source information, improving data quality for sales and reporting teams.
- Overall, these changes enhance tracking, reporting, and the ability to process loan applications without manual intervention.
Changelog:
Added:
- Capture and storage of a marketing click identifier for each user.
- New onboarding source handling that supports both Apply V2 and Lendflow entry points.
- Full Lendflow API client and controller to create, retrieve, and advance loan applications.
- Validation support for the new click‑tracking and onboarding fields.
- Logic to automatically update lead profiles with onboarding status and source.
Changed:
- Authentication and Google login flows now include the click identifier and onboarding source in their processing.
- Magic‑link consumption now returns the onboarding source alongside existing data.
- Lead‑signup completion checks now recognize Lendflow as a valid onboarding source.
Fixed:
- Corrected onboarding source detection to work for both Apply V2 and Lendflow entries.
- Ensured onboarding completion flags are set appropriately when the source changes.
Removed:
- (none)
Summary:
- Legal page links are now managed centrally, making future updates easier and more reliable.
- The logo in the header now directs users to the main homepage instead of a sub‑page.
- A clear disclaimer is displayed with loan offers, providing users with important legal and financial information.
- Offer cards now show detailed loan information (amount, payment, term, etc.) in a more readable format.
- Users can accept, decline, or continue to an external lender site with confirmation prompts, improving decision control.
- Real‑time updates keep the offer status current without needing a page refresh.
- Loading placeholders and refined formatting give a smoother, faster‑feeling experience.
- Unused code and constants have been cleaned up to keep the application tidy.
Changelog:
Added:
- Centralized constants for privacy policy and terms URLs.
- Comprehensive disclaimer text on the loan offer page.
- New, richer offer card design with detailed loan metrics.
- Buttons for accepting, declining, and continuing to external lender offers, each with user confirmations.
- Real‑time socket integration to instantly reflect offer status changes.
- Loading skeleton component to improve perceived performance while data loads.
- Visual icon for external links to clarify when users will leave the site.
- Integration with user data store for personalized experience.
Changed:
- Footer links now reference the centralized URL constants instead of hard‑coded strings.
- Header logo link updated to point to the main website URL.
- Offer wall now includes additional information fields (e.g., external offer URLs, timestamps) and uses improved number formatting.
- Layout and styling adjustments enhance responsiveness across devices.
Fixed:
- Added validation to ensure external URLs are correctly formatted before navigation, preventing broken links.
- Removed outdated stage handling logic that was no longer used.
Removed:
- Hard‑coded privacy policy and terms URLs from the footer.
- Unused stage constants and related copy text from the offer wall component.
Summary:
- Introduces a new optional attribute for storing a RedTrack click identifier with each user.
- Enables the system to capture and retain marketing click data for better campaign attribution.
- Supports more detailed analytics without affecting existing user information.
- The field is optional, so current users and processes remain unchanged.
- Lays groundwork for future features that rely on click‑tracking data.
Changelog:
Added:
- Optional RedTrack click ID attribute to the user data model.
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- Users can now request a login link sent to their email, allowing them to sign in without remembering a password.
- After clicking the emailed link, the system automatically validates it, creates a secure session token, and redirects the user to the appropriate dashboard or onboarding flow.
- The login flow includes clear loading indicators and concise error messages, improving the overall sign‑in experience.
- The existing email OTP verification page has been refactored to use a shared component, reducing duplicated code and simplifying future updates.
- Old, complex OTP handling code and related UI elements have been removed, making the codebase cleaner and easier to maintain.
Changelog:
Added:
- A new email‑based “send me a login link” page.
- A page that processes the magic link, sets a secure authentication token, and redirects users.
- Reusable UI components for displaying loading states, notes, and error messages in the new flow.
Changed:
- The email OTP verification page now leverages the new shared component instead of containing its own extensive logic.
Fixed:
- Improved handling of errors and loading states during both login‑link request and magic‑link consumption.
Removed:
- The previous large inline implementation of email OTP verification, including timers, duplicate cookie handling, and related imports.