Whatsapp

WhatsApp Number 1 → Assign all chats to [Agent Name / Email] WhatsApp Number 2 → Assign all chats to [Agent Name / Email]

GoHighLevel (GHL) should significantly enhance its value by allowing businesses to integrate and seamlessly switch between multiple WhatsApp (WA) numbers for different departmental sections like Sales, Customer Service, and Billing, providing clearer communication channels and an improved customer experience by directing inquiries to the right team immediately. Furthermore, automating the transfer of conversations between these WA departments within the same GHL system for example, moving a sales chat that becomes a billing inquiry would streamline operations, reduce manual errors, and ensure a continuous and efficient customer journey with all relevant context preserved.

So the company I am working with has multiple numbers for the sales office, accounts office, and maintenance office. I am trying to set up the whatsapp automation for them but their is an issue that the whatsapp integration can only hold 1 whatsapp business number is there a way you can increase that limit and have multiple accounts in one subscription. because if not my client will have to pay for multiple sub accounts and multiple whatsapp subscriptions.

Currently, when sending a bulk WhatsApp message from the Contacts area, users must leave the workflow to create or edit a WhatsApp template. It would be much more efficient if we could create or edit WhatsApp templates directly from the "Send Bulk WhatsApp" screen, without navigating away. This would streamline the process for agencies and non-agency users running frequent WhatsApp campaigns and reduce friction for users. It will also reduce ERRORS as jumping between screens and workflows absolutely opens for errors. Benefit: Saves time for users sending bulk WhatsApp messages Reduces workflow interruptions Makes bulk messaging more accessible and efficient Reduces margins for error

You are missing add this new category, so a lot of messages can be flag as miss category and GHL dont have the funtionality to put the right category, Authentication content. You only have 2, Utility and Marketing but there is a third one missing that you need to add, you can check Meta documentation.

We use WhatsApp voice messages here in Latin America, and these messages can be long. Unlike the WhatsApp App itself, the LeadConnector app will stop recording a message if the display blacks out. Please fix. This might be a leadconnector app issue as well.

Dear GoHighLevel team, We are writing to you to request an improvement in the integration of the WhatsApp channel within the platform, in order to facilitate and optimize the use of this means of communication, so vital for the Latin American market. Currently, 99% of users in Latin America use WhatsApp as their main channel for business, and we have identified that many customers do not use the official API due to various limitations affecting their experience, such as: Official API restrictions: Limitations due to 24-hour inactivity rules and the need to use META-approved templates, which generates high costs for customers with a large volume of messages. High number rejection rate for the connection via the coexistence API, a problem that has been proven not to be present in the API without coexistence. Complexity in the current integration: The QR code connection, which many other CRMs in Latin America already offer (for example Whaticket or Kommo), allows for easier and faster integration, without the customer losing access to important functions, such as editing messages sent from the mobile app or direct access to the WhatsApp application on Windows or Mac. High costs of current options: It is very expensive for users in Latin America to pay between 40 and 50 dollars a month just to have WhatsApp functionality via QR code when using providers such as AppleVel, which limits their adoption and loyalty. Need for multi-user use with the same number: The impossibility of using several vendors or applications in the same number limits scalability and teamwork. For these reasons, we request that GoHighLevel consider implementing a QR code connection option for WhatsApp that is simple, fast and functional, and that maintains the essential features for a good user experience and multi-user support. We believe that this functionality would considerably increase customer satisfaction and would help to retain and attract new users who today migrate to other platforms due to these limitations. For example, despite being Meta partners, Kommo also has easy integration with QR. Thank you very much for your attention and we look forward to any questions or developments regarding this request. Other users are also asking for the same thing: https://ideas.gohighlevel.com/whatsapp/p/whatsapp-api-qr https://ideas.gohighlevel.com/ad-reporting-and-attribution/p/integracion-mas-sencilla-de-whatsapp-qr-code https://ideas.gohighlevel.com/ad-reporting-and-attribution/p/whatsapp-por-qr-code https://ideas.gohighlevel.com/whatsapp/p/whatsapp-web-connection-using-qr-code-by-scanning Kind regards,

cant use multiple wpp providors on a same phone number and i need a lot of users

HOW IT WORKS WITH STANDARD WHATSAPP: Using a standard whatsapp account you can add the whatsapp button to your facebook business page AND have it as an ACTION button for the viewers to contact about a post (see screenshot 1) When they click ACTION it prefills with the link to the facebook post (as a link) and defaults the WhatsApp message to 'Can I get more info on this?has' (see screenshot 2) When you click 'continue to chat' it opens whatsapp and starts a new message with the default text AND includes the link to the post. (see screenshot 3). When it's sent it's very clear to the recipient which facebook post they are referring to. (see screenshot 4) HOW IT WORKS USING GHL/WHATSAPP INTEGRATION If I have a facebook page using my GHL/LC WhatsApp number as the contact and action buttons, it appears to work in the same way (same as screenshots 1, 2, 3) BUT The message received in GHL does not bring through the facebook post link - it just has the text part of the whatsapp message - Which is not very useful as you don't know which facebook post it was referring to. (see screenshot 5) It's not even mentioned in the message details either (click 3 dots and select details) (see screenshot 6) Given in GHL we can create whatsapp templates with links, images, videos etc to send OUTBOUND - then hopefully it's not too much of a stretch to have the same link/attachment style support for INBOUND messages too (which come from the facebook ACTION button linked to GHL/LC/WA account) (see comparison 'screenshot 7)