Writing replies

Every keyword has a reply. Replies are written in a familiar message editor with three things sitting next to it: variables, snippets, and favorites.

Variables

Variables pull live data from GHL into the reply at send time. The variable picker is grouped by source:

• Standard contact fields — first name, last name, email, phone, address, city, state, postal code, country, etc. These come from the contact GHL has on file for whoever commented.
• Custom fields — anything you've defined under Settings → Custom Fields in your GHL sub-account.
• Custom values — sub-account-wide values you've set under Settings → Custom Values.
• Calendars — the public booking URL for any calendar in the sub-account.
• Trigger links — short URLs you've created in Marketing → Trigger Links.

A variable looks like {{ contact.first_name }} in the editor. At send time, GHL substitutes the live value.

If a picker is empty, the most likely reason is your Private Integration Token is missing the relevant scope. See Installation for the full scope list.

Snippets

A snippet is a saved chunk of message text — a hook, a CTA block, a P.S. line, anything you want to reuse across multiple keywords. Manage them at Snippets in the sidebar.

Inside a reply, click the Snippets button to drop one in. Snippets are scoped to the team account, so everyone on your team sees the same library.

Favorites

The favorites bar is a per-organization shortlist of variables you use a lot. Star a variable inside the picker and it pins to the top of the editor as a one-click insert. Favorites travel across keywords — set them up once for the org, use them everywhere.

Tips

• Keep replies short. DMs that read like a human get higher engagement than DMs that read like an email.
• Use {{ contact.first_name }} early in the reply — it's the cheapest personalization there is.
• Don't paste calendar URLs by hand. Use the Calendars picker so the URL stays correct if you change the calendar's slug later.