Whatsapp

Hi HighLevel team, Following Meta’s WhatsApp pricing changes effective October 1, 2026, businesses are paying closer attention to how many messages they send. This makes it increasingly important to offer customers complete, interactive experiences within WhatsApp. HighLevel currently supports WhatsApp Flows for appointment booking through its calendar integration. However, Meta Flows can also be used for many other valuable use cases, including lead-generation forms, surveys, event registrations, product selection, customer-support intake, and quote requests. It would be extremely useful if HighLevel could support a broader range of Meta WhatsApp Flows, allowing users to create or import custom Flows, map submitted answers to contact fields, and trigger workflows based on Flow responses. This could help businesses collect information and guide customers through more of the process in a single interaction, reducing their reliance on multiple template messages and follow-ups where appropriate. It would also let HighLevel users take fuller advantage of the WhatsApp Flows capabilities available through Meta’s platform. Could you consider expanding WhatsApp Flows support beyond calendar booking? Thank you!

Problem: When selecting a WhatsApp template in Conversations, agents cannot see how dynamic variables ({{1}}, custom fields) render for the active contact before sending. This leads to blank fields, broken formatting, and wasted messaging costs. Proposed Solution: Add a preview modal/drawer upon template selection that: Renders the WhatsApp bubble with dynamic contact data resolved in real time. Flags missing or empty variables before dispatch. Allows inline text input to fill missing values manually before sending. Acceptance Criteria: Selecting a template displays an accurate preview (header, body, buttons). Variables populate automatically from the contact record. Missing fields are visually highlighted, disabling send until resolved or confirmed.

Customers currently have limited options for viewing and analyzing WhatsApp campaign performance in one centralized place. While individual workflow/message statistics may be available, it can be difficult to review historical campaign performance, compare campaigns over time, and understand how WhatsApp activity contributes to conversions and revenue. Proposed Enhancement Introduce a dedicated WhatsApp Campaign Analytics Dashboard that provides a centralized view of current and historical campaign performance. Additionally, consider GHL AI integration that could analyze campaign data and provide summaries or insights, such as identifying top-performing campaigns, engagement trends, conversion patterns, and opportunities for optimization. Expected Value This would allow customers to move beyond simply tracking the number of WhatsApp messages sent and create a clearer reporting journey: Campaign → Engagement → Conversion → Revenue/ROI A centralized dashboard would make it easier for agencies and businesses to understand which WhatsApp campaigns are generating meaningful results and use those insights to optimize future campaigns.

After a WhatsApp user adopts a username, the phone number will be masked. So when we chat with the contact, whether we manually ask for the phone number or are asked by the Conversation AI, it does not save the phone number to the phone field. The WhatsApp team said it can only be saved when we use a message template, but it is just not the right approach. On top of that, the AI cannot send a message template

Starting October 1st, Meta’s WhatsApp pricing changes will introduce new messaging costs for agencies and businesses that rely on WhatsApp. This could become a significant issue, especially for small and mid-sized agencies using HighLevel. Currently, WhatsApp API costs $10 in HighLevel, giving us access to options such as Cloud API or Coexistence API to connect WhatsApp. On top of this cost, we will now have to add Meta’s new messaging charges. My Proposal I believe HighLevel should remove the $10 WhatsApp API fee and make it free. Of course, agencies and businesses would still pay Meta’s actual messaging costs. However, removing the $10 fee would significantly help reduce the impact of this new pricing structure. We can also look at it another way: the $10 currently spent on WhatsApp API could essentially become $10 available for messaging costs instead. It may seem like a small amount individually, but for small and mid-sized agencies, every dollar adds up. Those $10 could help cover a meaningful portion of a client’s monthly messaging costs and help keep HighLevel competitive. Why Do I Think This Is Important? I personally work with five different agencies that use HighLevel, and this issue is already becoming a concern. The main problem is not simply paying an additional $10. The bigger issue is competitiveness against other CRMs and providers that charge little to nothing extra for similar WhatsApp API access. If, on top of our HighLevel subscription, we have the $10 WhatsApp API fee and now need to add Meta’s new messaging costs, the pricing gap between HighLevel and other platforms with simpler cost structures becomes increasingly noticeable. For agencies managing many clients, these costs add up. And this creates an important risk for HighLevel: some agencies may start considering moving to other CRMs where this additional $10 WhatsApp API fee does not exist. Not necessarily because $10 by itself is too expensive, but because once all the costs are combined and multiplied across multiple clients, the difference becomes significant. End clients also compare prices. If an agency using another CRM can provide a similar WhatsApp solution with fewer additional costs, agencies using HighLevel could find themselves at a competitive disadvantage. That is why I believe removing this $10 fee could have a much bigger impact than it may initially seem. Instead of paying $10 simply for access to WhatsApp API within HighLevel, that same money could be available to cover Meta’s messaging charges. In practice, it would be like giving each WhatsApp implementation approximately $10 of additional room for messaging costs. And although it may seem small, $10 + $10 + $10 across multiple clients can make a meaningful difference for an agency. HighLevel Has Made Similar Decisions Before HighLevel has previously made changes to reduce costs or make certain features more accessible to agencies. We have seen changes related to A2P, as well as tools and integrations with platforms such as Facebook, Instagram, and TikTok, which are part of the ecosystem without requiring us to continuously add new subscriptions just to use them. I believe WhatsApp deserves similar consideration. For many agencies outside the United States, especially in Latin America, WhatsApp is not simply another integration. It is one of our primary channels for sales, customer service, and follow-up. Making WhatsApp API Free Would Help: Reduce the impact of Meta’s new messaging costs. Keep small and mid-sized agencies using HighLevel competitive. Reduce the cost gap compared to other CRMs that do not charge a similar fee. Prevent agencies from considering other CRMs simply to reduce their WhatsApp costs. Make it easier for agencies to continue offering WhatsApp to their clients. Reduce friction when onboarding new clients. Keep more agencies and clients within the HighLevel ecosystem. Allow those $10 to go directly toward Meta’s new messaging costs instead. I believe this last point is especially important. If Meta is going to increase WhatsApp-related costs starting October 1st, HighLevel could help offset part of that impact by removing the $10 WhatsApp API fee. Those $10 could essentially become the first $10 available toward each client’s messaging costs. Individually, it may not seem like a huge amount, but those of us managing multiple accounts know that every dollar adds up. Most importantly, it could help prevent agencies that are currently happy with HighLevel from starting to look at other CRMs simply because they can offer WhatsApp at a lower overall cost. Instead of allowing Meta’s pricing changes to turn WhatsApp into a disadvantage for HighLevel, this could be an opportunity to turn it into a competitive advantage and demonstrate support for the agencies that depend on WhatsApp to operate and grow.

Extend the Social Planner to support WhatsApp Business Status (Stories) so users can schedule and publish content to their WhatsApp audience alongside Facebook, Instagram, TikTok, and other platforms — all from one dashboard. This would give businesses a unified content calendar for all their social channels including WhatsApp, saving time and ensuring consistent messaging across every platform where their audience is active.

Allow users to create, manage, and send messages to WhatsApp group chats directly from the CRM Conversations inbox. Businesses could group clients, leads, or team members and broadcast updates, follow-ups, or promotions — all tracked and logged inside the CRM. This would make WhatsApp group communication as manageable as individual one-on-one conversations already are within the platform.

Allow users to initiate and receive WhatsApp voice/audio calls directly from the CRM Conversations inbox. With WhatsApp already integrated for messaging, extending it to audio calls would eliminate the need to switch to the WhatsApp app to make calls. All call activity would be logged inside the CRM, keeping every client interaction centralized, trackable, and accessible to the whole team.

Since WhatsApp is natively integrated in the CRM, users should be able to initiate and receive WhatsApp video calls directly from the Conversations inbox — just like text messages. This would let businesses have face-to-face client conversations without ever leaving the CRM platform. Currently, integrated WhatsApp only supports messaging, but adding video call capability would make it a true all-in-one communication hub for sales and support teams.

Tested this recently trying to replicate an AI agent + WhatsApp automation setup across multiple sub-accounts for different real estate agents under one agency. Two separate problems, both add significant manual work per sub-account: The template often doesn't transfer at all when pushed via Snapshot, despite Snapshot documentation stating WhatsApp Templates are supported and auto-submitted to Meta for approval on import. In my case, the destination sub-account simply had no trace of the template after loading the snapshot, had to manually recreate and resubmit from scratch. Even in cases where the template does successfully copy over, it still has to be manually selected inside every individual workflow that references it, and the WhatsApp number for that sub-account also has to be manually reselected in each flow. So even a successful template transfer doesn't actually save the time it's supposed to, since the workflows still need to be touched by hand afterward. For agencies replicating the same system across many sub-accounts (in my case, multiple agents under one real estate brokerage, with more planned), this turns what should be a one-click snapshot push into hours of manual per-account cleanup, both fixing missing templates and rewiring every workflow. Requesting this be looked at as one combined issue: reliable template transfer on snapshot push, and automatic binding of transferred templates (plus the sub-account's own WhatsApp number) into any workflow steps that reference them, without manual reselection.