GoHighLevel Latest Updates: November 2026 Level Up Guide

HighLevel added an AI agent section inside the chat widget settings for AI Studio websites. You can connect an existing Conversation AI agent, see the connected agent and its tag conditions, and open the agent for editing or disconnect it. This reduces the number of places you need to visit when checking which agent is attached to a website. It applies to live chat widgets. You still create and train agents in Conversation AI.

Open your AI Studio site and go to More → Chat Widgets → AI agent. Choose the agent and save. If you need to change its tag conditions, use the link back to Conversation AI. AI Studio connects one agent through this interface. The source release describes adding further agents from Conversation AI, so review the existing widget configuration before adding a second connection elsewhere.

A contractor might want the chat to answer basic service-area questions and collect a callback request. Give the agent an approved coverage list and a short set of questions. If a visitor describes work outside that list, give them a way to ask a person. The useful outcome is a reliable handoff the office can act on. Avoid asking the chat to promise a same-day visit unless it can verify that availability.

Test before publishing

Open the public page in a fresh session, then test as a known contact whose tags meet the routing conditions and one whose tags do not. Ask a normal service question, an unfamiliar question and a question that should go to a person. Verify who receives the conversation and what happens after business hours. If you swap the agent, run the same cases again. Our website chat handoff guide goes deeper on the human side of this flow.

Official HighLevel release note ↗

The AI Studio Payments panel can now manage more than 100 products from your store. The product picker moves through the catalog in pages, marks items already added and can select a whole page for a bulk addition. The list of attached products loads in pages and supports search. For a team maintaining a large assortment, the improvement is mainly in how it selects and manages products inside the builder.

Two limits still matter when you design the buying experience. HighLevel says the checkout setting labeled “All products” offers buyers the first 100 products. To sell products beyond that set, choose the products for that checkout or link to individual product pages. The storefront product list shows up to 500 products, with storefront search covering that same list. The builder’s ability to attach items and the shopper’s ability to find them are separate checks.

Imagine a store with 250 items, including a seasonal product that falls outside the first 100. Attaching the catalog in AI Studio may be easy, but a campaign link should take shoppers to an appropriate product page or a checkout with the relevant item selected. If your business advertises a limited collection, a curated checkout can also help customers confirm that the offer they clicked is the one they are buying.

Test the purchase path

Use a small list that includes an early item, an item beyond 100 and a product from the campaign. Search for each as a shopper, check the price and variation, and run a test purchase through the relevant checkout. Recheck the order record, confirmation and receipt. HighLevel says existing sites and checkouts continue to work without action. Prioritize testing the pages where you want to use the expanded catalog.

Official HighLevel release note ↗

HighLevel updated its time zone handling for four named regions. Its release note says America/Vancouver is now selectable and stays at UTC−7, America/Edmonton stays at UTC−6, America/Winnipeg stays at UTC−5, and Africa/Casablanca uses UTC+0 under the rules it implemented. The update applies in places where these time zones are used, including scheduling, notifications and profiles. Treat these details as HighLevel configuration information when auditing the account.

The important migration detail is that HighLevel does not automatically replace existing settings or contact records that use a US zone as a substitute. A Vancouver account using Los Angeles as a proxy can therefore continue applying the wrong clock rules after the change. Correct the zone for the location or contact it belongs to, and preserve US settings for US operations and contacts.

Start with the location time zone in Business Profile and review the calendars and workflows that rely on it. Identify whether appointment reminders follow the account, the calendar or the contact for your particular setup. Then review relevant contacts that still have a substitute time zone. A mixed-country account needs a targeted review of the records affected, with a way to track what you changed.

Test the clock at each step

Book a test appointment and compare the slot selected, the time shown on the confirmation page, the reminder and the event in an external calendar. Repeat the test for a future appointment around a clock change, or use an existing test contact configured with a regional zone. Check rescheduling too. If staff handle appointments across time zones, write out the customer’s local time in the test notes. The calendar can look correct to staff while a customer-facing message still uses the old setting.

Official HighLevel release note ↗

HighLevel moved the Facebook integration onto its Marketplace architecture and added support for connecting multiple Facebook accounts to a single sub-account. Each authorized account can have access to multiple Pages. The supported multi-account use cases in the release include lead sync, messaging across Pages and supported automations. The update is particularly relevant when one business manages several Pages through different authorized Facebook accounts.

The documented setup starts in Labs with the feature for Facebook Marketplace migration and multiple account support. Then go to Settings → Integrations, select Facebook, connect the additional account and choose the Pages you are authorized to use. Availability depends on the permissions granted in Meta. HighLevel says existing connections are being migrated and that users do not need to disconnect them manually to start the process.

Check the scope before planning an agency-wide rollout. The release says Shops and Ad Accounts still support a single Facebook account. It also describes unifying Facebook connections with Social Planner as future work. If you are managing unrelated clients, keep your client and permission boundaries in mind. One sub-account can technically hold several connections, but each lead and conversation still needs to reach the people authorized to handle it.

Prove the route from each Page

For every Page you add, submit a controlled lead and send a test message. Check the source field, contact record, assigned user and the automation that follows. Include a repeat lead in your test so you can see whether the team receives one useful record or two competing tasks. Use an account map that names the authorized owner, Page, form, pipeline and expected responder. If something fails, that map will help you isolate the affected connection.

If lead sync works but the next action never runs, use our GoHighLevel workflow troubleshooting guide to check the trigger and workflow history.

Official HighLevel release note ↗

HighLevel recommends GPT-6 Sol for prompt-based Conversation AI agents and sets it as the default for new agents of that type. Most existing agents retain their selected model. HighLevel separately says that agents using the deprecated GPT-5 and GPT-5 Mini models have moved to GPT-6 Sol. It also advises teams with GPT-4.1 agents to move them ahead of that model’s retirement in Conversation AI.

In its own evaluation, HighLevel reported a 98.4% pass rate for GPT-6 Sol versus 96.3% for GPT-4.1, at about the same cost per reply in its comparison. Treat that as a product benchmark. Your agent’s results depend on its instructions, the business information it can access, the questions visitors ask and whether it follows your handoff rules.

For an existing prompt-based agent, open AI Agents → Conversation AI, select the agent, then review the Model menu on the Build tab. Record the current settings and test responses before switching. Select GPT-6 Sol and use the available agent testing controls to compare replies. When the agent handles active lead conversations, start with a test agent or a lower-risk workflow and agree on when the team will review results.

Run a repeatable comparison

Choose ten questions your team already sees. Include pricing, coverage, appointment changes, a request the business does not handle and one that should go straight to a person. Score each reply for factual accuracy, the next step it offers and whether the agent stayed within its authority. Repeat a few ambiguous prompts to see how consistently it responds. Check that a human still receives the correct record after escalation. A reply that is fast and polished still needs to route the customer correctly.

Official HighLevel release note ↗

Field Services is HighLevel’s private beta for businesses that work at a customer’s location. It organizes work into requests, jobs and visits. A request can come from the booking page or a staff member. The office can turn it into an estimate or a job, schedule one or more visits, assign staff and track the billing attached to the job. Accounts admitted to the beta see a Field Services entry in the navigation.

The release describes a daily dashboard, a schedule with list, calendar and map views, and scheduling suggestions that consider working hours, service areas, existing bookings and travel. Dispatchers can review a proposed route before applying it and lock visits with fixed times. The module also covers service catalogs, add-ons, area rules, checklists, timesheets, invoices, notifications and a mobile workflow for field staff. HighLevel also describes a branded booking page, AI reception and Google organic booking as part of the module.

For a roofing company, an inspection, a return visit and the installation may belong to the same customer job. Keeping them together can give the office a clearer view of what was approved, what is still scheduled and what has been invoiced. An HVAC team might start with a maintenance job that has one technician and a known visit duration, then test the harder scenarios once staff understand the basics.

Pilot one job from start to payment

Set up one service area, one staff member and one service. Create a request from the customer-facing path, quote the job, book the visit, mark the visit complete and check billing. Add an out-of-area request and a reschedule. Verify what the office, field worker and customer each see. Keep your existing dispatch process in place during the pilot so staff have a fallback if a beta feature is unavailable. Use our roofing lead guide to decide where sales intake ends and scheduling begins.

Official HighLevel release note ↗

Community owners and admins can open Settings → Analytics to review community earnings, membership, inactivity, outstanding invitations, traffic and engagement. The date filter applies across the dashboard and defaults to the last 30 days. HighLevel says changes are compared with the preceding period of equal length when a comparison is available. The dashboard also shows activity by time of day and offers a CSV export for inactive members.

Interpret each card in terms of what it measures. Earnings reflect community-attributed transactions after refunds and chargebacks. Inactivity identifies active members with no tracked activity during the selected period. A member who has gone quiet may still be getting value through other channels or may simply be on holiday. Compare the metric with what your team knows before changing the offer or starting an outreach campaign.

If you run a coaching membership, try comparing two periods of the same length around an onboarding change. Look at when new members joined, whether they engaged, and how revenue moved over the same windows. If members are joining but rarely posting, test a smaller first step, such as introducing themselves or completing one short exercise. Use the activity heatmap to choose a time to try a live session and review attendance afterward.

Pick one question before opening the dashboard

For example, ask whether new members are taking part in the first month. Compare equivalent time ranges and write down changes to campaigns, event frequency and membership size. Then select one adjustment you can review on the next pass. If you export an inactive member list, use only the fields your team needs and keep the outreach relevant. A message that points to a specific upcoming session gives someone a better reason to return than a generic reminder to log in.

Official HighLevel release note ↗

Private channels can now appear in the community sidebar as locked channels. Members can see the name and description of a visible private channel before joining, while access to posts stays restricted. Hidden channels remain available for groups that should stay out of the sidebar for non-members. Admins can offer a private channel for free, charge once or set recurring monthly or annual pricing.

During channel creation, choose Private, then select Visible or Hidden. Write a description that explains who the channel is for, what members get and how often the team will add material or respond. Set the price, currency and billing option if the channel is paid. The release describes a payment flow that members can start themselves on the web or mobile. Test Mode lets you validate the payment path before accepting real payments.

A community for home service owners could keep its general discussions open to members and offer a private channel for monthly job costing reviews. Before making it visible, decide what happens when someone joins between sessions. Give them a clear first step and explain whether recordings or previous examples are part of the offer. That reduces questions your team would otherwise answer individually.

Test access with different member accounts

Check the sidebar as an existing member who has not paid, then use the test purchase flow and verify access. Test on a phone and a desktop. For recurring offers, confirm how your setup handles membership changes and what the customer sees when billing or access changes. Review what an existing participant sees if you update an established channel. If you plan to bundle this channel into a higher membership tier, test both purchase paths and explain how the offers relate on the sales page.

Official HighLevel release note ↗

A community can now present several membership plans under Settings → Subscriptions. Plans can include selected private channels, paid events, and paid or private courses. The release lists weekly, monthly, yearly and one-time billing options, optional free trials and support for multiple currencies. Admins can arrange and highlight plans. Members can compare them, see subscription details and switch plans. HighLevel says the existing subscription stays in place until the replacement is confirmed.

Start with an access map. List each channel, event and course in one column, then mark which plan should include it. Review the access options and use the benefits section to explain what members get in everyday terms. If two plans differ by one course, make that difference clear before checkout. HighLevel’s release describes configurable free-plan benefits as forthcoming, so verify free tier behavior before building an offer around it.

This is useful when the offer involves several related benefits. A course creator could sell a plan that combines a private discussion space, a set of lessons and a live event. A standalone paid channel is a better fit when the offer is simply access to one conversation space. When a single channel is sold separately and also appears in a plan, explain the two routes so a member can tell which purchase covers it.

Test the member journey before launch

Create a test member for each plan. Verify access to included items and confirm that items outside the plan remain restricted. Switch from one plan to another and compare what the member sees before confirmation and afterward. If you offer a trial, check the language around billing and access at the end of the trial. Keep a support note that explains who can help when a member thinks they have paid for something they cannot open.

Official HighLevel release note ↗

HighLevel’s Quizzes builder can now redirect respondents to a destination URL based on configured conditions. In addition to answer-based conditions, the release describes four quiz-specific score fields. You can route by overall score, the score in a particular category, the highest scoring category or the lowest scoring category. The destination can be a landing page, an educational resource or a booking page suited to the result.

Start by defining the visitor’s next useful step. A contractor readiness quiz might route someone with a planned project and a near-term schedule to an inspection request. Someone in an early research phase could go to a guide on preparing for an estimate. Use the quiz to explain what the visitor can do next and avoid implying that a score confirms pricing, capacity or service eligibility.

Set up the destination pages before adding rules. Write the conditions in a small table, include the expected destination and decide what should happen when no special condition applies. The release is for redirect logic. HighLevel lists custom messages, disqualification and show or hide logic as planned additions. Build your first version around the behavior available in the account today.

Check edge cases as well as the happy path

Submit a result below, exactly at and above each score boundary. Test a tie between categories, a response that matches overlapping rules and a response that matches none. Observe which path actually runs and adjust your conditions if the result is unclear. Open each destination on mobile and verify the links and booking forms. If the quiz passes into an existing workflow, submit a controlled response and confirm that the CRM and follow-up still behave as intended.

Review the destination pages with our GoHighLevel landing page design guide, especially when one quiz directs prospects to several offers.

Official HighLevel release note ↗