Whatsapp

Problem: Meta's WhatsApp costs keep increasing, and the current rebilling model severely strains agency cash flow. Agencies must front usage costs, wait days for client reimbursement, and absorb 3-5% in Stripe and banking fees. Furthermore, clients push back against markups because Meta publishes its pricing publicly. Solution: Allow sub-accounts to attach their own payment method directly to Meta for WhatsApp usage, while HighLevel continues to manage the API connection and conversations. This eliminates agency financial risk, prevents fee erosion, and removes client billing friction.

Currently, when a team member replies to a contact from the WhatsApp Business App (using WhatsApp coexistence) instead of from HighLevel, no workflow is triggered, so automations that depend on a user reply do not run. This breaks processes such as stopping follow-up sequences, updating pipeline stages, adding tags, or pausing bots, and it can lead to duplicated or contradictory messages to the contact. We request a workflow trigger (or an extension of the existing reply triggers) that fires when a message is sent from the WhatsApp Business App, with a filter to identify its origin. This would keep automations consistent regardless of where the team replies from.

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.

Currently, users cannot select or create a destination folder while building a WhatsApp template; they must save the template first and manually move it into a folder afterward. Adding a folder selection/creation field directly within the template creation builder (matching the email template and campaign workflows) would streamline management and prevent unorganized template clutter.

To: Product & Engineering Team Dear Product Team, I am the Lead Systems Architect at FlowBridge Agency, a white-label enterprise deploying autonomous dispatch infrastructure for home service operators. We are actively onboarding multiple client sub-accounts on your platform, and I want to formally request a critical feature enhancement to the current phone number KYC (identity verification) flow. The Operational Bottleneck The current KYC verification process requires identity verification to be completed directly inside the platform's dashboard/chat interface. There is currently no mechanism to: Send a client a secure, external KYC verification link. Trigger an automated, white-labeled invitation email to a client when an agency initiates the process. Allow clients to complete verification independently on their own device. This forces agencies into one of two highly unscalable workarounds: Proxy Verification: Completing KYC on behalf of the client (which raises massive compliance and fraud concerns). Synchronous Friction: Scheduling a mandatory screen-share Zoom session per client just to complete a 2-minute Persona identity verification. For a white-label agency onboarding 10, 20, or 50+ clients a month, this is a severe operational choke point. The Requested Feature: Asynchronous Agency KYC Flow We request a dedicated, asynchronous flow that operates as follows: Agency Initiates: The agency inputs the client's details (Name, Email, Phone) and triggers a KYC invitation from the dashboard. Automated Invitation Fires: The client receives a clean, professional email containing: A brief explanation of why telecom verification is required. A checklist of required documents (e.g., Government-issued ID, selfie). A secure, time-limited verification link (e.g., 72-hour expiry) tied specifically to their sub-account. Client Self-Serves: The client clicks the link and completes the Persona identity flow on their own mobile device at their convenience. Status Webhook/Notification: Once the client completes (or fails) verification, the agency receives an automated dashboard notification and/or webhook with the result. Provisioning Unlocked: If approved, the agency is instantly unblocked to purchase and assign the phone number. Why This Matters (The Business Impact) This feature directly enables white-label agencies to deliver a frictionless, scalable client onboarding experience. Without it, the KYC step remains a manual bottleneck that slows down revenue-generating activations—not just for our agency, but for your platform's overall telecom volume. | Current State | Requested State | | :--- | :--- | | Requires live screen-share | Client self-serves asynchronously | | Agency bears compliance/fraud risk | Client legally verifies their own identity | | Unscalable for 50+ monthly clients | Fully automated, works at infinite scale | We strongly urge the prioritization of this feature in an upcoming sprint. I am more than happy to jump on a product feedback call with your engineering team to elaborate further. Thank you for your time and consideration. regards, Derric Yuh FlowBridge Agency

This should be no different to facebook, instagram, gmb (whatever it now is), tiktok etc and emails. WhatsApp should be included within the subscription cost!

We’ve connected WhatsApp to GoHighLevel using the API, which is great for automating one-on-one messages. But it would be extremely helpful if: Group chats were supported through the WhatsApp integration, especially for internal cleaner/staff communication. If there's a way to sync or access the same WhatsApp Business number from the mobile app, so we don’t lose flexibility while using automation. Right now, we’re forced to choose between automation in GHL or group chats in the mobile app — but not both. If this could be added, it would be a game-changer for businesses like ours that manage teams and need both automation and group communication. Please upvote if you’d also benefit from this!

The Lead connector doesn't have a button to send audios, I'm from Brazil and this is very common here, we really need to send audio via WhatsApp

Enabling webhook or API access to WhatsApp pin locations would unlock powerful, geo-aware automation capabilities across industries where on-site activity or movement matters. Key Applications Accurate address capture: Customers or staff can share their live location instead of typing details — ideal for service calls, deliveries, or field operations. Automated routing: Use coordinates to assign requests or leads to the nearest branch, technician, or representative. Proof of presence: Capture arrival and completion pins for verification, audits, or SLA reporting. Safety and assistance: Trigger workflows based on a user’s shared location (e.g., pickups, support, or emergencies). Operational insights: Build visual heatmaps or reports showing activity density, coverage, and efficiency.