
Conversation AI in GoHighLevel: How It Actually Decides to Reply
GoHighLevel Conversation AI does not simply search a FAQ and send the first matching sentence. It first determines whether the bot is eligible to answer, reads the latest message with recent context, classifies the contact’s intent, retrieves relevant instructions and knowledge, and generates a response within the bot’s goals and permitted actions. Off, Suggestive, and Auto-Pilot then determine whether that response is withheld, presented for approval, or sent automatically.
The decision chain behind every reply
A reply starts with routing, not intelligence. The bot’s deployment settings determine whether it is eligible for the conversation based on the messaging channel, connected destination, required tags, and excluded tags. Supported channels include SMS, Email, Facebook, Instagram, WhatsApp, Live Chat, and Chat Widget.
Direct assignment takes priority over ordinary channel-and-tag routing. A bot assigned manually, through the Update Conversation AI Bot and Status workflow action, or through Transfer Bot remains assigned until its status or assignment changes. This matters when a bot answers a contact who appears to be excluded: the direct assignment can be the real reason it is still active.
After routing, the New Query Detection Flow reviews the latest message against recent conversation context. It decides whether the contact is continuing an earlier topic or introducing a new question, support request, sales question, appointment request, or business-information request.
The system then matches that intent against the bot’s training data, Knowledge Sources, instructions, and conversation history before generating a reply. There is no separate toggle for this query detection step. A wrong answer therefore has several possible causes: the wrong bot was assigned, the intent was matched to weak information, the prompt pushed the wrong objective, or the knowledge contained duplicate, outdated, or conflicting statements.
Off, Suggestive, and Auto-Pilot control what happens after generation
The response mode does not rewrite the bot’s knowledge or goals. It controls what happens to the generated answer.
| Mode | What happens | Operational use |
|---|---|---|
| Off | No bot reply is sent. | Use while rebuilding routing, training, or instructions. |
| Suggestive | The bot drafts a reply, but a team member reviews and sends it manually. | Use to inspect real drafts without giving the bot permission to speak for the business. |
| Auto-Pilot | The generated reply is sent automatically according to the bot’s prompt, training, goals, actions, and behavior settings. | Use only after the test set passes and handoff rules are operational. |
HighLevel’s setup process calls for testing lead capture, FAQs, appointment booking, unknown questions, and workflow behavior before enabling Auto-Pilot. Suggestive mode is therefore more than a writing assistant: it is the safest place to observe how routing, intent detection, prompts, knowledge, and conversation history combine.
Review the entire draft, not just factual accuracy. A correct answer can still be operationally wrong if the bot asks for information already in the CRM, promises an action it cannot perform, keeps chatting instead of booking, or fails to escalate an unsupported request.
The prompt defines the job, not just the tone
The bot’s core prompt is assembled from separate controls. Personality defines the role, tone, and style. Goal or Intent defines the outcome, including answering questions, generating leads, booking appointments, collecting information, or directing the contact to a next step.
Additional Information contains boundaries and handling rules. This is where instructions such as asking one question at a time, avoiding emojis, mirroring the contact’s language, refusing to guess, and offering human help belong. Custom Values can inject business, account, contact, or assigned-user information into the prompt.
Conflicting instructions produce inconsistent behavior. “Answer in one sentence” conflicts with “provide a detailed explanation.” A custom 40-word limit competes with the separate Response Style control. “Always book an appointment” conflicts with a rule to answer support questions before proposing the next step. Remove the conflict instead of adding another instruction to correct it.
A selected template only supplies the initial prompt foundation and can be overwritten. For simple Q&A, lead capture, and appointment booking, Guided Form Setup provides the least configuration. Prompt-Based Bots expose model selection, detailed instructions, goals, and actions. Flow-Based Builder adds visual branching, multi-step objectives, and tighter control over lead qualification. When the objective cannot be expressed clearly as a prompt and permitted action, read When an AI Agent Is the Wrong Answer before adding more instructions.
The practical prompt-writing standard is outcome first, boundaries second, and style third. Writing the Prompt for a GoHighLevel Bot That Books Instead of Chats addresses the difference between a bot that maintains conversation and one that moves a qualified contact toward an appointment.
Knowledge Sources determine what the bot has to work with
A GoHighLevel Knowledge Base can contain website and help-center pages, FAQs, policies, written instructions, pricing or service tables, uploaded files, Google Drive files, and approved web sources. The available source types include Web Crawler, FAQ, Rich Text, File Upload, Tables, Web Search, and Google Drive.
The refreshed interface manages these sources under AI Agents → Knowledge Base, after which the Knowledge Base is selected inside the bot. Accounts using the earlier interface can show Web Crawler and Custom Bot Responses directly under Bot Training.
More source material is not automatically better source material. If an old website page lists one policy and an uploaded document lists another, the bot receives conflicting evidence. Duplicate service descriptions written with different terms also make intent matching less clear. Remove outdated material and keep one authoritative version of each price, policy, service boundary, and booking rule.
Separate facts from behavior. “The consultation lasts 30 minutes” belongs in the Knowledge Base. “Ask one question at a time and hand off when duration is unavailable” belongs in the prompt or action configuration. Mixing these categories makes updates harder and leaves the bot with competing instructions.
Goals and actions decide what the bot is allowed to do
Bot Goals combine the conversational objective with actions the bot is permitted to perform. Available actions include Appointment Booking, Trigger a Workflow, Contact Info, Human Handover, Stop Bot, Auto Follow-Up, and Transfer Bot.
This is the distinction between a bot that talks about booking and a bot configured to book. The goal can tell it to move the contact toward an appointment, but Appointment Booking must also be available as an action. The same principle applies to workflow triggers, human escalation, and routing to a specialist bot.
Information Collection can ask for name, email, phone, street address, city, and custom qualification details such as service preference, customer type, service area, budget, or business name. Each answer should be connected to its intended CRM field through Update Contact Field. An unmapped question can still be asked, but its answer does not update the intended field.
Enable Skip if Already Filled for every mapped value that should not be requested twice. This prevents the bot from asking for a phone number, email address, or qualification answer that is already present on the contact record. It also keeps workflows, segmentation, reporting, and follow-up tied to structured fields rather than facts buried in conversation text.
After changing personality, goals, instructions, or actions, use Test Your Bot again. A prompt change can alter which action the bot selects even when the action settings themselves have not changed.
Handoff and transfer rules contain failures
Human Handover supports three built-in scenarios: Human Requested, Lack of Information, and Failed to Resolve Issue. Human Requested accepts custom example phrases. Lack of Information activates when the bot cannot find relevant knowledge. Failed to Resolve Issue activates after repeated unsuccessful attempts, with a maximum of two retries in the documented behavior.
A handoff can assign the conversation to a user, send a final message, pause the bot for a configured number of days, hours, and minutes, create a task due 24 hours after the trigger, and add the default human_handover tag. Assignment without a task leaves staff with no deadline. A task without pausing the bot allows the automated conversation to continue while a person prepares to respond.
When Human Handover is not visible, check whether it needs to be enabled through Labs. Test direct phrases such as “I need a person,” indirect expressions of frustration, questions absent from the Knowledge Base, and an issue that remains unresolved after two attempts.
Transfer Bot serves a different purpose. It routes a conversation from a general bot to a specialized bot using intent conditions and realistic example phrases while preserving context. The source and destination bots must be active on the same channel and both must be in Auto-Pilot. The destination bot should be published and tested.
Transfer conditions must not be vague or overlapping. Direct assignment through Transfer Bot takes priority over ordinary channel-and-tag routing. When Transfer Bot is combined with Update Conversation AI Bot and Status, insert a Wait step so the original bot does not repeatedly reassign the conversation.
Auto Follow-Up separately handles contacts who stop responding, say they are busy, or request contact later. Each scenario supports up to five sequences with delays in minutes, hours, or days. Do not trigger a second follow-up through a workflow because that breaks the built-in follow-up logic.
Settings that limit exposure when the bot gets it wrong
Response Style controls output length without adding another instruction to the prompt. The available targets are Concise at approximately 30 words, Balanced at approximately 80 words, and Detailed at approximately 200 words. These are targets, not hard caps. The setting works with Form-Based, Prompt-Based, and Flow-Based bots, and competing word-count instructions make output less predictable.
The maximum generated-message setting accepts a value from 1 through 100, with 100 as the default for new bots. Only bot-generated messages count. Inbound contact messages, workflow messages, and human replies do not. The same limit applies across all enabled channels and cannot be configured separately for SMS, email, or chat.
When the limit is reached, the bot becomes dormant. It can be reactivated by marking the conversation Read or by using the Update Conversation AI Bot and Status workflow action. Because every generated reply counts toward usage, the message cap controls both conversation length and AI consumption.
Advanced settings also include minimum and maximum response delays, a Fallback Message, Content Filters, and Auto-Escalation. A 2–5 second minimum delay is the documented range for imitating human reading time. The fallback should say that the bot does not have a reliable answer and specify what happens next. Auto-Escalation can assign the conversation to a person when the bot reaches its limit or detects frustration.
Content Filters block designated words or phrases. They are a final barrier, not a correction for a poor prompt or inaccurate Knowledge Base. If a prohibited term appears throughout the training material, fix the source as well as adding the filter.
A test sequence that catches the expensive mistakes
- Confirm routing first. Test each enabled channel, destination, required tag, excluded tag, and direct bot assignment. A perfect prompt cannot correct the wrong bot being selected.
- Test known questions. Ask one question for each service, price, policy, and booking rule in the Knowledge Base.
- Test follow-ups and topic changes. Ask a question, request clarification, then switch to a new sales, support, business-information, or appointment topic.
- Test missing information. Ask questions whose answers are intentionally absent and verify that the bot uses the fallback or Human Handover instead of inventing an answer.
- Test CRM collection. Begin with empty fields, confirm each answer is written to the intended field, then repeat with those fields already populated to verify Skip if Already Filled.
- Test every permitted action. Complete an appointment booking, workflow trigger, transfer, handoff, and follow-up path that the bot is authorized to use.
- Test limits. Reach the generated-message cap, confirm dormancy, then verify the chosen reactivation method.
- Run the same set in Suggestive mode. Review drafts for factual accuracy, tone, action selection, repeated questions, unsupported promises, and failure to escalate before switching to Auto-Pilot.
Do not use a successful greeting and one correct FAQ as approval for Auto-Pilot. The failure cases reveal whether the bot has boundaries; the easy questions reveal only that it can restate available information.
What to do
- Set the bot to Suggestive mode and complete at least one test for lead capture, FAQs, appointment booking, unknown questions, and workflow behavior before enabling Auto-Pilot.
- Set Response Style to Concise, targeting approximately 30 words, during initial testing. Remove all separate word-count instructions from the custom prompt.
- Set the maximum generated-message limit to 20 for the first Auto-Pilot release. Raise it only after reviewing conversations that reached the cap.
- Set the minimum response delay to 2 seconds. Use 5 seconds when a slower reading-time effect is required.
- Enable Human Requested, Lack of Information, and Failed to Resolve Issue handoffs. Assign a user, pause the bot for 1 day, and create the task due 24 hours after the trigger.
- Use this fallback message: “I don’t have a reliable answer for that. I’m assigning this conversation to a team member.”
- Map every Information Collection question to its intended contact field and enable Skip if Already Filled for each mapped field.
- Create one required deployment tag named
ai_eligibleand one excluded tag namedai_excluded, then test both alongside any direct bot assignments. - Test Failed to Resolve Issue through two unsuccessful attempts and confirm the third step is human handling rather than another generated answer.
- If Transfer Bot is combined with Update Conversation AI Bot and Status, place a Wait step between them to prevent repeated reassignment.
Questions people ask
Why did the bot answer incorrectly even though the correct information was uploaded?
The bot also uses recent conversation context, instructions, goals, and other Knowledge Sources. Conflicting or outdated sources, an incorrect bot assignment, or a prompt that pushes the wrong objective can override the intended path.
Does Suggestive mode send anything to the contact?
No. It generates a draft for a team member to review and send manually.
What happens when the bot reaches its generated-message limit?
The bot becomes dormant. Mark the conversation Read or use the Update Conversation AI Bot and Status workflow action to reactivate it.
Does asking for a human automatically stop the bot?
The Human Requested scenario can trigger Human Handover. Configure the handoff to assign a user, send a final message, pause the bot, create the 24-hour task, and apply the human_handover tag.
Can one bot transfer a conversation to a specialist bot?
Yes. Transfer Bot preserves context, but both bots must be active on the same channel and in Auto-Pilot, and the destination bot should be published and tested.