Whatsapp

Our clients use whatsapp communities to manage a lot of their business. It would be great to be able to manage, chat and maybe set up automations to integrate with whatsapp community.

Currently once verified, facebook side will show 2000/24hr message limit, but at our system it is still showing 1000/24hr

Request: In GoHighLevel WhatsApp messaging (outside of workflows), we currently can: Reply to an incoming WhatsApp message (only after the contact messages us), or Send a WhatsApp template to initiate outreach But when sending a template, the content is too rigid—there’s no clean way to input a custom message at send-time beyond fixed placeholders. This forces us to create lots of near-duplicate templates just to change the wording for different scenarios. What I’m asking for: When we choose a pre-approved WhatsApp template, add a “Custom Variables / Message Input” section where we can: Fill template variables with custom text (not just single-word fields) Optionally have a dedicated variable like {{custom_message}} that opens a larger text box so we can type a contextual message at send time Keep it compliant by still requiring the outbound initiation to use the approved template structure Example: Template: “Hi {{name}}, {{custom_message}} Reply YES to confirm.” At send-time, we type: “Just confirming your appointment is tomorrow at 3pm—can you make it?” Why this matters: Other WhatsApp providers support this model: you initiate with an approved template, but you can customize the variable content (including longer free-text) per send. This reduces template sprawl and makes WhatsApp outreach usable for real sales/support scenarios. Impact: Initiate WhatsApp outreach cleanly without requiring inbound messages first Fewer duplicate templates Faster, more human personalization at send-time Better sales + support operations Implementation (what GHL would likely build) Add a large-text input for one or more variables in template messages (e.g., {{custom_message}}) Allow multi-sentence variable values (within WhatsApp limits) Keep approval/compliance intact by not altering the template structure—only variable values

When you put Custom CRM Fields (example: {{contact.first_name}}) or Variable Fields in a META template, when an automation triggers the message, the CRM user sees the fields correctly, but the customer's WhatsApp sees only the variable without data “{{contact.first_name}}” CRM support said that they haven't done that implementation, so it would be nice to have

So having the buttons also available as internal notifications would easen some mannual tasks staff memebers have to do, example: I want to send an internal notification after an appoitnment asking "did the client arrive" if they click the "Yes" buttons then the next action in that branch would be "update appointment status to: showed" & the same if they didn't show. It would make it easier for the busy staff member, instead of going to the app and marking them as not shown + it would help to remove/add tags easier if client didn't show "update appt status to: no show" + add tag "no show client" to later ask for a pre-payment before the meeting. This would overall just ease the manual actions staff members have to do and not only that, we wont have to rely on them to mark them as no show or add tags mannualy, etc. Should be an extremely easy and fast addition since the internal notification is availble all we need is to have the buttons work as well as branches just like sending a regular message to a client.

Currently, GoHighLevel only allows one WhatsApp number per sub-account. This creates a major limitation for structured sales teams where each commercial agent operates with their own WhatsApp Business number. In B2B industries, especially international and relationship-driven sectors, sales agents build direct and personal communication channels with their clients. Clients save the salesperson’s number, not a generic company number. Forcing all users inside a sub-account to share one WhatsApp number breaks relationship continuity and reduces accountability. Because of this limitation, agents continue using their own WhatsApp accounts outside the CRM. As a result, conversations are not tracked, automations cannot be triggered properly, reporting becomes incomplete, and management loses visibility over communication. This directly impacts CRM adoption and undermines the purpose of implementing the system. The current structure works for small teams using a single business number, but it does not support scaling companies with multiple sales agents, regional markets, or international operations. A scalable solution would allow either one WhatsApp Business number per user login or multiple WhatsApp numbers within a sub-account assignable to specific users, while still giving administrators full visibility and control. For companies like SPATIUM PETRA GROUP, which operates multiple international entities with dedicated commercial agents per market, WhatsApp is the primary communication channel. Without per-user WhatsApp integration, CRM implementation becomes partial and fragmented. This is not a cosmetic improvement. It is a fundamental requirement for structured, growing sales organizations.

Let us send an internal notification via WhatsApp to the assigned user or follower via a WhatsApp message instead of a template, with the last reply from the contact, for example: {contact.whatsapp.message.body.reply} This would be very useful in many scenarios, like a restaurant, so we can send all the order information a Conversation AI agent collects directly to our client's WhatsApp numbers without incurring template charges.

It is necessary to be able to have several coexisting phones in each sub-account together with API cloud, which can be assigned as responsible for each number and even if the name of the user sending the message through WhatsApp appears. General improvements in the use of WhatsApp coexistence.

We need to be able to synchronize leads who initiate conversations with us through ads directly with the Meta Pixel so we can manage them through the CRM stages. This is similar to how it works when a customer submits a Facebook form or a form or survey from our sales funnel. A customer who sends a message through an ad should be considered a lead, and we should be able to manage them with the Meta Pixel.

Currently, when a WhatsApp Coexistence number gets disconnected from GHL, we don't receive any notification about it. This often goes unnoticed until clients start complaining that they're not receiving messages, which can damage our reputation and client relationships. By the time we realize the disconnection, we may have already lost important conversations and leads. Proposed Solution: Implement automated notifications (via email, SMS, or in-app notification) when a WhatsApp number becomes disconnected, similar to the notifications we currently receive when purchasing or connecting a new WhatsApp number. This would allow us to take immediate action and maintain uninterrupted service for our clients.