HighLevel updates for Sep 28-Oct 2, 2026: Muse, Voice AI and generated sites

Muse connects an external agent to the CRM

HighLevel is an official Muse app and reports more than 600 operations across 38 domains through MCP connections. OAuth limits access to selected sub-accounts and scopes.

Agencies should begin with minimum permissions and reversible tasks.

Prompting becomes the new starting point

Voice AI turns text or dictation into a conversation graph and offers a review mode. Ask AI applies the same pattern to funnels and sites before opening the visual editor.

The main saving is the first draft. Paths, copy, mobile rendering and tracking still require review.

Mobile calls and Meta budgets

The mobile app can call from a verified existing number, lowering initial cost and retaining familiar caller ID.

Ad Manager adds campaign or ad-set budgets and an option for Meta to shift up to 20%. Test that flexibility on limited spend first.

Three risk levels that should not be confused

A generated site draft is easy to discard. A mobile call reaches a real prospect. A Muse action may change CRM data or trigger a process. These capabilities should not share one permission level.

Voice AI and Ask AI need review checklists for logic, accuracy, compliance, mobile rendering, data capture and conversion events. A preview speeds production but is not quality assurance.

For Muse, separate reading from writing and add operations gradually. For Ad Manager, pair budget redistribution with a stop threshold so automation cannot accelerate poorly calibrated spend.

The decision this development should support

The real question is not whether the demonstration looks impressive, but whether to adopt conversational interfaces where they remove a specific friction without unnecessarily widening permissions. That wording starts with an operating problem and an expected outcome. It prevents a team from adopting a capability merely because it is new or prominent in the HighLevel ecosystem.

Before deciding, the agency should document its baseline: current tools, cost, volume, human time, error rate and conversion. Without that snapshot, a smoother experience can be mistaken for an economic improvement even when it has only moved work from one place to another. The baseline also gives the team a clear reason to keep, revise or stop the experiment.

The evidence worth requesting

Useful evidence includes time saved, required corrections, reversed actions and final-output quality. Define every indicator before the trial, name its data source and assign an owner. Building the dashboard afterward makes it too easy to select the figures that support the preferred story.

Activity and outcome metrics should remain separate. Sent messages, produced content and automated actions describe volume. Qualified conversations, attended appointments, margin, net time saved and incidents describe business effect. Both levels matter, but they answer different questions.

A trial small enough to teach

A sensible starting point is one Ask AI draft, an isolated Voice AI flow, a read-only Muse action and a small Meta budget. Give the trial a duration, budget, owner and stop rule. Record manual interventions as well, because automation that requires invisible correction can look efficient while consuming more resources than the previous method.

Where possible, keep a comparable group on the old process. Follow the difference through the entire journey rather than stopping at the first click or reply. A top-of-funnel lift loses value if quality falls, support demand rises or sales fail to follow.

Limits that belong in the operating process

The central boundary is that generating a preview, calling a prospect and writing to the CRM carry three different risk levels. Turn that statement into permissions, procedures, messaging and quality checks. A caveat in an article protects nobody if it disappears during implementation.

The final decision may be yes, no or conditional. Adopting for one segment, waiting for a stronger integration or declining when control costs exceed the gain are all valid outcomes. A useful development is not one every agency enables, but one whose role, cost and safeguards can be explained.