The Spent field is one of the most valuable pieces of customer data in HighLevel, but currently it can only be viewed on a contact record in Payments. It cannot be used anywhere else in the platform.

🚨 Requested Enhancement

Please make the Spent field available as a standard field that can be used throughout HighLevel, including:

🔹Workflow triggers and conditions

🔹Smart Lists and contact filters

🔹If/Else branches in workflows

🔹Segments and audiences

🔹Bulk actions

🔹Reporting and dashboards

🔹Custom Values and merge fields (where appropriate)

🔹Opportunities and automation logic

🚨 Why This Matters

A customer's lifetime spend is one of the most important metrics for automation and customer segmentation. Without access to this field, agencies and businesses cannot build automations around their highest-value customers without maintaining separate custom fields and complicated workflows.

Examples include:

🔹Automatically move VIP customers into exclusive nurture campaigns after they spend $1,000.

🔹Trigger loyalty rewards once a customer reaches a spending threshold.

🔹Send thank-you gifts to customers after lifetime purchases exceed a certain amount.

🔹Identify high-value clients for account managers.

🔹Filter contacts by lifetime value for marketing campaigns.

🔹Create reports based on customer spending tiers.

🔹Build renewal or upsell automations for top customers.

🚨 Current Workaround

The only workaround is to maintain a separate custom field and update it manually or through complex workflows, even though HighLevel already calculates and displays the total. This creates duplicate data, unnecessary workflow complexity, and opportunities for data inconsistencies.

🚨 Benefits

Making the Spent field accessible across the platform would:

🔹Reduce unnecessary workflows

🔹Improve automation capabilities

🔹Eliminate duplicate data

🔹Enable true customer lifetime value segmentation

🔹Help agencies create more sophisticated marketing and retention campaigns

🔹Leverage data HighLevel is already calculating

👀 Since HighLevel already stores and displays this value, exposing it to workflows, filters, and reporting would provide tremendous value with minimal additional complexity.