Managing Client Portal email domains is now more streamlined. The Client Portal Domain configuration has been moved from Notifications Domain Configuration directly into the main Domain Configuration page under Dedicated Domain Setup.

This update also ensures that Client Portal emails can continue to be viewed directly within Conversations, while making domain management more centralized and intuitive.

✨ What's New

• Moved configuration from Notifications Domain Configuration to Domain Configuration.

• Client Portal emails can be viewed directly within Conversations.

• Centralized management for all email domain types in one place.

💡 Why It Matters

📩 Better communication visibility – customers can easily track Client Portal emails alongside other conversation history.

🧩 Centralized interactions – keep all customer communication accessible in one place.

🔍 Easier tracking – quickly reference Client Portal email activity as well.

🛠 How to Use

• Go to Email Services.
• Open Dedicated Domain Setup.
• Navigate to Domain Configuration.
• Configure the Client Portal Domain

The Company object just got a lot more useful. You can now reference Company fields – both standard and custom – across the platform as custom values: in emails, workflows, contracts, conversations, and AI context. All the rich business context you've been storing on Company records can now power personalized, automated communication.

✨ What's New

• Company fields in the Custom Value Picker — pick from standard fields and all your custom Company fields.
• Available across the platform: Workflows, Email Builder, Email Campaigns, Conversations, Documents & Contracts, Bulk Actions, and Conversation AI.
• Each custom value resolves to the Company associated with the Contact at runtime.

💡 Why It Matters

• 📩 Smarter personalization – reference a recipient's company name, industry, account tier, or any custom attribute directly in your messages.
• 📄 Auto-filled contracts – generate proposals and agreements with full Company context pre-populated.
• 🤖 Context-aware AI – Conversation AI can now use Company information in its replies.
• ⚙️ More powerful automations – drive workflows with Company data without workarounds.
• 🚀 More value from your Company data – every field you've set up on Company is now usable wherever you communicate.

🛠 How to Use

1. Open any supported tool (e.g., Conversations or a Workflow Send Email action).
2. Click the Custom Value Picker in the editor toolbar.
3. Select the Company group.
4. Pick any standard or custom Company field.

What’s new?

The Math Operation action is now supported in company-based workflows and custom object-based workflows. This expands the same calculation action already available in other workflows, so users can run math on numeric values tied to companies or custom objects.

How it works

When a company or custom object workflow reaches the Math Operation action, HighLevel calculates the selected values and stores the result for use later in the workflow. The action follows the same behavior as the existing Math Operation action.

How to use it

• Open a company-based or custom object-based workflow.
• Add the Math Operation action.
• Choose the values and operation, then use the result in the next workflow steps.

Why we built it

Users can now automate calculations directly in more workflow types without switching objects, adding manual steps, or relying on workarounds.

Simple example

• A construction business uses a custom object workflow to calculate the total project cost by adding material cost and labor cost stored on the project object.

Scope & edge cases

• Supported in company-based workflows.
• Supported in custom object-based workflows.
• Uses the same Math Operation behavior available in other workflow types.

What’s new?

The Math Operation action is now supported in company-based workflows and custom object-based workflows. This expands the same calculation action already available in other workflows, so users can run math on numeric values tied to companies or custom objects.

How it works

When a company or custom object workflow reaches the Math Operation action, HighLevel calculates the selected values and stores the result for use later in the workflow. The action follows the same behavior as the existing Math Operation action.

How to use it

• Open a company-based or custom object-based workflow.
• Add the Math Operation action.
• Choose the values and operation, then use the result in the next workflow steps.

Why we built it

Users can now automate calculations directly in more workflow types without switching objects, adding manual steps, or relying on workarounds.

Simple example

• A construction business uses a custom object workflow to calculate the total project cost by adding material cost and labor cost stored on the project object.

Scope & edge cases

• Supported in company-based workflows.
• Supported in custom object-based workflows.
• Uses the same Math Operation behavior available in other workflow types.

What’s new?

The Math Operation action is now supported in company-based workflows and custom object-based workflows. This expands the same calculation action already available in other workflows, so users can run math on numeric values tied to companies or custom objects.

How it works

When a company or custom object workflow reaches the Math Operation action, HighLevel calculates the selected values and stores the result for use later in the workflow. The action follows the same behavior as the existing Math Operation action.

How to use it

• Open a company-based or custom object-based workflow.
• Add the Math Operation action.
• Choose the values and operation, then use the result in the next workflow steps.

Why we built it

Users can now automate calculations directly in more workflow types without switching objects, adding manual steps, or relying on workarounds.

Simple example

• A construction business uses a custom object workflow to calculate the total project cost by adding material cost and labor cost stored on the project object.

Scope & edge cases

• Supported in company-based workflows.
• Supported in custom object-based workflows.
• Uses the same Math Operation behavior available in other workflow types.