Payments

Allow Custom Email Messages When Sending Estimates
One feature that would significantly improve the Estimates module is the ability to customize the email message before sending an estimate. Currently, when sending an estimate, users can choose the recipient and delivery method, but there is no option to personalize the email. This forces agencies and businesses to send a separate email before or after the estimate, creating unnecessary steps and a less professional client experience. A simple email editor within the Send Estimate dialog would allow users to: Customize the email subject line Write a personalized message to the client Explain the proposal or estimate Highlight special pricing or promotional offers Set expectations for next steps Build stronger client relationships through personalized communication Many proposals require context before a client reviews pricing. Being able to introduce the estimate with a professional message would create a much better sales experience while eliminating the need to switch between email platforms. Suggested Features: Editable Subject Line Rich Text Email Body Save as Default Template Create Multiple Email Templates (Proposal, Follow-Up, Reminder, etc.) Personalize using Custom Values (Contact Name, Business Name, Estimate Amount, etc.) Option to Preview the Email Before Sending This enhancement would streamline the sales process for agencies and businesses while making HighLevel's Estimates feature a more complete proposal solution.
0
·
Enhancement
💸 The "Spent" Field Is Trapped! Free It for Workflows, Filters & More
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.
0
·
Enhancement
Add Per-Product Tax Toggle with Bulk Edit Support
Currently, there is no way to disable tax collection on individual products. If a user has global automatic tax settings enabled, those settings apply universally to all products with no option to disable taxes at the product level. This becomes a significant pain point for users who sell a mix of taxable and non-taxable products. For example, a user selling physical books (taxable) and digital memberships (non-taxable) has no streamlined way to exempt certain products from tax collection. If that user has 50 or 100+ products, this gap in functionality creates a major workflow problem. Proposed Solution: Per-product tax toggle: Add a simple enable/disable toggle on each product that overrides the global tax settings. When toggled off, no sales tax is collected on that product regardless of the customer's location. When toggled on, the global automatic tax rules apply as normal. Bulk edit support for tax toggle: Include this new tax toggle as an available field in the bulk edit menu. Users should be able to select multiple products at once and update the tax setting across all of them in a single action. No more tedious one by one updates. Why this Matters: Reduces support tickets from users confused about how to exempt specific products from tax Saves users significant time, especially those with large product catalogs The bulk edit piece is critical here. Without it, users with large catalogs are currently still stuck updating products one by one, which defeats the purpose of the feature. Additional Note: Please also consider adding a "select all" or multi-select option in the bulk edit menu. Right now, users must select products individually before applying bulk changes, which limits the usefulness of bulk editing for large catalogs.
0
·
Enhancement
Load More