Whatsapp

Make WhatsApp Subscription Free Before Meta’s October Pricing Changes
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.
1
·
New Feature
URGENT: WABA stuck on previous Location and cannot be reassigned
I need urgent help from the HighLevel WhatsApp/LeadConnector technical team with a WABA-to-Location association issue that has been unresolved since September 3, 2026. WABA: Daniel Angiología Phone: +52 1 564 004 0818 WRONG / PREVIOUS LOCATION ID: FIeNTIwTLYotvgncpnhp CORRECT CLIENT LOCATION ID: OqrPOrmo4bQ9DhXRgnG HighLevel continues to show this error: “This WABA is already onboarded at location Id: FIeNTIwTLYotvgncpnhp” The previous Location has already been checked. There is no visible WhatsApp connection and no option to disconnect the WABA from that Location. Meanwhile, Meta shows the WABA and phone number as active and connected to LeadConnector. This issue has already been escalated through HighLevel Support and is documented under: Ticket #6281712 Related ticket #6290177 I have been requesting assistance through both chat and email since September 3. The case has been escalated and marked as high priority, but I continue receiving generic responses stating that the case is still in queue. The issue remains completely unresolved and is blocking a paid client implementation that must be delivered today, September 7, 2026. I am NOT requesting another onboarding tutorial. I do NOT want to create another WABA, change the phone number, or repeat the same troubleshooting steps. I need the WhatsApp/LeadConnector technical or backend team to review the WABA-to-Location association, release the stale association from the previous Location FIeNTIwTLYotvgncpnhp, and correctly associate the WABA with the client Location OqrPOrmo4bQ9DhXRgnG. The Conversation AI phone selector currently shows “No data” because the WhatsApp asset is not properly available in the correct Location. All relevant information and screenshots have already been provided to Support. Please have someone with actual backend access review this issue and provide a concrete technical resolution today. I do not need another generic escalation status. I need the underlying WABA-to-Location association fixed.
0
Load More