GHL Voice AI vs Hermes: 8 Things GoHighLevel Still Won't Do in 2026

GoHighLevel added voice AI. If you run an AI voice agency, that should matter to you. GHL sits inside the daily tool of most of your ICP, the GoHighLevel-native marketing agency owner who wants to add voice to their service stack. A capable voice layer inside GHL would close the gap between marketing automation and voice delivery, and GHL has been building toward exactly that: inbound AI agents, outbound calling campaigns, appointment booking, and a SaaS mode that lets agencies resell under their own brand.

The question is not whether GHL has voice AI. It does. The question is whether it has the voice infrastructure an agency needs when voice is the core product, not a feature add-on. After running this comparison against 20-plus agency stacks in early 2026, the answer is eight specific places where GHL's architecture creates hard walls. Here is each one, with the pricing math and the documentation to back it.

By builders, for builders. This is not a dismissal of GoHighLevel. GHL is exceptional at what it was built for: marketing automation, funnel building, reputation management, and CRM for marketing agencies. The gaps below are the gaps of a horizontal platform adding a vertical capability, not a failed product. But if voice AI is your agency's primary product, knowing where the walls are before you scale to 10 clients is worth 14 minutes.

Why does the GHL vs dedicated voice infrastructure comparison matter right now?

Because most agencies building on GHL in 2025 hit the same inflection point at the same client count. The stack works at two or three clients. The per-sub-account costs, the call caps, and the billing opacity become material at five to seven clients. At ten clients you are managing a spreadsheet of AI Employee subscriptions on top of a platform subscription on top of outbound per-minute charges, and the margin model you sold the first client on no longer holds.

The Automize 2026 GHL Voice AI guide notes that GHL's AI voice agent capabilities include appointment booking, inbound handling, and basic outbound campaigns, but flags that "accents and highly technical objections still trip up the Voice AI" and that agencies need clean human-transfer triggers for complex queries. That is a product limitation. The eight gaps below are structural, in the platform design itself.

1. The AI Employee cost stacks per sub-account, not per agency

This is the number that surprises most agencies when they model it out. GHL's AI Employee Unlimited plan, which covers inbound Voice AI among other AI features, costs $97/month per enabled sub-account. Not per agency account. Per client location.

The math at scale looks like this.

Compare that to Hermes Agency at $699/month for 20 workspaces and 2,000 included minutes, with no per-workspace AI subscription stacking. The platform cost difference at 20 clients is $1,738 per month before a single outbound call is billed. That is margin that disappears from every retainer you close.

2. Outbound voice AI is still pay-per-use even on the Unlimited plan

This one catches agencies who read "AI Employee Unlimited" and assume outbound is covered. It is not. Per the GHL AI Employee documentation, the $97/month Unlimited add-on covers inbound Voice AI under AI Employee. It does not cover Voice AI outbound phone calls or the Voice AI chat widget. Those remain pay-per-use at $0.13/min through LC Phone, plus phone system charges on top.

For an agency running outbound campaigns for clients, that means two cost layers: the per-sub-account subscription and the per-minute outbound charge. There is no included outbound minutes allotment at any GHL plan tier. Hermes includes 300 minutes Starter, 1,000 minutes Business, 2,000 minutes Agency, applied across all workspace types including outbound campaigns.

3. No per-client minute cap or auto-rebilling at the voice layer

One of the most-requested features on the GHL ideas board is the ability to set per-sub-account voice minute limits with auto-rebilling when the client exceeds the cap. In plain terms: you want to tell GHL "Client A gets 500 minutes, then charge them $0.20/min and bill it to my account." That workflow does not exist in GHL's Voice AI as of May 2026.

What exists is a global markup multiplier at the Agency Pro tier. You set a percentage, and that markup applies to all AI usage across all clients. You cannot set individual rate cards per client, cannot automate the overage invoice, and cannot give the client a self-service usage dashboard showing where they are against their limit. The practical result is that agencies managing this on GHL are doing it manually in a spreadsheet, which breaks at five or more clients.

"Without filtering, every robocall creates a fake contact in your CRM and can trigger automations, messing up your data and wasting workflow credits." [NextPhone, GoHighLevel Voice AI Alternatives 2026]

4. Hard outbound call rate and daily volume caps

GHL's outbound voice AI runs at a maximum of 10 calls per minute per location (one every 6 seconds), with a hard cap of 1,000 calls per day per sub-account, per the GHL Voice AI Outbound documentation. Each number can be called once per day, no more than 14 times in 14 days. Calls are restricted to 10am to 6pm in the contact's local time zone.

These limits exist for legitimate compliance reasons, and GHL is right to enforce them. But for an agency running a client with a list of 5,000 leads that need to be contacted in a 48-hour window, a 1,000 call-per-day cap across a single sub-account means the campaign takes five days at minimum. If you have five clients running concurrent campaigns, you are managing five sub-accounts each at their own cap, which requires five separate campaign dashboards and no cross-client visibility.

5. No dedicated voice CRM -- call data competes with marketing contacts

GHL's CRM was built for marketing automation: contacts, pipelines, deals, and the communication history across SMS, email, and chat. Voice call data is added on top of that model. The result is that every AI voice call creates or updates a contact record in the same CRM your client uses for their email campaigns. Inbound calls from numbers not already in the CRM create new contacts automatically, which means robocalls, spam calls, and wrong numbers generate contact records and can trigger automations.

For a marketing agency using GHL for email + SMS, this is manageable because the contact volume is intentional. For a voice agency deploying an inbound receptionist for a dental client handling 200 calls per week, the CRM fills with call records from existing patients, new inquiries, appointment confirmations, and spam, all in the same contact list as the client's email subscribers. Filtering requires manual workflow configuration per client, and the margin for error is high.

Hermes ships a voice-native CRM. Contacts are created from call data. Pipelines are structured around call outcomes (booked, transferred, follow-up scheduled, not interested). The data model was designed for how voice agencies actually use it, not retrofitted onto an email marketing contact list.

6. Rebilling markup requires Agency Pro at $497/month -- and is still coarse

Per the GHL Central 2026 pricing breakdown, rebilling with agency markup is exclusive to the Agency Pro plan at $497/month. The Starter plan ($97/mo) and the Unlimited plan ($297/mo) allow cost pass-through only, meaning you bill your client at the same rate GHL charges you. There is no margin to be made on the platform costs at those tiers. You must be on Agency Pro to mark up AI usage and keep the difference.

Even at Agency Pro, the rebilling model is a global multiplier. You cannot set Client A at a 40% markup and Client B at a 25% markup based on contract terms. One rate applies to all clients in the markup bucket. For agencies that close retainers at different price points, which is most agencies, this means the billing logic lives outside GHL entirely.

"GHL's voice AI only books appointments; you need one that also modifies and cancels." [NextPhone, GoHighLevel Voice AI Alternatives 2026]

7. Phone number WHOIS resolves to HighLevel's carrier account, not yours

GHL's telephony runs on LC Phone, GHL's wrapper around Twilio. When you provision a phone number inside a sub-account, that number is registered to LC Phone's Twilio account, not to your agency. A client who runs a WHOIS lookup on their agent's phone number, or whose tech team checks the carrier registration, will see the LC Phone or HighLevel entity, not your agency name.

This matters for two reasons. First, it is the same white-label leak problem we documented in the Vapi white-label audit. If your agency's pitch is that you built the infrastructure, a WHOIS lookup that surfaces HighLevel ends that claim in 60 seconds. Second, if a client wants to port their number out (whether they are leaving you or changing platforms), the number porting process goes through GHL's support, not yours. You are not the number owner.

Hermes numbers are provisioned to your agency's account. Number porting is handled through your workspace. If a client leaves, you port the number on your terms.

8. No single-platform view across clients for voice performance

GHL's agency-level view is built for the snapshot report: a high-level look at each sub-account's CRM activity, lead volume, and campaign performance. That view was designed for marketing agencies reviewing client results in a weekly report. It was not designed for a voice agency that needs to see, across all clients simultaneously, how many minutes were consumed this month, which agents have the highest call abandonment rate, which clients are approaching their included minute allotment, and which campaigns have the highest booking rate.

The Sympana 2026 GHL Voice AI cost breakdown notes that the pricing model complexity -- platform subscription, per-sub-account AI add-ons, per-minute outbound, phone system charges -- makes total cost of ownership "difficult to predict without careful planning." That is true. It also makes multi-client performance reporting difficult without building a custom view on top of the GHL API. That is a developer project, which is exactly the kind of overhead dedicated voice infrastructure is supposed to eliminate.

How does the full platform comparison look?

Side by side on the eight gaps above. This is not a complete feature comparison. It is the specific comparison for an agency where voice AI is the primary product, not a marketing automation add-on.

What is GoHighLevel actually good at for voice agencies?

Acknowledging the gaps honestly means acknowledging the strengths honestly too. GHL is genuinely excellent at three things that matter for a voice agency's surrounding workflow.

First, the automation engine. GHL's workflow builder connects voice call outcomes to SMS follow-ups, email sequences, pipeline stage moves, and webhook triggers in ways that are fast to configure and do not require a developer. If your voice agent books an appointment and you want the client to receive a confirmation SMS, a calendar invite, and a reminder 24 hours before, that is a 15-minute workflow build in GHL.

Second, the reputation management and review layer. GHL's review request automation, Google Business Profile integration, and reputation reporting are the best in the SMB automation stack. For a dental or HVAC client using Hermes for the voice layer, connecting GHL for review management on the back of each completed call is a legitimate architecture.

Third, the existing client base. An overwhelming share of the AI voice agency ICP already uses GHL for their marketing clients. The familiarity removes onboarding friction. If you are pitching a new voice AI service to a GHL-native marketing agency, you are pitching into a platform they already know.

The recommendation for most agencies in this position is not to abandon GHL. It is to use GHL for what it does well (automation, reputation, existing client relationships) and use purpose-built voice infrastructure for the voice delivery layer. Hermes and GHL are not mutually exclusive, and the agency that connects both via webhook is not duplicating costs -- it is using each tool at its intended scope.

What is the right move if you are currently scaling voice AI on GHL?

The decision point is client count, not frustration level. If you are at two or three clients and GHL's voice AI is handling your inbound and booking flow, there is no urgency to change. The per-sub-account cost is manageable, the outbound caps are not a bottleneck, and the CRM overlap has not become noise yet.

The inflection point hits reliably at five to seven clients, and almost always shows up the same way: someone on the team builds a spreadsheet to track per-client minutes because GHL does not show it. If you have that spreadsheet, you have found the wall.

At that point the options are three. You can build a custom reporting and billing layer on the GHL API, which runs $8,000 to $15,000 in developer cost and ongoing maintenance. You can accept the margin compression and treat the per-sub-account stacking as a cost of doing business. Or you can move the voice delivery layer to dedicated infrastructure where the billing, the CRM, and the campaign engine were built for exactly this use case from day one.

For the math on the move, the margin math post works through what agencies actually pay across Vapi, GHL, and dedicated platforms at 5, 10, and 50 clients. If you are coming from Synthflow, the Hermes vs Synthflow comparison covers the structural differences at each tier. And if you want to understand the full cost of a five-tool stack before deciding anything, the five-invoice problem post runs the numbers.

GoHighLevel is great for what it was built for. Voice AI agency infrastructure is a different product category. Knowing the difference before you scale is cheaper than learning it after.

Frequently asked questions

Where this leaves you

GoHighLevel's voice AI is a real product with real capability. The eight gaps above are not bugs -- they are the natural result of a horizontal platform adding a vertical feature. GHL was built for marketing automation. The voice layer is a capable add-on for agencies whose primary product is marketing automation.

For agencies whose primary product is voice AI service delivery, the math changes at five clients and breaks at ten. The per-sub-account AI stacking, the absent outbound minute allotment, the coarse rebilling model, and the lack of cross-client voice performance visibility are the specific walls. They are documented, they are on GHL's ideas board as open requests, and they are not shipping in the near term based on public roadmap signals.

By builders, for builders. Hermes is the platform that fills the gap. Not as a replacement for GHL in marketing agencies, but as the dedicated voice layer for agencies where voice is the core product. $149/month Starter for three clients. $699/month Agency for twenty. Fixed overage at $0.24/min. No per-client subscription stacking.