Company Fields as Custom Values

TL;DR

HighLevel now allows using standard and custom company fields as custom values. This provides dynamic information for communications. This is a standard update, not requiring immediate agency action.

Who this affects

HighLevel has not confirmed who is affected by this update.

What changed

Standard and custom company fields can now be used as custom values. Company details can be linked to contacts. Merge fields dynamically populate company information across emails, workflows, contracts, and Conversation AI. The handling of missing company data during messaging is demonstrated. Company fields can be configured. Company custom values can be inserted into email templates and conversations. HighLevel has not confirmed any limits or plan gating. HighLevel has not confirmed the rollout status.

Where to find it

HighLevel has not published the location yet. Based on the functionality, this feature will likely reside within sub-account settings or custom field configuration areas, accessible when setting up templates or workflows that utilize custom values.

How agencies will use this

Agencies can leverage this to personalize communications at scale. For example, an agency managing clients could configure a custom company field named 'Account Manager Name' within each client's company profile. This field, once populated, can then be used as a custom value in email templates for onboarding. When sending a welcome email to a new contact at Company A, the merge field {{company.Account Manager Name}} would automatically insert the name of Company A's assigned account manager, ensuring consistent and personalized outreach without manual editing. This extends to contracts, where company-specific terms or details could be dynamically inserted, or even within Conversation AI to provide company-specific answers.

Our take

This is a standard update. It provides useful functionality for agencies looking to further personalize communications and automate data insertion. There is no immediate need to drop everything and implement this. It's a quality-of-life improvement for structured data use. HighLevel has not confirmed if this replaces or breaks existing functionality.