Whatsapp

Whatsapp call are needed as it is the main form of contact abnd way to touch up base with latin population.

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!

Please add feature that every Staff member can have their own WA number to chat from wihtin GHL

Please, we want to schedule WhatsApp bulk action messages instead of sending them directly. Also, drip mode is important, similar to workflow bulk action.

Hello, I am a teacher specialized in automation and AI, and I use Go High Level (Agency plan) to create AI agents. However, I'm experiencing a major limitation because Go High Level doesn't pass message attachments (such as audios, videos, and PDF files) through the output webhook. This is essential for me to be able to integrate and process these types of media into my automation flows. I've tried using the variables {{message.attachments}} and {{ message.id }}, but they return empty. Specifically, due to the WhatsApp/Meta integration with GHL, I'm unable to use the webhooks provided by Meta itself. Even trying to solve this with inbound webhooks, it doesn't work, because I need to continue using the “Customer Replied” trigger in GHL. In addition, since the WhatsApp integration via Meta → Go High Level and the official WhatsApp Cloud API (with an app on Facebook Developers) cannot coexist, I can't work around the problem using the Meta API directly. In other words, I have to choose between creating and managing my own app on Meta to send and receive messages or connect via Go High Level. Using both simultaneously is not possible. What I need in the automation flow is very simple: Customer Replied → Outbound Webhook → I need all message parameters to be correctly passed on, including body, id, and attachments (audio, video, PDF). It should be noted that the attachments must be passed on as a media link, because if only the attachment ID is forwarded, I have no way of obtaining the file via the Meta API. This is because, when connecting WhatsApp to GHL via Lead Connector, it is not possible to use the Facebook Developers app to access the Meta API. I really appreciate the help in resolving this limitation, as it's critical for the AI agents and automation flows that I build on your platform. Thank you very much.

Specifically on WhatsApp, attachment URLs are not found in workflows or API. Urgent need, this makes us unable to process any kinds of attachment. I'm fine with paying $20 per mo for leadconnector's WA, but atleast make images available. Been using unreliable & unofficial WA integrations due to this issue..

It would be nice to reply contacts who send WhatsApp voice notes. It doesn't do anything right now.

I've been working on configuring Go High-Level to work with a local Indonesian number, as the option to purchase a number within GHL is not available. My research into Go High-Level's local competitors revealed that they suggest purchasing a local SIM card and registering that number with Meta prior to integrating it with their software. It would be beneficial if Go High-Level could adopt a similar approach, not only for Indonesia but also for other countries not covered in their phone number purchasing section.

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