Set Up a HighLevel AI Employee Steps 1 - 5
- The AI Employee feature must be enabled at the agency level before any sub-account can use it. Two places to check if it is missing.
- Your knowledge base is the single most important configuration decision. Garbage in, garbage out applies here more than anywhere else.
- The web crawler is the fastest way to populate a knowledge base if your website already has solid content on your services and FAQs.
- Start with knowledge base only in Step 5, then layer in appointment booking, contact capture, and call transfer as you get comfortable.
- A pre-configured snapshot can compress a multi-hour setup into minutes, with a working agent, knowledge base, and workflows already in place.
Where the Setup Actually Starts: Agency-Level Access
Most people who hit a wall on their first HighLevel AI Voice Agent setup run into the same problem: they cannot find the feature. The reason is almost always the same. The AI Employee capability lives at the agency level, and it has to be turned on there before it shows up anywhere inside a sub-account.
If you are not sure which view you are in, look for a "click here to switch" prompt near the top of the screen. If you see it, you are inside a sub-account and need to use that switcher to get to agency view. From there, navigate to Settings, then AI Employee, find your sub-account in the list, and flip the toggle on. If you still do not see the AI Employee option in that settings menu, there is a second place to check: Settings, then Company, then Basic Details, then Features. There is a master-level toggle buried there that controls whether the option appears at all.
It sounds like a minor thing, but this two-minute check saves a lot of frustration. Getting the feature enabled is the real Step 1, and everything else builds from it.
Creating and Naming Your AI Voice Agent with Purpose
Once you are back inside your sub-account, the path to creating a new agent is: AI Agents, then Voice AI, then Agent List, then Create Agent at the top right. You will be given the choice to start from a prebuilt template or build from scratch.
Templates exist for common use cases and can save time once you know what you are doing. For a first build, though, starting from scratch is worth the extra effort. When you wire everything together yourself, the logic of how the knowledge base connects to the goals, and how the goals connect to call-transfer rules, becomes intuitive in a way that following a template does not quite replicate.
Give your agent a name that signals its function clearly. "Sales Assistant" and "Front Desk Agent" are better choices than generic names because they set expectations for anyone on your team who later needs to edit the configuration. Small naming decisions like this matter more as you scale.
The Knowledge Base Is the Whole Game
Step 4 in the setup process is where most of the value is created, and where most under-built agents fall flat. The knowledge base is what your agent draws on when a caller asks a question. It will not speculate, and it will not reach outside the content you provide. That constraint is actually a feature: it means it stays accurate and on-brand, rather than improvising in ways that could mislead a prospect or create liability.
You have three options for loading content. The web crawler pulls text directly from URLs you specify. If your website has detailed service pages, FAQ sections, or pricing information, the crawler is by far the fastest option. The Morgan Systems snapshot, which is available as a free starting point, was built using the crawler across 27 URLs, and the resulting knowledge base was comprehensive enough to handle the majority of real caller questions immediately. Manual entry lets you add Q and A pairs and text blocks directly, which is useful for information that does not live on a public webpage. File upload handles PDFs and documents, which works well for rate sheets, menus, policy documents, or anything else that exists in a formatted file.
The content you want to prioritize: your most-asked questions, service descriptions with enough specificity to be genuinely useful, pricing or pricing ranges if you are willing to share them, business hours and location details, and common objections with your preferred responses. A knowledge base built around how your team actually answers calls will outperform one built around what you think callers might ask.
Agent Goals: Starting Simple and Building Up
After the knowledge base is built, Step 5 connects it to what the agent actually does. This is where you attach the knowledge base you just created, configure appointment booking and select the target calendar, define which contact fields to collect during the conversation, and set the rules for when a live transfer should happen.
The temptation at this stage is to turn everything on at once. Resist it. Start with knowledge base only. Get familiar with how the agent handles questions in test mode before adding appointment booking. Then add contact capture. Then configure call transfer rules. Each addition changes how the conversation flows, and troubleshooting is much easier when you have introduced one variable at a time.
Call transfer rules deserve particular attention. Defining clearly when the agent should hand off to a human is one of the most important decisions in the entire configuration. A rule as simple as "transfer if the caller asks to speak to someone" is a good start. You can refine it as you learn which calls actually benefit from a live conversation.
The Bigger Picture for Small Business
There is a version of this conversation that frames the technology as a cost-cutting measure. Fewer receptionists, reduced after-hours labor costs, leaner headcount. That framing misses what is actually interesting about this tool.
For a small business, the problem is rarely too many people answering the phone. It is the opposite: calls that go to voicemail during a meeting, prospects who do not leave messages and move on to the next search result, after-hours inquiries that sit in a queue until morning. It addresses a real gap, not a staffing redundancy.
When the AI Voice Agent answers a call, gathers the caller's name and interest, books them into a consultation slot, and routes the complex questions to your team, it is not replacing anyone. It is catching the lead that would have been lost. Your human staff still handles the conversations that actually require judgment, empathy, and expertise. It handles the intake and triage that nobody had bandwidth for. The person on your team who learns to configure and optimize these tools becomes more valuable as a result, not less, because they are operating with better information and more qualified conversations to work from.
This is what AI augmentation looks like in practice: not a replacement for the front desk, but a layer that makes the front desk more effective.
The Snapshot Option: When You Want It Running Today
For those who want to compress the setup timeline significantly, a pre-configured snapshot is available through the Morgan Systems demo page. Rather than building each component manually, the snapshot installs a working AI Voice Agent, a pre-populated knowledge base built from real-world content, and connected workflows directly into your HighLevel account.
The snapshot is paired with an extended 30-day free trial when you sign up through the demo link, along with live bootcamp training and 90 days of premium support including screen-share. For a business owner who wants to see the system working before committing to the full manual build, it is the fastest way to form a real opinion about whether the tool fits.
The full 12-step process, including chat widget installation, phone number assignment, live call testing, and workflow connections, is documented with screenshots in the setup guide linked above. Steps 1 through 5 covered here are the foundation; Steps 6 through 12 cover deploying the agent, and they are considerably easier once the core configuration is solid.
Frequently Asked Questions
Do I need agency-level access to set up the HighLevel AI Employee?
Yes. The AI Employee feature must be enabled at the agency level before it becomes available inside any sub-account. You toggle it on under Settings, then AI Employee in agency view. If you only have sub-account access, you will need to ask your agency admin to flip that switch first. There is also a master toggle under Settings, Company, Basic Details, Features that controls whether the option appears at all.
What is the knowledge base and why does it matter so much?
The knowledge base is the content your agent draws on when answering questions. It is what keeps the agent accurate and on-brand. Without a well-built knowledge base, the agent has nothing to work with and will either give vague answers or fall back on generic responses. Loading it with your FAQs, service details, pricing, and objection-handling content is what transforms a generic bot into a genuine business representative.
Can I use a prebuilt template instead of building my agent from scratch?
HighLevel does offer prebuilt templates when you create a new agent, and they can save time if you are in a hurry. That said, building from scratch your first time is worth the extra 20 minutes. It forces you to understand how the knowledge base, goals, and call-transfer rules connect, so you know what to adjust later when something is not performing the way you want.
Will this AI Employee replace my receptionist or front desk staff?
No, and that is not the right frame for thinking about it. The agent handles calls that would otherwise go to voicemail or get missed entirely. It answers questions, qualifies callers, and books appointments, then routes complex situations to a real person. Your team handles the high-value conversations; the agent catches everything that would have slipped through the cracks. It is a force multiplier, not a headcount reduction.
What contact information can the AI Employee collect from callers?
Inside the agent goals configuration you can specify exactly which fields to capture: name, email, phone number, service interest, and any custom fields you have defined in HighLevel. The agent gathers this conversationally during the call and writes it directly to the contact record, so your CRM stays current without any manual data entry.
How does the web crawler option work for building the knowledge base?
You provide the URLs you want HighLevel to crawl and the system pulls the text content from those pages automatically. It is by far the fastest way to get a knowledge base populated if your website already has detailed service pages, FAQs, or blog content. The Morgan Systems snapshot was built by crawling 27 URLs, which covered enough content to handle the most common caller questions right out of the box.
What happens if a caller asks something the agent does not know?
The agent stays within the boundaries of your knowledge base, so it will not fabricate answers. When a question falls outside its training content, or when call-transfer rules are triggered, it hands the conversation off to a live person. This is a feature, not a flaw. It means the agent stays reliable and on-message, while your team handles the edge cases that actually benefit from a human touch.