Browse docs and guides
Set up Community Agents in your GoHighLevel community
Install Community Agents for the GoHighLevel sub-account that owns your community. Launch it from GoHighLevel, connect the member portal, and test your agent privately before enabling replies.
On this page
What you need
- Permission to install Community Agents and manage billing in the relevant GoHighLevel sub-account.
- The member-facing community portal address. A public GoKollab discovery page alone is insufficient.
- A dedicated community member login for each AI identity, with access to the intended groups and channels.
- Accurate knowledge and instructions: a getting-started guide, frequently asked questions, course resources, and the situations that require a human reply.
Read the portal compatibility guide before connecting. Review the $47 monthly subscription and AI usage charges before subscribing.
1. Install and launch from GoHighLevel
Use Install in GoHighLevel and select the intended sub-account. Complete the Marketplace installation and subscription steps, then launch Community Agents from that sub-account. Your GoHighLevel session signs you into the app; you do not create a separate Community Agents account or checkout.
Install separately for each sub-account you want to use. Check the selected account before connecting a portal so its community access and billing belong together.
2. Connect the member portal
In the app’s Settings, enter the portal domain your members use to sign in. Open that domain in a browser and verify the AI member’s login can reach the intended community. A directory listing can describe the community without being its sign-in portal.
Use a dedicated member identity rather than a person’s everyday account. Confirm the member can see each group and channel you plan to enable.
3. Give the agent a clear role and knowledge
Add the AI identity, define its job, and supply the information it should use. Start with a narrow role, such as answering onboarding questions. Explain the preferred tone, which resources it may reference, and when it should leave the question to your team.
Example instructions
Help new members find the getting-started lesson. Answer from the supplied onboarding material. If the material does not answer a question, ask for clarification or direct the member to the community team. Do not promise refunds, account changes, or a guaranteed business outcome.
This is an example to adapt to your community, not a preset or a tested member conversation. See knowledge and response controls.
4. Preview before enabling activity
Test a real recurring question, an ambiguous question, and a question your knowledge does not cover. Check the factual answer, resource links, tone, and escalation behavior. Edit the agent’s knowledge or instructions and test again if the answer is incomplete.
- Can a member follow the answer without additional context?
- Does it avoid making up a lesson, policy, price, or product promise?
- Does it make the AI identity clear?
- Would your team be comfortable with this reply appearing publicly?
5. Choose scope, schedule, and actions
Choose the groups, channels, actions, schedule, and limits the identity may use. Enable only the activity you intend to monitor. Configured agents can reply to posts, comments, and direct messages. Optional reactions are off by default; creating posts is a manual action.
AI disclosure is enabled by default and can be changed in workspace settings. Keep disclosure enabled and identify the member profile as AI. Review early replies and adjust your configuration as needed.
Review insights and usage
Member Insights summarizes synced conversations and possible buying interest with evidence. A person should review the messages and decide whether to follow up. It does not automatically contact interested members. Read how to review Member Insights.
Review included allowance and overage in billing. Usage is metered at 4× provider cost; GoHighLevel handles additional charges through the applicable wallet. AI activity pauses if payment cannot complete.
Troubleshooting your first setup
| Problem | What to check |
|---|---|
| App opens in the wrong account | Return to GoHighLevel, select the correct sub-account, and launch its installed app. |
| Portal connection fails | Confirm the member-facing portal domain and test the dedicated login directly. Avoid discovery/listing URLs. |
| Agent cannot see a channel | Check the member identity’s group and channel permissions, then the agent’s allowed scope. |
| Reply uses the wrong information | Update conflicting or missing knowledge and preview the same question again. |
| Activity stops | Review enabled actions, schedule, limits, subscription status, and wallet funding before changing the agent. |
If a connection remains unclear, contact support@lcbridge.app with the portal domain, selected sub-account, and error message. Share credentials only through an agreed secure support process.
Set up your first agent
Install in GoHighLevel and begin with one recurring member question.
Install in GoHighLevel ↗