WhatsApp – Audio and Image Issue
A
Aquiles Casabona
We are currently facing a significant problem with our clients: many of them want to stop using GHL’s WhatsApp and migrate to other platforms because GHL still does not offer essential features they consider indispensable.
At the moment, we already have several improvement requests, but there is no set date or specific action to address these issues. It is crucial to include in GHL’s roadmap solutions that allow:
Audio and image interpretation for messages received in conversations with leads, similar to what ManyChat already offers.
More contextual responses: currently, the system replies to each message individually, which harms the experience. A better approach would be to implement a 30-second timestamp from the last interaction, grouping all messages received before the bot’s reply to ensure more context and coherence.
Image interpretation: analyze the received image and respond based on the knowledge already available in the database.
Audio transcription and response: convert the audio into text and reply, even if at first the answer is sent in text format.
These features are already available in other tools and can be implemented using OpenAI resources integrated via N8N, for example, with Evolution Manage as the interface.
We urgently need these simple but high-impact solutions to prevent clients from leaving GHL in search of alternatives.
Log In
A
Abhishek Kumar
Aquiles Casabona Holman Alvarez .
These features will be supported by conversation AI in next 4-6 weeks .
contextual response - make the wait time before responding to 30 seconds , this is already supported .
whatever message comes in this time frame , the bot will reply to all at once .
One feedback - do you want to update contact fields from image ?
A
Aquiles Casabona
Abhishek Kumar I think we need to make this configurable, considering that some companies may want to have this information stored in a dedicated field, while others may prefer to keep it only in the message history.
H
Holman Alvarez
I completely agree, we have agent solutions that do not allow the interpretation of attachements because GHL does not include them in the body of the message when making API calls, this has led us to use third-party solutions that do not work properly and with the aggravating circumstance of being banned by Meta.