GoHighLevel Custom Values and Merge Fields for Contractors: Full Setup Guide

GoHighLevel custom values and merge fields for contractors are the tools that turn generic automated messages into personalized outreach that actually gets responses. Most contractors who set up GoHighLevel start with basic automation sequences but quickly run into a problem: the messages feel robotic and generic. A follow-up text that says "Hi, following up on your inquiry" performs far worse than one that says "Hi Mike, following up on the kitchen remodel you asked about last Tuesday at your Plano home." The second version reads like a human wrote it specifically for that contact. Custom values and merge fields in GoHighLevel are what make the second version possible at scale.

This guide covers exactly how contractors configure GoHighLevel custom values and merge fields, which contractor-specific fields deliver the highest response improvement, and the complete setup workflow for building personalized automation sequences that work across multiple lead types and project categories.

What Are Custom Values and Merge Fields in GoHighLevel?

GoHighLevel has two related but distinct personalization systems that are often confused: custom values and merge fields. Understanding the difference is important before building any automation.

Custom values are location-level or account-level variables that stay the same across all contacts. They are typically used for business-specific information that appears in messages but does not change from contact to contact. Examples: your company name, your booking link, your office phone number, your owner's first name, a specific service guarantee. You define a custom value once, and every SMS or email template that references it pulls the current value automatically. When your booking link changes, you update it in one place and every automation that uses it updates instantly.

Merge fields (also called custom fields) are contact-level variables that pull different data for each individual contact. They insert contact-specific information into messages. Examples: first name, address, job type, project notes, estimated job value, lead source. When an automated SMS fires using the merge field for first name, GoHighLevel inserts that specific contact's first name into the message. Every recipient sees a personalized message even though the template was written once.

According to HubSpot research, personalized emails improve click-through rates by 14% and conversion rates by 10%. For SMS messages, personalization impact is even higher because SMS is a personal medium. A text addressed to "Mike" that references the specific project he called about reads as one person communicating with another. A generic "Hello there" text reads as a mass campaign. For a full overview of GoHighLevel SMS automation for contractors, read GoHighLevel SMS automation for contractors.

How to Set Up Custom Values in GoHighLevel for Contractors

Custom values are configured in GoHighLevel under Settings > Custom Values. Every contractor business should set up a core set of custom values during initial platform configuration. The table below shows the essential custom values for a contractor GoHighLevel setup.

Custom Value Name	Example Value	Used In
company.name	Apex Roofing Co	All SMS signatures and email headers
company.owner_name	Marcus	Personal-feeling SMS sign-offs
company.booking_link	calendly.com/apex-roofing	Estimate scheduling messages
company.phone	(214) 555-0100	All reply-to and contact messages
company.review_link	g.page/apexroofing	Post-job review request messages
company.guarantee	5-year workmanship warranty	Estimate follow-up trust messages
company.service_area	Dallas-Fort Worth metro	Area-specific outreach messages
company.license_number	TX #1234567	Trust-building messages and proposals

To use a custom value in a message template, you reference it with double curly braces: {{custom_values.company_name}}. GoHighLevel replaces this with the actual value when the message sends. Updating the custom value once updates every message template that references it automatically. For contractors who rebrand, change phone numbers, or update booking links, this saves hours of manually editing templates.

How to Set Up Merge Fields for Contractors in GoHighLevel

Contact merge fields (custom fields) are configured under Settings > Custom Fields in GoHighLevel. Standard system fields like first name, last name, email, and phone are pre-built. Contractors need to add trade-specific custom fields that capture the project data needed to personalize follow-up meaningfully.

Contractor-Specific Custom Fields to Create

The following custom fields are high-impact for contractor businesses because they capture data that makes follow-up messages more specific and more relevant:

• Job Type (dropdown): Roof Replacement, HVAC Install, Full Kitchen, Bathroom Remodel, etc. Used to send job-type-specific follow-up messages rather than generic ones.
• Property Address (text): The address of the project. Including the address in messages signals that you remember the specific property, not just the contact record.
• Estimated Job Value (number): Assign during intake. Used to trigger different follow-up sequences for $5K jobs versus $50K jobs.
• Lead Source (dropdown): Google Ads, Referral, Website Form, Social Media, etc. Used for source-specific messaging and routing.
• Estimate Date (date): When the quote was delivered. Used to calculate when follow-up sequence messages fire relative to the delivery date.
• Salesperson Name (text): Which team member handled the estimate. Used in messages so the follow-up comes from the same person who did the walkthrough.
• Preferred Contact Method (dropdown): SMS, Call, Email. Routes follow-up to the channel the homeowner prefers.

Using Merge Fields in SMS Templates

With contact fields populated, merge fields are inserted into message templates using the syntax {{contact.first_name}}, {{contact.custom_field_job_type}}, or {{contact.custom_field_property_address}}. A contractor estimate follow-up SMS using merge fields looks like this:

"Hey {{contact.first_name}}, {{custom_values.company_owner_name}} here from {{custom_values.company_name}}. Just checking in on the {{contact.custom_field_job_type}} quote we sent for your {{contact.custom_field_property_address}} property. Any questions before you decide? Here to help: {{custom_values.company_phone}}"

When this template fires for a contact named Sarah Chen with a kitchen remodel quote at her Scottsdale home, the message reads: "Hey Sarah, Marcus here from Apex Contracting. Just checking in on the kitchen remodel quote we sent for your 4521 N Scottsdale Rd property. Any questions before you decide? Here to help: (602) 555-0100"

That message reads like Marcus personally typed it for Sarah. It converts at a significantly higher rate than a generic follow-up. According to Salesforce research, personalized outreach improves reply rates by 26% compared to generic messages. For contractors following up on estimates worth $15,000-$80,000, a 26% improvement in reply rate is a direct revenue multiplier.

Advanced: Branch Automations Using Custom Field Values

Custom fields are not just for message personalization. They also drive conditional logic in GoHighLevel automation workflows. When a custom field contains a specific value, GoHighLevel can route a lead to a completely different automation branch. This is where contractor automation moves from basic to genuinely sophisticated.

Job Type Branching

A roofing company that does both insurance replacement and retail jobs builds two entirely different follow-up sequences. The insurance replacement branch sends messages about the adjuster process and what to expect after the inspection. The retail branch sends messages about materials, warranties, and scheduling windows. With job type stored as a custom field, a single automation workflow can check the value and route each contact to the appropriate branch automatically. No manual sorting. No wrong message sent to the wrong contact type.

Lead Value Branching

When estimated job value is stored as a custom field, GoHighLevel can apply different follow-up intensity based on job size. A $5,000 deck job gets the standard five-touch sequence over 14 days. A $75,000 addition or whole-home remodel gets a higher-intensity sequence with a personal call alert to the owner at days 2 and 5 in addition to automated texts. Treating a $75,000 prospect the same as a $5,000 prospect is a resource allocation mistake that custom field branching eliminates. For more on using automations effectively, read GoHighLevel automation recipes for contractors.

Lead Source Branching

Referral leads close at 3-4 times the rate of cold Google Ads leads. Knowing this, a contractor can build a referral-specific follow-up sequence that acknowledges the referral source, moves faster toward booking, and uses different language than the cold inbound sequence. When lead source is stored as a custom field and GoHighLevel checks it at the start of the automation workflow, referral leads automatically enter the high-conversion sequence without any manual routing.

Custom Field	Branch Condition	Different Action Triggered
Job Type	= Insurance Replacement	Insurance claim-specific follow-up sequence
Estimated Job Value	Greater than $30,000	Owner personal call alert at day 2 and day 5
Lead Source	= Referral	Fast-track sequence, referral acknowledgment message
Preferred Contact	= Call (not SMS)	Owner call task assigned instead of automated SMS
Salesperson Name	= any value	Follow-up messages sign off with that rep's name

Common Setup Mistakes Contractors Make with Custom Values and Merge Fields

Even contractors who understand the concept of merge fields make configuration errors that result in broken messages. The most common mistakes and how to avoid them:

Forgetting fallback values. If a merge field references a custom field that is empty for a contact, GoHighLevel may send a message that reads "Hey , Marcus here" with a blank where the name should be. Every merge field in a message template should have a fallback. Use conditional logic in the workflow to check that the field is populated before firing the personalized message, or set a default value for fields that are sometimes empty.

Not syncing fields from intake forms. Custom fields only work if they are populated. Every intake form on the contractor's website or landing page should map directly to the GoHighLevel custom fields that drive follow-up personalization. If the intake form captures job type as a free-text field but the GoHighLevel custom field is a dropdown with specific values, the branch logic breaks. Use GoHighLevel's native form builder or configure external form integrations to pass data into the correct field format.

Updating templates instead of custom values. When a contractor changes their booking link, they should update the custom value in Settings, not manually edit every template. Contractors who skip the custom value setup and hardcode their booking link into each template create a maintenance problem. Updating 12 templates manually when the link changes guarantees that at least one will be missed and leads will receive a broken link.

According to HubSpot, the average sales rep spends 21% of their day writing emails. For a contractor business, that time is better spent on site visits and closing jobs. Custom values and merge fields shift the writing work from daily manual tasks to one-time template configuration, then deliver personalized outreach at scale automatically. For a complete view of GoHighLevel contact management for contractors, read GoHighLevel contact management for contractors.

Frequently Asked Questions

What are GoHighLevel custom values and how do contractors use them?

GoHighLevel custom values are account-level variables stored once and referenced across unlimited message templates. For a contractor, they store information like the company name, owner name, booking link, review link, and service guarantee. Referencing a custom value in a template means updating one setting updates every message instantly. For a business with 20+ automation sequences, this is a significant time saver and eliminates the risk of outdated links in active campaigns.

What is the difference between custom values and merge fields in GoHighLevel?

Custom values are static account-level data shared across all contacts. Merge fields pull contact-specific data that is different for each recipient. Both use the double curly brace syntax but pull from different data sources. A well-built contractor automation uses both: custom values for the business information that stays constant, and merge fields for the contact-specific details like name, address, and job type that make each message feel personal.

What happens if a merge field is empty for a contact in GoHighLevel?

If a merge field references a custom field that has no value for a specific contact, GoHighLevel either leaves a blank in the message or shows an error depending on how the template is configured. The solution is to use conditional logic at the start of the automation to check whether required fields are populated before firing personalized templates, and to configure intake forms to map directly to GoHighLevel custom fields so data is captured at the point of first contact.

Send Messages That Feel Personal to Every Lead You Follow Up With

GoHighLevel custom values and merge fields are the difference between automation that feels robotic and automation that feels like a real person following up. When a homeowner gets a text that includes their name, their property address, and the specific project they asked about, it reads like attentive service. When they get a generic "checking in on your inquiry," it reads like spam. Contractors who take the time to configure merge fields properly see the response rate improvement immediately.

Setting up GoHighLevel with a complete custom value and merge field library takes 2-3 hours of upfront configuration. Once built, it runs personalized multi-touch follow-up on every lead automatically, at any volume, without the office having to write a single individual message.