OpSkills
AI Workflows · 10 min read

GHL Conversation AI Setup — From Trigger to Tone

The actual walkthrough for setting up GoHighLevel's Conversation AI to handle inbound chat + SMS without burning trust. Trigger rules, tone calibration, escalation logic, and the four configuration mistakes that kill it.

A new lead hits your website chat widget at 11:47pm on a Tuesday. They ask a question. Without AI, the answer comes back in the morning. By morning, they’re already on your competitor’s site.

With Conversation AI set up correctly, the answer comes back in 8 seconds. The conversation continues. The lead books a call before midnight.

The catch — and there’s always a catch — is that “set up correctly” is doing a lot of work in that sentence. Most operators turn on Conversation AI, ask it to “be helpful,” and watch it confidently give incorrect answers, miss obvious sales opportunities, or worse, sound like a robot that’s pretending to be a human and getting caught.

This post is the practitioner’s walkthrough. The actual settings that make Conversation AI work, the tone calibration that keeps it from sounding generic, and the four mistakes I see in nearly every fresh client setup.

What Conversation AI actually is in GoHighLevel

GHL’s Conversation AI is the chat + SMS arm of the AI Employee suite. It can:

It does NOT:

Match it to the right job: first-touch qualification, FAQ handling, appointment booking. That’s the strike zone.

The four-component setup

Conversation AI in GHL has four configuration layers. Get all four right and the system performs. Skip any one and it breaks.

Component 1 — The knowledge base

The AI answers based on what you’ve fed it. Garbage in, garbage out. The knowledge base should include:

For most service businesses, this is a 2,000-4,000 word document. Spend an afternoon writing it. Then upload to GHL Settings → AI → Knowledge Base.

Important: write the knowledge base in the voice you want the AI to use. The AI mirrors the language of its training material. Stiff knowledge base = stiff AI. Conversational knowledge base = conversational AI.

Component 2 — The trigger rules

When should Conversation AI fire vs. when should a human pick it up?

The defaults in GHL fire the AI on every inbound chat/SMS. Don’t accept the defaults. Sensible trigger rules:

Set these in Settings → AI → Triggers. About 15 minutes of work.

Component 3 — The conversation flow

What questions should the AI ask, in what order?

For lead qualification, a typical flow:

  1. Acknowledge the inbound message
  2. Ask one qualifying question (e.g., “What’s the timeline you’re working with?”)
  3. Based on response, ask one more question (e.g., “And what’s your approximate budget?”)
  4. Offer either: a) book a call, b) send an email with more info, or c) hand off to human
  5. Confirm the next step

Four messages from the AI, four from the visitor. Eight total turns. Most conversations should resolve in this range. If you find yourself going past 12 turns, the AI is going in circles and you should add a “hand off to human” trigger at turn 10.

Component 4 — The escalation rules

The single most important part. When does the AI stop and pass to a human?

Always escalate on:

Set these in Settings → AI → Escalation. The AI escalates by adding a tag like “needs_human_attention” and notifying your team via internal SMS/Slack.

The escalation rules are what separate “AI that helps” from “AI that frustrates customers.” Get them right.

1

Knowledge base

What the AI knows about your business.

2,000-4,000 words covering services, pricing, objections, hours, brand voice samples. Write in the voice you want the AI to use — it mirrors.

~2 hours to write

2

Trigger rules

When AI fires vs. when a human picks up.

Default = AI on every inbound. Override for known customers, urgent tags, active sales pipelines. After-hours SMS = AI default.

~15 min to configure

3

Conversation flow

How the AI structures the exchange.

Acknowledge → qualifying Q1 → qualifying Q2 → offer book/info/handoff → confirm. Cap at 10 turns total. Past that = escalate.

8 turns target

Tone calibration — the underrated lever

The default AI tone in GHL is generically friendly. That’s fine for some businesses, wrong for others. Tone calibration is the single biggest difference between an AI that feels like part of your brand vs. one that feels like a generic chatbot.

Three levers:

Lever 1 — Voice prompt

In Settings → AI → Voice & Tone, write a 2-3 paragraph description of your brand’s voice. Examples:

For a high-end med spa:

“Speak warmly but professionally. Use the client’s name when known. Avoid casual contractions like ‘gonna’ or ‘wanna’ — use full forms. Never use emojis. Never start a message with ‘Hey’. Match the energy of a concierge at a luxury hotel.”

For a coaching business with a younger audience:

“Speak like a knowledgeable friend, not a service rep. Use casual contractions. One emoji per message is okay if it lands. Skip honorifics. Ask ‘how’s that sound?’ instead of ‘is this acceptable?’. Match the energy of texting with a smart friend.”

Each gets a very different AI personality. Both are valid. Match the description to your audience.

Lever 2 — Sample dialogues

GHL lets you upload 10-20 sample conversations (real ones from your team, anonymized). The AI uses these as the strongest signal for tone. Five well-chosen samples beat 50 hours of prompt engineering.

Pick conversations that show:

Lever 3 — Forbidden phrases

In Settings → AI → Restrictions, list phrases the AI should never use. Common ones:

Forbidden phrases are surprisingly effective. They prevent the failure modes that make AI feel generic without you having to predict every scenario.

Setting up booking from chat

The single highest-value capability of Conversation AI is direct calendar booking. The setup:

Step 1 — Connect a calendar. In Settings → AI → Calendar Integration, select the calendar the AI can book to. Usually a “Discovery Call” or “Initial Consultation” calendar with 30-min slots, 24-48h advance booking required.

Step 2 — Define booking rules. Who can book? Often “anyone who’s qualified” — meaning the AI must complete at least 2 qualifying questions before offering a slot. Otherwise everyone books and your calendar fills with low-quality leads.

Step 3 — Set buffer time. 15-min buffer between bookings prevents the AI from booking a 9:00am slot when your 8:30am call might run long.

Step 4 — Confirm via SMS. When the AI books, it auto-sends an SMS confirmation with calendar link + reminder. Test this end-to-end before launching.

Step 5 — Set the cap. Maximum 3 bookings per AI-only path per week. Beyond that, force human qualification. This protects you from a viral spike that books 20 calls in one weekend.

Conversion rates from chat-to-booking when set up correctly: typically 8-15% for med spas, coaching, real estate. The unset-up version converts at 2-3%. The lift pays for the AI add-on inside the first month.

The four mistakes that kill Conversation AI

After auditing 15+ client setups, four consistent failures:

Mistake 1 — Pretending the AI is human

The AI introduces itself as “Sarah” or “Mike” or “Alex.” Visitors find out it’s an AI 6 messages in. Trust evaporates. Reviews tank.

The fix: be transparent. “Hi, I’m the booking assistant for [business name]. I can answer questions and help you book. If anything gets complicated, I’ll hand you to the team.” Honest from message one.

Mistake 2 — No knowledge base scope

The AI gets asked something outside its training and confidently hallucinates an answer. “Yes, our spa has a 90-day satisfaction guarantee” (you don’t). The customer holds you to the AI’s claim. Legal exposure.

The fix: scope-limit the AI explicitly. Restrict it to topics in your knowledge base. For anything else, escalate. Don’t try to give it free range.

Mistake 3 — Too-aggressive sales push

The AI tries to close every conversation with “Want to book a call?” — even when the visitor just asked what hours you’re open. Pushy AI burns trust faster than pushy humans because the visitor doesn’t have a relationship buffer.

The fix: separate “info” intents from “buying” intents. Info questions get info answers. Don’t try to book the curious — book the qualified.

Mistake 4 — No human review loop

You set up the AI on Monday. On Friday you have 50 conversations you haven’t read. The AI is making mistakes you don’t know about because you haven’t audited.

The fix: weekly 30-minute audit. Read 10-15 random conversations. Tag failures. Add to forbidden phrases / knowledge base / escalation rules. The AI gets sharper every week.

Pretending AI is human

"Sarah" introduces herself, visitor catches on 6 messages in. Trust evaporates. Be transparent from message one.

No knowledge base scope

AI confidently hallucinates: "Yes, we have a 90-day guarantee" (you don't). Customer holds you to the claim. Legal exposure.

Too-aggressive sales push

AI tries to book every conversation. Pushy AI burns trust faster than pushy humans — no relationship buffer.

No human review loop

Set on Monday, never audited. AI makes mistakes invisible to you. Weekly 30-min audit is non-negotiable.

The metric that matters

Most operators measure “AI handle rate” — what % of inbound conversations did the AI resolve without human intervention. This is the wrong metric.

The right metric is conversion rate from inbound chat to booked appointment or sale. Doesn’t matter if AI or human handles it — what matters is the downstream business outcome.

A healthy setup converts inbound chats to bookings at 8-15% (combined AI + human). If you’re under 5%, the system isn’t working regardless of how much “AI handle rate” you’re showing.

Measure the right thing. Adjust accordingly.

What to do this week

Three actions if you’re setting up or auditing Conversation AI:

Step 1 — Write the knowledge base. 2,000-4,000 words in your brand voice. Spend an afternoon. Upload to GHL.

Step 2 — Configure escalation rules. The trigger phrases + the 10-turn timeout + the negative-sentiment detector. 30 minutes of configuration. Single biggest determinant of customer satisfaction.

Step 3 — Audit weekly. Block 30 minutes every Friday. Read 10 conversations. Tag failures. Update settings.

The AI gets smarter only if you treat it like an employee in training, not a feature that runs itself.

Closing

Conversation AI isn’t a magic feature. It’s a configurable system that gets dramatically better or worse based on the work you put into setup.

The agencies and operators who win with AI aren’t the ones who turned it on and hoped. They’re the ones who treated the first 30 days as configuration time, not auto-pilot. By month two, the system runs itself.


Related reading:

Free PDF · No signup tricks

Free: The GHL Snapshot Library

7 battle-tested GoHighLevel workflows you can steal today. No fluff, no upsell.

Delivered to your inbox in 60 seconds. Unsubscribe anytime.

Keep reading

Related posts