HighLevel guide Β· October 2026

How to write Conversation AI prompts that book appointments

Heads up: we earn a commission if you buy HighLevel through our links, at no extra cost to you. We are an independent affiliate and do not speak for HighLevel. Full disclosure.

Part of Drop #01

This guide is one piece of the AI website booking assistant. Download the free AI Website Booking Assistant kit, which includes the full prompt, a knowledge base starter and the test script.

HighLevel's Conversation AI can answer your leads and book them into your calendar. Whether it does that well comes down almost entirely to what you write in its instructions. A vague prompt gives you a bot that chats politely and books nobody, or worse, invents a price. This guide walks through where the settings live, what to put in each one, and the prompt structure that keeps the bot focused on booking qualified people.

Screen labels change. These steps match a HighLevel account as of October 2026. If something is named differently in yours, go by your screen.

Where the settings live

Inside your sub-account, go to AI Agents, Conversation AI, click Create Agent and choose Prompt Based Agent. The agent opens on a Build tab with everything that matters for booking:

  • The prompt editor: the large text area on the left, with the Business Name field above it. New agents start with a long template; replace it. This is where the prompt goes.
  • Actions: what the bot can do, such as Appointment Booking and Human Handover.
  • Knowledge Base Triggers: which knowledge base the bot draws answers from.
  • Mode and Timing & Pacing: whether it replies on its own, how long it waits, and how many messages it sends.
  • Test your agent: a panel on the right where you chat with the bot without anything reaching real contacts.

A second tab, Deploy, sets which channels the agent answers on.

Pick the right mode while you build

Use Suggestive mode while you build: the bot drafts each reply and waits for a person to approve it. Autopilot replies on its own. Fix what you see in Suggestive mode and only switch to Autopilot once a full day goes by without corrections.

Ask for less, and let the prompt ask

Every field you collect is one more reason for a visitor to leave. For a booking assistant on a website, ask for first name and email, nothing else. HighLevel's own guidance is to put name, email and phone collection in the prompt rather than in the Contact Info action, which is for other custom fields. Step 4 of the prompt below does exactly that.

For booking, open Actions, Setup Your Actions, Appointment Booking, choose Single calendar and pick the calendar that holds your bookable appointment. Multi calendars lets the AI pick between several calendars; start with one, because routing adds a new way to fail before the basics work.

The prompt structure that books

A booking prompt needs five parts. Here is the shape, with the reasoning for each.

1. Identity and setting

You are the booking assistant for [BUSINESS NAME], a [WHAT YOU DO]
in [CITY / "online"]. You chat with visitors on our website.

Short and concrete. The bot needs to know who it represents and where it is talking, because a website chat calls for different behavior than a text thread.

2. One job, in order

YOUR JOB
1. Answer questions using ONLY the knowledge base. If the answer is not
   there, say [OWNER NAME] will follow up, and collect their email.
2. When someone shows interest, ask one or two short questions:
   [QUALIFYING QUESTION 1], [QUALIFYING QUESTION 2].
3. If they are a fit, offer a [APPOINTMENT NAME] and two or three times.
4. Before booking, collect their first name and email address.
5. Confirm the booking: day, time, time zone, and what happens next.

The numbered sequence matters. Without it, bots tend to either jump to booking before understanding the visitor, or never get to booking at all.

3. Who is and is not a fit

WHO IS A FIT
- Good fit: [YOUR IDEAL CUSTOMER]
- Not a fit: [WHO YOU DO NOT SERVE]. Be kind, point them to
  [ALTERNATIVE], and do not book them.

This one block saves your calendar from people you cannot help. Be specific: "homeowners within 20 miles of downtown" beats "local customers".

4. Hard rules

RULES
- Keep replies to 1 to 3 short sentences. One question at a time.
- Never invent prices, discounts, availability or promises.
- Never give legal, medical or financial advice.
- Always confirm the visitor's time zone before booking.
- If someone is upset, asks for a person, or asks something sensitive,
  stop and tell them [OWNER NAME] will reply personally.
- Do not claim to be human. If asked, say you are [BUSINESS NAME]'s
  AI assistant and a person reads every conversation.

These are the rules that keep you out of trouble. The "never invent" line is the most important sentence in the prompt; the honesty line about being an AI is the second.

5. Tone

TONE
[Friendly and plain-spoken / professional and brief]. No jargon.

Under Response Behavior you can also turn on response style settings. For booking, short is better: brief messages read like a person typing. Add a wait of a few seconds under Timing & Pacing so replies do not land instantly.

Feed it a knowledge base, not a novel

The prompt says how to behave; the knowledge base says what is true. Add your real answers as FAQs: what you do and for whom, location, how pricing works, what happens on the first call, hours, rescheduling, and how to reach a person. Two or three sentences each, in your own words. The kit has a 12-question starter list.

Avoid dumping your whole website in on day one. A smaller, accurate knowledge base produces more accurate answers than a large, messy one.

Test it like a difficult customer

Before anyone real talks to it, use the Test your agent panel and send the bot messages designed to break it: ask for a price you have not given it, ask for a time outside your hours, ask whether it is a real person, ask for a service you do not offer, and complain. Then repeat the tests in Suggestive mode on your site, where you see every draft. When a reply is wrong, fix the prompt or the knowledge base, then test again. The kit includes a 12-message test script with what a passing answer looks like.

Common mistakes

  • Collecting phone numbers on web chat when you will never call. It lowers completion.
  • No exit for humans. Upset visitors talking to a bot that keeps selling is how you get bad reviews. Add the Human Handover action with Human Requested turned on.
  • Two agents on one widget. New accounts include a default agent that answers on every channel. Turn its channels off on its Deploy tab before you deploy yours.
  • Skipping calendar sync. The bot books into HighLevel's availability. If your Google Calendar is not connected as a conflict calendar, it will happily offer times you are busy. See the Google Calendar sync guide.
  • Going straight to Autopilot. A day in Suggestive mode catches most problems for free.

Questions

How long should the prompt be?

Long enough to cover the five parts above, usually 250 to 400 words. Past that, rules start contradicting each other.

Can the bot take payments while booking?

Not during the booking conversation, according to HighLevel's documentation. Collect payment separately if you need it.

Does Conversation AI cost extra?

AI features are usage-billed. Check the current pricing inside your HighLevel account before switching to Autopilot.

Not using HighLevel yet?

HighLevel offers a 14-day free trial. We earn a commission if you sign up through that link.