Share your ideas to make Manychat better.
Ability to send files through Dynamic Content or the sendContent API endpoint for Whatsapp and Instagram.https://manychat.github.io/dynamic_block_docs/channels/#sending-files
Title: I will switch my entire business to ManyChat if you add "Agent Chat Privacy feature"Description:I am currently using a different WhatsApp BSP, but I want to migrate my entire operation to ManyChat because your automation tools are superior. However, there is one missing feature stopping me from switching.The Requirement:My sales agents work on commission. In my current platform, Agents will only see the customers they have successfully "picked" or been assigned to. In ManyChat, any agent can jump into another's chat and "steal" the commission. The Request:Please add a permission setting that:Restricts agent visibility to ONLY their "Assigned to Me" folder and Unassigned. Not All chats. Not chats assigned to fellow agents. Blocks(hided chats) from replying to any chat assigned to a different team member.My Commitment:If ManyChat adds this "Strict Assignment" or "Commission Protection" mode, I will immediately move my account and all my WhatsApp numbers over to your platform. This is a critical requirement for any sales team that operates on a commission structure.
Currently, part of the customer support workflow is handled directly through the WhatsApp mobile app by team members, outside of automated flows. This creates an important limitation: the system is unable to identify what was the last message sent by the company to a given customer, which negatively impacts automation continuity and context-aware decision making.This feature aims to enable the system to identify and retrieve the last outbound message sent by the company, regardless of whether it was sent via automation or manually through the WhatsApp app. By doing so, automations gain full conversation awareness, preventing duplicate messages, poorly timed follow-ups, or responses that conflict with recent human interactions.
Since the beginning of the year, Meta has released WhatsApp flows, the carousels on WhatsApp, and so far I haven't seen Manychat move to make this happen. When will we have access to these new features, and why does the tool take so long to update?
Context:We are integrating Manychat with our in-house CRM to create a unified and intelligent sales pipeline. Currently, we can capture basic lead data (name, phone number, tags, etc.), but there is no official method to retrieve the full conversation history between the user and the bot (or human agent).This limitation affects our ability to provide context to our sales team and to maintain proper records of interactions.Feature Request:We’re requesting a native action within Flow Builder or a dedicated API endpoint that enables us to retrieve the entire message history of a user — ideally in structured format (JSON or plain text), including all bot interactions and Live Chat messages.Use Cases: Provide full context to human sales agents when continuing conversations outside Manychat; Log conversations for quality control and auditing purposes; In the future, support emotional tone analysis and decision-making insights from conversation history. Why This Matters:This functionality would eliminate the need for complex workarounds and strengthen Manychat’s role as a central communication and sales tool. Businesses could operate with more continuity, precision, and accountability — enhancing the user experience and internal workflows.
Seria muito interessante uma função nativa que permita enviar automaticamente o boleto, a linha digitável, o código de barras ou o código Pix no evento de carrinho abandonado da Hotmart, isso ajudaria muito na conversão e nos ajudaria a manter nossa assinatura com a Manychat, pois não perderíamos vendas.
Dynamic input that identifies the type of message sent by the user (text, audio, photo and document). This way, it is possible to create a conditional and direct the user to the correct flow.
Hi Manychat Team, I’d like to suggest a useful enhancement to the flow builder: the ability to set conditions based on which team member is assigned to a conversation. At the moment, it’s not possible to trigger different actions or flows depending on the specific assigned agent. This limits the ability to personalize automations based on internal assignments. Example Use Case:If a conversation is assigned to Agent John, I could send a personalized message like:"John will get back to you shortly — he’s our specialist on this topic!"Whereas if it's Agent Lisa, the message could say:"Lisa is reviewing your message now. She’ll respond as soon as possible!" This feature would allow for more humanized and efficient communication, improving the user experience by showing that someone specific is handling the conversation — not just an anonymous team. Thanks for considering this suggestion. It would be a great addition for support teams using assignment-based workflows. Could you help me with this, @Raquel C , @Marina? Best regards,Heric Fernandes
Currently, when running WhatsApp ad campaigns, users must send a keyword or message first before a ManyChat flow can start. This extra step creates friction in the lead onboarding process and can negatively affect conversion rates — especially in paid campaigns.Proposed Solution:Introduce native WhatsApp Forms (in-app forms) that open directly inside WhatsApp when a user clicks a link or ad.These forms would allow users to fill in fields such as name, email, preferences, or other custom data without needing to send a message first.Why This Matters:I build automated WhatsApp funnels via ManyChat for coaches and consultants in the DACH region, and this feature would be a real gamechanger for WhatsApp automation and advertising.Platforms like Spoki already offer this kind of native WhatsApp form experience — enabling smoother lead capture and higher conversion rates.With native WhatsApp forms, advertisers could: Simplify the ad-to-chat flow dramatically Collect structured data directly in WhatsApp Improve the first-contact experience for new leads Optimize campaign performance and reduce drop-offs Questions: Is native in-WhatsApp form support currently on the ManyChat roadmap for 2025? If not yet, is there any workaround (e.g., via structured messages, templates, or custom API logic) to simulate this behavior? Impact:This feature would make WhatsApp ads much easier to optimize, improve lead quality, and reduce friction in funnel automation — especially for businesses running WhatsApp-based lead generation at scale.
Gostaria que vocês lançassem uma integração que permita coletar os parâmetros para rastreio e tracking de campanhas diretas para whatsapp. Esses parâmetros seriam o source_id que é a identificação do anúncio da Meta e o ctwa_clid que é a identificação do clique para WhatsApp. Hoje em dia muita gente envia conversão pelo manychat mas é apenas uma conversão “para dizer que envia”. Não enviam com esses dados que são necessários para atribuição e marcação dentro da Meta. Outra coisa também seria a identificação do clique para anúncios para instagram ig_sid que tem a mesma função que o ctwa_clid porém focado em campanhas de instagram.
I use Manychat as a mass recruiting tool, and it would be extremely helpful to be able to track which candidates read the broadcast so I can profile them and have a better kpi on our messaging system.
In the AI Step, it would be very helpful to have the ability to set dropdown options for tasks. This way, the AI could select only from predefined values when filling a variable, avoiding the risk of generating or inventing incorrect data.Additionally, the AI Step should also support boolean fields (true/false) as valid task outputs. This would make the automation more precise and reliable, especially for conditional logic.These improvements would give us more control over data consistency and reduce errors in workflows.
Manychat webhooks have a 10-second timeout limit for API responses. A lot of times people are trying to integrate manychat and n8n with webhooks and API requests to create WhatsApp AI agents, which means that a lot of times the webhook response from the n8n agent takes more that 10 seconds and so the response doesn’t make it back to manychat to be sent.I would like to propose a change in this timeout limit, which is probably making a lot of people change platform.
Hello, good morning.I’d like to share an idea that I believe could be very useful: extending the current WhatsApp audio limit in ManyChat from two minutes to five or even eight minutes. In my professional work I often need to send audio messages, and two minutes is far too short — I’m forced to use external tools, which sometimes causes complications.I would really appreciate it if you could consider increasing the audio duration to five or eight minutes directly from the ManyChat chat interface. Thank you very much.
The Idea is to be able to send a message with an image in a single message (image with caption)and to be able to use it freelywithing the 24 hour window,it would be very useful to deliver visuals with a message to convey the message even better
It would be very useful if the AI Step in ManyChat included a "No Response" fallback option.This would allow us to recover conversations when the user does not reply to the AI Step, making it easier to redirect them to another flow or trigger a human takeover.Right now, if the user stays silent, the conversation can get stuck. Having this option would give us more control and prevent lost leads.
Ever set up an awesome AI Step… only for the user to just vanish? 😅 Right now, if they don’t reply, the convo just sits there collecting dust.👉 My idea: let us add automatic follow-ups inside the AI Step itself.So if the user doesn’t answer in, say, 5 minutes, 1 hour… boom 💥 ManyChat sends a friendly nudge like: “Hey, are you still there? 👋” “Just checking in… want to keep going? 🚀” Why this would be amazing:✅ No more dead-end chats.✅ Conversions go up with those little reminders.✅ Saves us from building crazy workarounds.✅ Makes the AI feel waaay more human. 🤖❤️Imagine just clicking “If no response → send this” right inside the AI Step. Easy. Powerful. Game-changing.Who else wants this? 🙋♂️🙋♀️ Smash that like button so ManyChat knows we need it! 🔥
English:Currently, sending audio files is not supported on WhatsApp and Instagram channels when used through integration platforms such as Make.com and N8N. This limitation significantly compromises the experience, as audio is one of the most popular forms of communication among users—especially on WhatsApp here in Brazil.Therefore, we request that this feature be enabled, allowing audio messages to be sent natively. Make itself already supports this feature, but since ManyChat doesn't support the audio format, all automation is rendered impossible.Enabling this feature would make communication much more natural, practical, and aligned with the already established usage patterns on these platforms. It's worth noting that this is a basic feature, already present in competing solutions, which reinforces its importance and urgency.We thank you in advance for your attention and hope that this improvement will be prioritized. Portuguese BR: Atualmente, o envio de arquivos de áudio não é suportado nos canais do WhatsApp e Instagram quando utilizados via plataformas de integração como Make.com e N8N. Essa limitação compromete bastante a experiência, já que o áudio é uma das formas de comunicação mais utilizadas pelos usuários — especialmente no WhatsApp aqui no Brasil.Solicitamos, portanto, a habilitação dessa funcionalidade, permitindo que mensagens de áudio sejam enviadas de forma nativa. Hoje, o próprio Make já oferece suporte a esse recurso, mas como o ManyChat não libera o formato de áudio, toda a automação acaba inviabilizada.A liberação dessa função tornaria a comunicação muito mais natural, prática e alinhada ao padrão de uso já consolidado nessas plataformas. Vale destacar que trata-se de um recurso básico, já presente em soluções concorrentes, o que reforça sua importância e urgência.Desde já, agradecemos pela atenção e esperamos que essa melhoria seja priorizada. Font: https://manychat.github.io/dynamic_block_docs/channels/
We have noticed that when users react to a message we send (for example with a thumbs up), the response we receive is ‘Unsupported Message Type’This is part of Meta’s API as per the doc below:https://developers.facebook.com/docs/whatsapp/cloud-api/messages/reaction-messages/
Hello ManyChat Team,I’d like to suggest a feature that would be really useful for WhatsApp automation inside ManyChat:👉 Allow a Tag Update to send a WhatsApp Message directly to one or more specified WhatsApp numbers, from the account holder’s WhatsApp number.Why this matters:Currently, when I tag a conversation as Order Completed, I need to use Zapier to notify my delivery riders. The challenge is: Zapier’s WhatsApp integrations are limited and rely on pre-set templates. It adds extra steps and costs to the workflow. It’s not flexible enough when I want to assign orders to specific riders quickly. How it would help: I could set up an automation so that when a tag like Order Completed is applied, a WhatsApp message is automatically sent to Rider A or Rider B (or multiple numbers). This would streamline order handling and reduce dependency on third-party tools. It would also improve real-time communication for logistics, deliveries, and similar use cases. Example use case: Customer chat is tagged as Order Completed. ManyChat automatically sends: A confirmation to the customer. A delivery notification to the assigned rider’s WhatsApp number. This feature would save time, cut down on costs, and make ManyChat much more powerful for businesses managing deliveries or field operations.Thank you for considering this!
Summary:I propose that ManyChat’s integrated AI can understand audio (transcribe + extract intent) and images (OCR / recognize context). Today users prefer sending voice notes and images; allowing ManyChat to process them natively will reduce friction and enable new support and sales flows.Problem: Many users send voice messages and images because it’s more convenient; bots currently ask them to type or repeat information. This causes delays and extra work for agents. Proposal: Enable processing of voice messages to produce a transcription and the user’s main intent. Enable basic image recognition (read text in photos like tickets/receipts and detect image type: product / receipt / ID). Allow flows to combine voice + image + text to make decisions (for example: detect a complaint and automatically create a ticket). Use cases: Support: customer sends a product photo and says by voice “it arrived broken” → bot identifies order and creates a refund proposal or ticket. Commerce: user sends a photo of a product and asks the price by voice → bot replies with options and a purchase button. Pre-human assistance: automatic summary of audio + photo so the agent sees the essentials before replying. Accessibility: people who have trouble writing use voice and images to complete forms. Closing / Request:Please consider prioritizing multimodal capabilities (processing audio and images) in ManyChat’s AI. I can provide concrete flow examples if the product team wants them.
Summary:I propose that ManyChat’s integrated AI can understand audio (transcribe + extract intent) and images (OCR / recognize context). Today users prefer sending voice notes and images; allowing ManyChat to process them natively will reduce friction and enable new support and sales flows.Problem: Many users send voice messages and images because it’s more convenient; bots currently ask them to type or repeat information. This causes delays and extra work for agents. Proposal: Enable processing of voice messages to produce a transcription and the user’s main intent. Enable basic image recognition (read text in photos like tickets/receipts and detect image type: product / receipt / ID). Allow flows to combine voice + image + text to make decisions (for example: detect a complaint and automatically create a ticket). Use cases: Support: customer sends a product photo and says by voice “it arrived broken” → bot identifies order and creates a refund proposal or ticket. Commerce: user sends a photo of a product and asks the price by voice → bot replies with options and a purchase button. Pre-human assistance: automatic summary of audio + photo so the agent sees the essentials before replying. Accessibility: people who have trouble writing use voice and images to complete forms. Closing / Request:Please consider prioritizing multimodal capabilities (processing audio and images) in ManyChat’s AI. I can provide concrete flow examples if the product team wants them.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK