How to Use HighLevel to Turn Form Leads into Booked Calls

The short answer: open the client's sub-account (or load a snapshot into it), set up a dedicated sending domain, create a booking calendar, build a form with a notification and an auto responder, start a workflow on the Form Submitted trigger that sends the booking link, let Conversation AI draft replies in Suggestive mode while a person approves them, then embed the form and compare submissions with appointments after the first week.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: a client's website collects enquiries, and too many of them never become a booked call because nobody follows up the same day. HighLevel can answer every form with a booking link, remind people who book, and draft replies to those who answer back. For what the platform is and costs, see the HighLevel glossary entry.

Before you build:

• Price the follow-up first. For example, a confirmation and two reminders for 400 leads a month is 1,200 emails, which at $0.675 per 1,000 is $0.81, using the rate in HighLevel's pricing guide (checked on 24 October 2026). Email is the small line; AI Employee, at $50 or $97 a month per sub-account in the same guide, is the larger one.
• Start from what the client has. Copy the fields of the current enquiry form and the hours someone can take calls. Those two lists become the form and the calendar.
• Decide the measure now. Bookings divided by form submissions, counted for one week before and one week after, is enough to know whether the change worked.

What you need

• A sub-account for the client. Starter covers three, per the pricing page.
• Access to the client's DNS for the sending domain.
• Consent for any SMS. HighLevel's messaging policy says SMS goes only to contacts who opted in, that consent cannot be bought with a list, and that the first message must identify the sender and say how to stop, such as "Reply STOP to unsubscribe".

Step 1: Load the snapshot, if you have one

From the Agency Dashboard, open Sub-Accounts, click the three-dot menu next to the client and choose Manage Client, then Actions and Load Snapshot, per the snapshot loading guide. Pick the snapshot, tick only the assets you need and review each conflict before you confirm, because an asset you choose to override replaces the client's version. If Load Snapshot is missing, check Snapshot access under Roles and Permissions. With no snapshot yet, build steps 2 to 5 by hand in this sub-account; it can become your first snapshot.

Step 2: Send from the client's domain

Go to Settings, Email Services, the Dedicated Domain and IP tab, and click Add Domain. Enter a sub-domain such as mail.clientname.com and verify the DNS records, automatically or by hand, as the sending domain guide explains. Propagation can take up to 24 hours. Warm up a brand-new domain before it emails a large list.

Step 3: Create the booking calendar

Go to Calendar, Calendar Settings, click New Calendar and choose Personal Booking for one-to-one calls, per the calendar guide. Give it a name, a host, a URL, the call length and the hours you collected, then confirm. Copy the calendar link; the workflow will send it. The same guide sets up reminders with the Appointment Confirmation + Reminder recipe under Automation: edit the confirmation email's meeting link, review the actions and publish.

Step 4: Build the form

Go to Sites, Forms and click Create New Form, starting blank or from a template, as the contact form guide describes. Add the client's fields and mark the essential ones required. Under Notifications, set an internal email alert to whoever covers the inbox and an auto responder for the person who submitted. Choose a thank-you message or a redirect, save, submit a test entry and confirm it appears in the Submissions tab.

Step 5: Start the follow-up on submission

Create a workflow under Automation, click Add New Trigger and choose Form Submitted, then set the filter Form is to the form from step 4, per the trigger guide. Add the actions: an email with the calendar link, and an internal notification or task for the owner. Test with sample data, then switch on the Publish toggle. The workflow stays inactive until you do.

Step 6: Let Conversation AI draft the replies

Some leads answer the email or text back instead of booking. In the sub-account, open AI Agents, Conversation AI, and create a bot, per the booking guide. Set its name, wait time and first message; under Bot Goals choose the details to collect; enable Appointment Booking and select the calendar from step 3. Add prompt and training content with the facts the client wants said, because calendar descriptions alone do not reach the customer.

Set the bot to Suggestive mode. HighLevel's bot guide describes it plainly: the AI drafts each reply, and a person reviews, edits and sends it. Keep it there until the drafts need no edits for a week, then consider Autopilot.

Step 7: Embed the form

In the form builder, open the Integrate tab, choose the form type and copy the embed code, or share the direct link, per the embed guide. The guide has steps for Squarespace, Wix, Shopify, WordPress and Duda.

Step 8: Read the first week

The form's Analytics tab shows views, responses, average completion time and completion rate, per the contact form guide. Set those responses beside the appointments on the calendar for the same days, and you have the measure you chose before building. Then check the wallet: the pricing guide shows charges by sub-account under Agency View, Settings, Billing.

Where HighLevel's own docs say it goes wrong

• Expecting a snapshot to bring the client's data. Contacts, appointments, conversations, Stripe connections and other integrations do not transfer, per the snapshots overview. Reconnect them in the new sub-account.
• Several DKIM records for one domain. The sending domain guide says that is not supported.
• Multiple calendars on the wrong bot type. Routing across several calendars works only for prompt-based Conversation AI bots; Guided and Flow Builder bots use a single calendar.
• Untested cancellation and rescheduling. The booking guide asks for live testing of both before the bot faces leads.
• Texting a bought list. The messaging policy rules it out: consent cannot be bought or exchanged.

A ready-made recipe or snapshot is designed to get a workflow live quickly, and every message a live workflow sends draws on the wallet. Run each one on your own test contacts first.

FAQ

Do I need a snapshot to start?

No. Build the form, calendar and workflow in one sub-account first. Once it works, create a snapshot from that account and load it into the next client's.

Can the AI book the call itself?

Yes, with Appointment Booking enabled and a calendar selected, per the booking guide. In Suggestive mode a person still sends each message the bot drafts, including the one that offers times.

How long before emails send from the client's domain?

As soon as the DNS records verify, which can take up to 24 hours, per the sending domain guide. A new domain still needs warming up before large sends.