By Alpit Patel and the aibrevo team · October 17, 2026 · 9 min read
GoHighLevel Updates October 14 to 16, 2026: AI Studio Git Sync, WhatsApp Countdown Templates and Number Pool Calls
HighLevel's changelog for October 14 to 16, 2026 lists eight releases: GitHub sync, chat widgets and checkout options in AI Studio, a rebuilt WhatsApp template builder with per-contact media, WhatsApp countdown offer templates, number pool calls that ring up to 6 users, and correct ad-platform labels on number pool calls. What changed, what to check before you rely on it, and which workflows it can break.
Key takeaways
- October 15, 2026: AI Studio projects can sync with GitHub in both directions. HighLevel creates a private repository, pushes every saved version and pulls back commits made elsewhere. A new permission, Manage Git & download code, is on by default for every role.
- October 15, 2026: AI Studio checkout can hide or require the phone number and billing fields, and a two-step checkout saves the buyer as a contact before payment. Those new leads fire the Contact Created trigger, not Order Form Submission.
- October 15, 2026: WhatsApp limited time offer templates show a live countdown drawn by WhatsApp, with copy-code and URL buttons. The expiry is chosen at send time, so one approved template can run many campaigns.
- October 15, 2026: WhatsApp media headers can now point to a custom field, so each contact gets their own image, video or document from one template. The resolved value must be a public URL that Meta can download.
- October 16, 2026: number pool calls can ring up to 6 selected users at once, and call tracking now labels Facebook, TikTok, LinkedIn and Microsoft ad calls by platform. Both apply to new calls only.
HighLevel published eight changelog entries between October 14 and October 16, 2026. Three matter most to anyone running client work on the platform: AI Studio now syncs with GitHub and ships chat widgets and a two-step checkout, WhatsApp gained countdown offer templates and per-contact media, and number pools can ring a group of users and label ad calls correctly. The list below is what changed, followed by the points that can quietly break a workflow.
Checked on October 17, 2026 against HighLevel’s public changelog at ideas.gohighlevel.com. Dates are the changelog’s publish dates.
| Date | Change | Area | Act on it if |
|---|---|---|---|
| Oct 14 | Native live chat and email chat widgets in AI Studio apps | AI Studio | You build client sites in AI Studio |
| Oct 15 | Two-way GitHub sync for AI Studio projects | AI Studio | A developer or coding agent edits the same project |
| Oct 15 | Checkout fields and two-step checkout in AI Studio Payments | AI Studio | You sell through an AI Studio page |
| Oct 15 | Rebuilt WhatsApp template builder, plus per-contact media | You send invoices, tickets or personalised images | |
| Oct 15 | Limited time offer templates | You run deadline promotions | |
| Oct 15 | Gift card emails and texts translated by locale | Payments | You sell gift cards in more than one language |
| Oct 16 | Number pool calls ring up to 6 selected users | Phone | You run call tracking for a team |
| Oct 16 | Ad-platform labels on number pool calls | Phone | You report on which ads drive calls |
For the earlier part of the month, see GoHighLevel mid-October 2026 updates, which covers October 9 to 14.
What does the new GitHub sync do in GoHighLevel AI Studio?
It keeps an AI Studio project and a GitHub repository identical in both directions. According to HighLevel’s changelog entry, you connect a personal account or an organization from More, then Git, and AI Studio “creates a private repository for the project, pushes every version you save, and pulls back every commit made outside it.”
| Behaviour | What HighLevel says |
|---|---|
| What gets pushed | Every saved version: AI prompts, code edits, visual edits and restores |
| What gets pulled | New commits on the connected branch, automatically; Push now and Pull now are always available |
| Branch | Starts on main; you can switch, including to a new branch created on the next push |
| After a pull | A fresh preview builds in the background and you click Update preview when ready |
| If both sides moved | Choose Force push (AI Studio wins) or New branch (keep both) |
| Secrets | Pushes are scanned for AWS, GitHub, Stripe and OpenAI keys and private keys, and blocked if found |
| Supported projects | React (Vite) and TanStack Start |
| Commit author | GHL AI Studio, not your GitHub identity |
Why it matters. Until now an AI Studio project lived inside HighLevel. With sync, an agency can hand the same project to a developer or a coding agent in another editor and have the changes land back with a fresh preview. HighLevel names Claude Code, Codex, Cursor, Copilot and Gemini CLI as examples. It also means client source code can now leave HighLevel, which is why the permission below is worth checking today.
The permission to check. A new permission called Manage Git & download code controls Git access and code downloads. HighLevel states it is “on by default for every role, so nobody loses access.” If your agency does not want every sub-account user able to export a project, turn it off per user under Settings, Team, Permissions, AI Studio. Users without it lose the Git tab and the download options and keep building, editing and previewing. Only the connected branch syncs, and projects that never connect GitHub see no change.
What changed in AI Studio chat widgets and checkout?
Chat widgets arrived on October 14, and checkout options on October 15. Both build on HighLevel features you already use, which is why they need little setup.
Chat widgets. Ask AI Studio to add a live chat and it creates a real HighLevel chat widget in your account, styled to match the site. HighLevel’s entry lists Live Chat and Email Chat, secure visitor sessions that never touch your app’s code, a captcha when the chat suspects a bot, rate limits and your widget’s spam settings, file attachments within the supported types and sizes, and business-hours rules. Every message lands in Conversations like the standard widget, and a new Analytics, Chat Widgets view shows loads, opens, open rate, ratings and a table of leads with the page each chat started on. Voice chat, WhatsApp, Facebook Messenger and Instagram chat widgets are not supported in AI Studio yet.
Checkout. The checkout entry adds three things:
| Option | What it does |
|---|---|
| Checkout fields | Show, hide or require phone and each billing address field; name and email are always required |
| Two-step checkout | Step 1 saves the buyer as a CRM contact, step 2 takes payment, so abandoned checkouts are still leads |
| Order details | The confirmation shows order ID, items, taxes, total paid and the next charge for subscriptions, or sends buyers to your own thank-you page |
Projects already using Payments get this on their next prompt, with no reconnect.
The trigger that changes. HighLevel flags this itself: new leads from a two-step checkout fire the Contact Created trigger, not Order Form Submission. If your follow-up workflow listens for Order Form Submission, an abandoned two-step checkout will never start it. Check the trigger before you switch a live page to two-step.
What are WhatsApp limited time offer templates and dynamic media?
They are two separate WhatsApp changes from October 15, and both remove a Meta approval cycle.
Limited time offer templates. HighLevel’s entry describes a Marketing template type with “a live countdown clock inside the message itself, drawn by WhatsApp.” The discount code sits under the clock and copies with one tap, with a URL button beside it. Meta requires both buttons, so they cannot be removed. The expiry is set when you send, not when you build, so one approved template runs campaign after campaign. It works from conversations, bulk actions, workflows and calendar sends, and the AI template writer can draft one. Build it under Settings, WhatsApp, Templates, Create template, with Category set to Marketing and Type set to Limited time offer.
One thing to watch. If you send with an expiry that has already passed, Meta still accepts the message and the chat shows the offer as expired. Check the date before a bulk send.
Rebuilt builder and dynamic media. The second entry replaces the template builder with one layout and a live phone preview, and the AI template generation and the builder opened from Reputation now use it too. The larger change is that a media header can accept a custom field or dynamic value instead of one fixed URL. The value resolves per contact at send time, so a single approved template can carry each contact’s invoice, ticket or personalised image. It works in workflows, conversations, bulk actions, calendar appointments, reputation review requests and missed call text back.
| Setup step | What to do |
|---|---|
| Store the file | Put a public HTTPS URL in a contact custom field |
| Map the header | Choose that custom field in the template’s media field |
| Send | Run it from a workflow, bulk action or conversation |
| Requirement | The resolved value must be a public URL that Meta can download; private Drive links, links behind a login and empty fields fail |
HighLevel says an invalid or empty value fails clearly instead of sending the wrong file. For the account-level basics, see does GoHighLevel work with WhatsApp.
What changed for GoHighLevel number pool calls?
Two things, both on October 16, and both apply to new calls only.
Ring several users. In a number pool’s settings, turn on Ring Incoming Call to selected Users, then pick up to 6 team members. Each person’s devices ring at the same time, using the ring channel set under Settings, Users or My Staff, Edit, Call & voicemail, Default channel for ring all. Each person can answer on web, mobile, a desk phone or their own phone number. Before this, HighLevel says number pool calls could not be sent to specific team members’ devices. The changelog entry says your choices are saved and show again when you reopen the pool.
Correct ad-platform labels. Calls from Facebook ads that used to show as Facebook or Direct now show as Facebook Paid. The second entry adds TikTok, LinkedIn, Microsoft (Bing) and Google ads clicked in apps, and any link with utm_medium=cpc is labelled platform plus Paid, such as Bing Paid. Visits from ChatGPT and similar tools appear as their own source.
| Rule | Detail |
|---|---|
| Setup | None; the number pool tracking script updates on its own |
| History | Past calls keep the source they already had |
| Still Direct | Some calls remain Direct when the browser hides the referrer and the link has no tracking code |
| Several tracking codes | The first match wins: Google, then Facebook, TikTok, LinkedIn |
If you report call volume by source to clients, expect a visible step change in your Facebook Paid count from October 16. It is a labelling fix, not a jump in calls. Our guide to missed call text back covers the phone system side.
The two number pool entries carry “6th of October, 2026” in their body text, while the changelog lists them as published October 16. This page uses the changelog publish date.
What this means for you
- Agency owner: decide who may export client code. Review the Manage Git & download code permission today, since it defaults to on.
- Anyone using two-step checkout: point follow-up workflows at Contact Created before you switch a live page.
- WhatsApp senders: build one limited time offer template, then check the expiry date before every bulk send.
- Call-tracking clients: note October 16 in your reports so the Facebook Paid change is not read as growth.
- Not urgent: localised gift card emails and texts translate automatically by locale, with previews that match, so there is nothing to configure.
If you want a second pair of eyes on how these fit your account, book a free 30-minute call and we will walk through it.
Sources
- HighLevel changelog, AI Studio: Git Sync with GitHub, published October 15, 2026.
- HighLevel changelog, AI Studio Chat Widgets, published October 14, 2026.
- HighLevel changelog, Checkout upgrades for AI Studio Payments, published October 15, 2026.
- HighLevel changelog, A rebuilt WhatsApp template builder, plus per-contact media and Limited time offer templates for WhatsApp, both published October 15, 2026.
- HighLevel changelog, Localized Gift Card Communications, published October 15, 2026.
- HighLevel changelog, number pool calls to multiple users and ad platform labels, both published October 16, 2026.
- All entries read in full on October 17, 2026.