Tag: contact first name

By Elijah LeFavour, Chief AI Officer at Spectral Vision. Published October 15, 2026.

GHL.Support is independent and not affiliated with HighLevel, Inc. If you start a HighLevel account through a link on this page we earn a commission at no extra cost to you. It never changes a number we publish. Read our full disclosure.

You open a draft and see “Hi ,” where your customer’s name should be. You need to fix that greeting before the message goes out. Insert the saved first name through the editor’s picker, then give an empty email field a fallback. Use the steps below to save First Name, insert {{contact.first_name}}, fix a blank or raw token, and test your greeting.

I read HighLevel’s merge-field list, its email fallback guide and its email preview guide before writing this, and you need a saved First Name and the right contact record to insert a recipient’s name. A contact field needs a contact, while an appointment field needs an appointment. HighLevel’s merge-field and email fallback guide, updated October 2, 2026, explains why correct spelling alone does not supply missing data.

What is the contact first name merge field in GHL?

HighLevel inserts your recipient’s saved first name from {{contact.first_name}} when it generates supported content. HighLevel’s merge-field list, updated September 1, 2026, separates it from {{contact.name}}, which inserts the full name. Use the first-name field for a personal greeting in your email marketing or SMS marketing message.

1. Open your supported email or SMS message editor and place the cursor after the greeting.
2. Click Merge Field, Custom Value, or the { } icon, according to the editor you are using.
3. Search for the first-name field or open its Contact category, then select First name.
4. Review the complete sentence around {{contact.first_name}} and save your changes.
5. Test using a contact whose First Name contains data before activating your workflow automation.

Your first-name greeting uses HighLevel’s built-in standard First Name field. Custom fields store information that differs by contact or another record. Custom values store reusable information, such as a shared support email address.

Use Contact fields for your recipient’s data, Account fields for account data, and Appointment fields for booking data. HighLevel groups contact, account, and appointment fields separately. For your appointment reminders, the workflow needs an appointment record to supply its time or reschedule link.

Information you need	Field and required record
Recipient’s first name	{{contact.first_name}} retrieves First Name from the contact.
Recipient’s full name	{{contact.name}} retrieves the contact’s full name.
Your account name	{{location.name}} retrieves the account name.
Appointment start	{{appointment.start_time}} requires an appointment record.
Reschedule link	{{appointment.reschedule_link}} retrieves the appointment’s reschedule link.

Where does GHL get the contact first name from?

HighLevel reads your contact first name from the saved First Name field on the contact record. Add an individual name manually, collect new names with a form, or map existing names from a CSV. Store each name in that standard field so your greeting retrieves the right value.

1. For manual entry, open Contacts → Smart Lists → + Add Contact, enter First name and the other contact details, then click Save. These are the steps in the contact creation guide, updated August 17, 2026.
2. For a form, open Sites → Forms → + Create New Form and choose a blank form or template. Add First Name, choose whether to require it, then save and preview the form. Submit test information and review it in the Submissions tab, following the contact form guide, updated September 10, 2026. Click Integrate, then copy the embed code to add the form to a website or use the direct form link to share it independently.
3. For a CSV, open Contacts → Import, select Contacts, and click Next. Confirm the format, upload your file, and map its first-name column to First Name. Complete the import details and click Bulk Import, as described in the import guide, updated March 24, 2026. Wait for the contacts to finish importing.

A new lead’s form submission creates a contact record for your follow-up. HighLevel lists First Name and Last Name as standard form fields and First Name as a standard import field. Store the name in the standard First Name field instead of creating a duplicate field.

What shows when the contact first name is empty?

Set a fallback so an empty first-name field does not leave a blank in your email greeting. Add there as the default to get “Hi there,” when the saved name is missing. HighLevel’s email fallback instructions, updated October 2, 2026, document this for templates, workflow emails, campaign emails, and bulk emails.

1. Create or edit your email and insert the first-name field through the picker.
2. Click the inserted tag to open the Default Text editor.
3. Enter there as the fallback text, then click Save.
4. Repeat for each occurrence that needs a default, including the subject, preview text, and body.
5. Send a test using a contact whose First Name is blank and inspect the resulting greeting.

The fallback changes your generated email without filling the contact’s CRM record. Each occurrence keeps its own default, so setting a body greeting does not set the subject’s default. HighLevel’s dedicated default-values guide, updated May 21, 2026, also says saved contact information takes precedence over fallback text.

HighLevel’s September 1 overview and October 2 email fallback guide conflict. The merge-field overview, updated September 1, 2026, says HighLevel does not support fallback values. The October 2 email fallback guide explicitly documents them, so follow that guide’s Default Text instructions for your emails.

How do you fix and test a first-name message?

If your message shows raw braces, delete the token and reinsert it through the picker in a supported editor. If the field renders blank, check the saved value and confirm that the action has the required record. HighLevel’s October 2, 2026 email fallback guide gives separate fixes for a raw token, a blank value, and a missing fallback. Reinsert a raw token, restore missing contact data, or save a fallback for the affected email tag.

What you see	What to check
Empty name	Confirm the contact has a saved First Name and the action has access to that contact.
Raw token	Reinsert through the picker and confirm the editor supports that field.
Email fallback missing	Confirm you saved the default for that specific tag in a supported email area.
Send action fails	Inspect missing closing braces or extra opening braces across the message.

HighLevel’s guide warns that one invalid or malformed custom value risks stopping your entire action from firing. The send-error checklist, updated July 1, 2026, identifies missing closing braces and extra opening braces in email and SMS. Keep the documented token intact, including its lowercase letters and the underscore in first_name.

Correct a name’s capitalization with a formatting action when your automation needs it. HighLevel’s Text Formatter guide, updated February 5, 2025, lists Title Case and Capitalize as separate operations. Title Case changes each word’s initial letter, while Capitalize changes the initial letter of the first word.

1. Open Automation → Workflows and click Create Workflow, or edit an existing workflow.
2. Click the plus (+) button and select Text Formatter.
3. Choose Title Case to capitalize the first letter of every word or Capitalize to change the first letter of the first word, then select Contact → First Name.

Preview and send a test before using your finished greeting. HighLevel’s email preview and testing guide, updated September 21, 2026, lists these Preview and Test Email controls for campaigns and templates. Review both the rendered name and the surrounding sentence.

1. Open Marketing → Emails → Campaigns/Templates, select the item, and switch to Design Editor.
2. Click Preview at the top right and check Desktop, Tablet, and Mobile views.
3. Click the Three Dots beside Preview, then Test Email.
4. Set Sender Email, Sender Name, Receiver Email, Preview Text, and Email Subject.
5. Click Send Test Email and inspect the received message.

In your workflow’s Send Email action, use Test Emails and Send Test Mail. HighLevel’s Send Email guide, updated April 24, 2026, documents Test Emails and Send Test Mail. For a blank merge field in a workflow test, check the contact’s saved data and the records the trigger or action supplies before saving the action.

1. Open the Send Email action in your workflow.
2. Enter your email address in Test Emails and click Send Test Mail.
3. Inspect the received content and formatting, then click Save Action.

What does a HighLevel account cost?

HighLevel includes Contact First Name as a standard field in every account, as its September 1, 2026 merge-field overview explains. HighLevel list price as of October 9, 2026: $97 a month for Starter, $297 a month for Unlimited, and $497 a month for Agency Pro. Compare Starter, Unlimited, and Agency Pro in the pricing plans comparison before choosing your monthly subscription. On October 9, 2026, HighLevel’s pricing page said your subscription covers platform features and lists separate usage charges for sent emails and text messaging. Having the First Name field in your account does not remove those sending costs.

Start your own HighLevel account through our link and you pay HighLevel directly, from $97 a month. We earn a commission from HighLevel at no extra cost to you. HighLevel’s pricing page lists a 14-day free trial on any plan.

The GHL.Support tutorial library lists more HighLevel setup procedures. For gym account ownership and membership billing, use the gym guide. Before sending your greeting, test the message with the contact record that supplies the expected First Name.

Contact first name FAQ

How do I insert a contact’s first name into an email or SMS?

Use the supported editor’s field picker, or type / in a workflow text field to search for a value. HighLevel’s workflow dynamic-value guide, updated September 17, 2026, says blue chips indicate an available value, yellow chips indicate unavailable workflow context, and red chips indicate an unrecognized value. A yellow chip warns you about missing context without blocking saving or publishing.

What happens when the first name is missing, and how do I add an email fallback?

Click your email tag, enter fallback text in Default Text, and save it. A green tag has a default, while a grey tag does not. Hover over a configured tag to see its default, or click it again to edit that text.

How does HighLevel get the first name from forms, imports or manual entry?

Manual entry, forms, and imports save First Name on your contact record. Edit an existing record through Contacts → Smart Lists. Select the contact, click the Contact Name, edit its details, and save your changes. Your account configuration controls which fields appear during contact creation.

How do I fix capitalization, wrong braces, spaces or a missing name?

Use Text Formatter for capitalization and the picker for supported syntax, then inspect your saved contact name. Workflow Builder accepts spaces immediately inside braces, according to the September 17 dynamic-value guide. Its rule differs from letter case: the merge-field overview explicitly says field names are case-sensitive.

Where do merge fields work in workflows, templates, funnels and trigger links?

In your workflow text field, type / to find and insert the value, then click its chip to replace it if needed. In email templates and campaigns, use the picker in the body or subject line, as described in HighLevel’s September 17, 2026 dynamic-value guide. Website and funnel personalization requires stored visitor data from a previous form submission or appointment booking, and field support depends on your editor and available records. For trigger-link destinations, the HiRise trigger-link guide, updated October 15, 2025, documents a {} picker for fields including first name.

How do I test the message, and does personalization cost extra?

Preview and Test Email check your campaign or template, while Send Test Mail checks your workflow’s Send Email action before Save Action. HighLevel disables unsubscribe actions in test emails, so an inactive unsubscribe link does not signal a name-field failure. Every account includes Contact First Name as a standard field, while HighLevel’s October 9, 2026 pricing page lists usage charges for sent SMS and email.