6th of October, 2026

Send number pool calls to multiple users who can answer it on any device they choose

What's new

You can now send number pool calls to several team members at once. Each person can answer on the device they prefer: web, mobile, desk phone, or their own phone number. Earlier, number pool calls couldn't be sent to specific team members' devices.

How it works

• Open a number pool's settings and turn on Ring Incoming Call to selected Users.

• Pick up to 6 team members. Each person's devices ring at the same time, using the ring channel they've set up.
• Your choices are saved and show up again the next time you open the pool.

Good to know

• You can choose the preferred device type of a user under Settings > Users/My Staff > Edit > Call & voicemail > Default channel for ring all.

• More about number pools and call tracking here.

Overview

You can now automatically add Internal Comments to conversations using Workflows. Until now, teams had to manually add internal comments to share context, provide instructions, or keep other team members informed. With this workflow action, you can automate internal comments based on specific events, ensuring important information is captured directly in the conversation without manual effort.

What’s New?

We've introduced a new Add Internal Comment workflow action that lets you automatically post internal comments to conversations when a workflow runs. You can use this to share important context, provide follow-up instructions, or notify specific team members by @mentioning users directly in the comment.

For example, when a high-priority lead enters a workflow, you can automatically add an internal comment mentioning the assigned team member with instructions for the next steps. These comments appear directly in the conversation history, keeping internal communication and customer context in one place without sending anything to the customer.

How to Use

• Go to Automation → Workflows.
• Create a new workflow or open an existing one.
• Add the Internal Comment action.

• Enter your comment and @mention team members as needed.
• Save and publish the workflow.

Why It Matters

This helps teams automate internal communication, keep everyone informed, and ensure important customer context reaches the right people at the right time.

Overview

We're excited to announce that snapshot and public API support is now available for all our recently launched custom field types (URL, Date & Time, Rich text, Users field, Image support in Radio and Checkbox fields – <a href="https://highlevel.canny.io/changelog/introducing-new-custom-fields" rel="ugc noopener noreferrer" target="blank”>https://highlevel.canny.io/changelog/introducing-new-custom-fields)

<a href="https://marketplace.gohighlevel.com/docs/ghl/locations/create-custom-field/" rel="ugc nofollow noopener noreferrer" target="blank”>https://marketplace.gohighlevel.com/docs/ghl/locations/create-custom-field/

Why it matters: Build more flexible integrations, synchronize custom field data with external applications, and automate processes without relying solely on manual updates.

Availability: Both snapshot and public API support are now live in production and available to all accounts. If you've already enabled the new custom field types through Labs, you can start taking advantage of these enhancements without any additional activation.

With snapshot and public API support now available, we're making custom fields more powerful, reusable, and easier to integrate into your everyday business processes.

Community posting just became more powerful for developers and integration partners.

You can now schedule and publish Community posts through the Social Planner Public API, including choosing which Community member the post should be published as.

This makes it easier for marketplace apps and custom integrations to bring Community publishing into their own workflows.

What's new

List Community Members

Integration partners can now retrieve eligible Community members who can publish posts.

• Search members by name
• Paginate through member lists
• Only active, permitted members are returned
• Private Communities return only members of that specific group

Validate Member Eligibility

Before scheduling a post, integrations can verify whether a selected member is still active and authorized to publish in the Community.

Publish as a Specific Member

When creating a Community post through the API, integrations can specify which eligible member the post should be published as.

Publish-Time Verification

Social Planner performs a final eligibility check before publishing. If the selected member has left the Community or lost permission, the post won't be published under the wrong identity.

Instead, the post fails with a clear and actionable error.

How it works

• Connect a Community group in Marketing → Social Planner → Settings → Social Accounts
• Use Get Accounts to retrieve the Community account ID
• Use Get Community Members to retrieve eligible members
• Select the member you want to publish as
• Create the post using the Community post API
• Optionally validate the member before scheduling
• Social Planner verifies the member again before publishing

Why it matters

• Enable Community publishing through marketplace apps and custom integrations
• Automate Community announcements from external workflows
• Ensure posts are always published by an eligible member
• Catch invalid member selections before publishing
• Get clear error messages instead of silent publishing failures
• Bring Community posting closer to API parity with other social channels

Notes

• Community account connection and management remain available in the HighLevel UI.
• The Public API supports member listing, member validation, scheduling, and publishing.
• Draft posts don't require a postAsUser selection.
• Member eligibility is checked when posts are scheduled or published.
• The selected member must remain active and permitted in the Community at publish time.
• API access requires the appropriate Social Planner scopes.

Marketplace API link – https://marketplace.gohighlevel.com/docs/ghl/social-planner/get-community-users/

🧭 Overview

Notifications for recurring appointments have been enhanced and now also work consistently across default and custom recurrence patterns. A recurring booking now sends a single confirmation that covers the whole series, and custom recurring appointments created in-app are now fully covered by notifications. Reminders and follow-ups continue for every occurrence, and for custom recurrences, notifications can show the recurrence details so recipients understand the full scope of a change.

🚀 What's New?

✅ One confirmation for the whole series

For default recurring appointments, the confirmation or unconfirmed notification now goes out once per booking and covers the entire series. Before: one was sent for each occurrence.

✅ Notifications for custom recurring appointments

Custom recurring appointments created in-app now send a confirmation or unconfirmed notification once per booking, covering the whole series. Before: no notifications were sent for these.

✅ Reminders and follow-ups for every occurrence

Reminders and follow-ups continue to be scheduled individually for each occurrence, and they now apply to custom recurring appointments as well. Before: they weren't triggered for custom recurrences.

✅ Reschedule and cancellation notifications for custom recurrences

• Custom recurring appointments now send these notifications, based on the option you choose when making the change.
• This appointment: a notification for that single appointment.
• All appointments: a single notification for the whole series.
• This and following: a single notification for reschedules.
• Default recurring appointments are unchanged, and these notifications stay specific to the affected appointment.

✅ Recurrence details in notifications

For custom recurrences, notifications now show the recurrence pattern alongside the specific date time, for example: October 14, 2026 12:00 PM (reoccurs every Thursday). This helps recipients see the full series when it's changed. Before: only the specific date was shown.

🧩 How to Use It

No setup needed. These enhancements are live automatically.

• This applies to: Any newly booked appointment, and any appointment that's edited.
• Default recurring appointments: Confirmation and unconfirmed notifications now go out once per booking, while reminders and follow-ups continue for each occurrence.
• Custom recurring appointments: Confirmations, reminders, follow-ups, and reschedule and cancellation notifications now apply, following the option you select when you make a change.
• Recurrence details: To include them, make sure your notification template uses the appointment date and time custom value.
• Scope: These changes apply to calendar notifications only. Workflows are not affected.

🎯 Why This Matters

• One consolidated confirmation per booking keeps communication for a recurring series clear and focused.
• Default and custom recurrences now share the same notification experience, so attendees get consistent communication however a series was created.
• Reminders and follow-ups for every occurrence keep each session on attendees' radar.
• Recurrence details help recipients tell at a glance whether a change affects a single appointment or the whole series.