Share your ideas to make Manychat better.
Hello Manychat Support,I’m unable to connect my Instagram Business account @donyaye.sakhteman to Manychat. I have tried several times, but the connection/Meta authorization does not complete.I also receive a “Your account is restricted” error when trying to connect Instagram to Facebook.My goal is to use Manychat to automatically reply to Instagram comments and send DMs with requested product information, while encouraging users to follow my page first.Could you please check the issue and help me connect my Instagram account to Manychat?Thank you.
Since 2026, Meta creates new WhatsApp Business Accounts (WABAs) in Chile and other Latin American countries in local currency (CLP, ARS, COP) by default. Meta does not allow changing a WABA's currency after it is created.Manychat can only share its USD credit line with USD WABAs. As a result, businesses like mine with a WABA in CLP get "Credit line is not set up" and cannot:- Reply to customers from the Manychat inbox- Send message templates or broadcasts- Reply to contacts who did not come from a Click-to-WhatsApp adSince October 1, 2026, Meta charges per service message, so this blocks a core part of our daily operations. I already added my own card as payment method in Meta Business for the WABA, but Manychat still requires its own credit line.The only solution offered by support is to delete the number from the WABA and create a new one in USD. This is very risky for us: we would lose our approved templates, our messaging limit (10,000/day), our high quality rating, and we could affect our Click-to-WhatsApp campaigns, which have strong performance.Requests (any of these would solve it):1. Support WABAs in local currencies (CLP, ARS, COP, etc.)2. Allow clients to use their own payment method in Meta instead of the Manychat credit line3. Offer an official currency migration that keeps the same WABA, templates and quality ratingThis affects more and more Latin American businesses as Meta rolls out local-currency billing. Other platforms already allow paying Meta directly with the client's card.Thank you!
Description: When a WhatsApp contact sends a photo or a document with a caption, Manychat only stores the file link in "Last Text Input". The caption text is not available in any field or variable, so automations and external integrations (Make, webhooks, AI assistants) never receive it. For documents, the caption is not even visible in the Inbox.Why it matters: Customers very often write the key part of their request in the caption ("I need 50 of these in red"). Today that information is silently lost, and the business has to ask again or answer without context.Request: Expose the caption as a system field or variable (for example "Last Media Caption"), include it in the External Request / webhook payload, and show it in the Inbox for documents as well as photos.Reference: Support ticket #579833.
Please include an option to use regular expressions for keyowrds matching. This is especially useful in languages with diacritical marks, where people can combine any form of a word with diacritical marks - with all of them, with some of them, with none of them, also tend to swap letters z/y etc. Since the limit to match keywords is 10, many times it is not sufficient.Another option is to raise the keyword limit from 10 to at least 30, however, regular expressions would have been more elegant.
Hello. We need ManyChat to fully embrace the era of artificial intelligence and at least allow us to build flows more quickly using AI.It would be excellent if they integrate or enable an MCP for the platform. This would, of course, require adding more endpoints to the API and, additionally, building a web MCP.If the MCP becomes too complicated for you, a web MCP would at least enable the AI to navigate the digital portal more intuitively.
The Problem ManyChat has one of the best visual automation builders on the market. But its API tells a different story. In 2026, where AI agents are becoming the primary interface between developers and SaaS platforms, ManyChat's API coverage leaves critical operations locked behind the UI — making it nearly impossible for AI-powered workflows to fully automate marketing campaigns. We manage 1,275 WhatsApp contacts through ManyChat for marketing campaigns in Brazil. Through the API, we can tag subscribers, create contacts, set custom fields, and reactivate subscribers. That part works great. But the moment we need to do the things that actually drive revenue — create a broadcast, list our approved WhatsApp templates, schedule a campaign, or pull performance metrics — the API has nothing. We are forced back into the UI for every critical operation. This is not a niche complaint. This is a structural gap that will determine whether ManyChat thrives in the AI agent era or gets replaced by API-first alternatives. The AI Agent Revolution Is Here — And ManyChat Is Missing It The numbers are not hypothetical. They are happening right now: - Claude Code (Anthropic's AI coding agent) has reached a $2.5B annualized revenue run-rate, with 58% of professional developers using AI agents in their daily workflow. - Gemini CLI (Google's agent) hit 98K GitHub stars within weeks of release. - MCP (Model Context Protocol) — the open standard for connecting AI agents to external tools — now has 17,000+ community servers and 97 million monthly SDK downloads. - Every major platform has already shipped MCP integrations: Stripe, Shopify, GitHub, Slack, HubSpot, Linear, Notion, Sentry, Cloudflare, Supabase — the list grows daily. What does this mean in practice? Developers and agencies no longer interact with SaaS tools through UIs. They say to an AI agent: "Send last month's broadcast performance report" or "Create a campaign targeting all subscribers tagged 'hot-lead' using the approved Black Friday template, scheduled for Friday at 9am." The agent calls the API. The work gets done. ManyChat's API cannot support any of these workflows today. Not because the product lacks the features — but because the API simply does not expose them. The Community Is Already Building Around the Gap The developer community is not waiting. They are building what they can with what exists: - Biznomad/manychat-mcp — a community-built MCP server that wraps ManyChat's API so AI agents can interact with it. But it can only do what the API allows: subscriber CRUD and tagging. No broadcasts. No templates. No metrics. - Multiple Zapier and Pipedream MCP bridges exist, all hitting the same wall. - Existing feature requests on this very portal tell the story: broadcast API management (1 vote), template API access (2 votes), flow control via API (4 votes). The low vote counts do not reflect low demand — they reflect the fact that most ManyChat users are marketers, not developers. The developers who need this are building workarounds or leaving the platform entirely. What We Are Asking For P0 — Critical (Unlocks AI agent integration) ┌───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────┐ │ Endpoint │ Why │ ├───────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────┤ │ List WhatsApp templates │ AI agents need to know which templates are approved before sending. Without │ │ │ this, any automation is blind. │ ├───────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────┤ │ Send WhatsApp template to subscriber │ The single most requested programmatic action. Templates are the only way to │ │ (with variable substitution) │ initiate WhatsApp conversations outside the 24h window. │ └───────────────────────────────────────────┴───────────────────────────────────────────────────────────────────────────────┘ P1 — High Priority (Unlocks campaign automation) ┌─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────┐ │ Endpoint │ Why │ ├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤ │ Create broadcast via API │ Allows AI agents and external systems to trigger campaigns without UI │ │ │ interaction. │ ├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤ │ Schedule broadcast │ Time-zone-aware scheduling is table stakes for any marketing API. │ ├─────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────┤ │ Get broadcast metrics (sent, delivered, │ Without metrics, there is no feedback loop. AI agents cannot optimize what │ │ read, clicked) │ they cannot measure. │ └─────────────────────────────────────────────┴─────────────────────────────────────────────────────────────────────────────┘ P2 — Important (Unlocks full platform programmability) ┌─────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────┐ │ Endpoint │ Why │ ├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤ │ Get flow content/structure │ Currently only sendFlow exists (fire-and-forget). No visibility into what a flow │ │ │ contains. │ ├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤ │ Create/update flows │ Enables version control, CI/CD pipelines, and AI-generated flow creation. │ │ programmatically │ │ ├─────────────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────┤ │ List subscribers by tag │ No way to say "give me all subscribers tagged X." Bulk operations on filtered segments │ │ │ are impossible via API. │ └─────────────────────────────────┴─────────────────────────────────────────────────────────────────────────────────────────┘ The Competitive Reality - Listmonk (open-source, 19K GitHub stars) offers a complete REST API for every operation: campaigns, templates, subscribers, metrics — all fully programmable. - WhatsApp Business API (direct) gives full programmatic control over templates, messages, and analytics. - Brevo, Mailchimp, SendGrid — all have comprehensive APIs that AI agents can fully orchestrate. The pattern is clear: platforms that expose full APIs get integrated into AI agent workflows. Platforms that don't get bypassed. A Real Workflow We Cannot Automate Today 1. AI agent queries CRM → identifies 340 subscribers who attended a webinar but did not purchase 2. AI agent calls ManyChat API → lists approved WhatsApp templates → selects the "post-webinar-offer" template 3. AI agent calls ManyChat API → creates a broadcast targeting those 340 subscribers, scheduled for Tuesday at 10am 4. AI agent polls ManyChat API 48 hours later → pulls delivery and read metrics 5. AI agent generates a performance report and suggests optimizations Step 1 is possible today. Steps 2 through 5 are completely impossible via the API. Closing ManyChat has built an incredible product. The visual flow builder, the multi-channel support, the WhatsApp integration — all best-in-class. The API is the missing piece that would unlock an entire ecosystem of AI-powered automation tools. The community is ready — we just need the endpoints. The platforms that win the next five years will be the ones that AI agents can fully orchestrate. ManyChat has every advantage to be one of them. It just needs to open the door.
In the EU, all invoices must include the legal identification of both the client and the provider, such as tax ID, business name, and address.
Hi — I’m really frustrated with how the Free plan’s “25 active contacts” limit is being calculated. I haven’t actually used ManyChat automations this month, but my allowance is already exhausted because people who simply messaged me on Instagram were automatically added as active contacts.I don’t use or want ManyChat as a general CRM for every person who sends me a normal Instagram DM. I only want contacts created when someone actually interacts with a ManyChat automation.It feels misleading to have a free usage limit consumed by interactions that did not use the feature I’m trying to evaluate. At minimum, there should be an option to disable automatic contact creation from ordinary Instagram DMs.I was considering resubscribing, but this setup makes the Free plan effectively unusable for testing the product in any meaningful way. I’d really encourage your team to reconsider how these contacts are counted.
Currently, all debug information (such as triggered automations and filled custom fields) is visible to agents in Live Chat. While this can be useful for technical analysis, in many cases it clutters the chat interface and makes it harder for support or customer service agents to focus on the conversation.The suggestion is to add a toggle option in Live Chat settings to enable or disable the display of debug information, depending on the user’s profile or role.This would make the interface much cleaner for customer-facing agents, while still allowing administrators or developers to view detailed debug data when needed.Additionally, a quick toggle button (“Show Debug” / “Hide Debug”) would make this even more practical during live interactions.
Seria ótimo um plano mais acessível do que os demais, de entrada, só com a função de boas vindas, por exemplo de $10 a $15 dolares, com grande limitação apenas de comentário!
Hi ManyChat Team!I wanted to reach out with a feature suggestion that would be incredibly valuable for creators who use ManyChat for brand partnerships!Brands frequently ask me to provide my total Story link clicks over the last 30 days as part of their evaluation process for potential collaborations.Because I use ManyChat for nearly all of my Instagram Story links, Instagram's native link-click analytics don't accurately reflect the traffic I'm driving. While ManyChat allows me to view link clicks for individual automations, there doesn't seem to be a way to see my total link clicks across ALL automations within a specific date range.I'd love to see ManyChat introduce an analytics feature that allows creators to:View total link clicks across all automations over the last 30 days (or a custom date range). See an aggregate overview of link-click performance rather than having to calculate each automation individually. Generate a clean, shareable screenshot or downloadable report that can be sent directly to brands and talent managers.Having a report similar to Instagram Insights, but reflecting our actual ManyChat link clicks, would be a GAME CHANGER for creators!You are an such an important tool for driving traffic and conversions, and I would love to have a way to accurately showcase that value when negotiating brand partnerships.Is this something your team has considered implementing, or is there currently a way to access this information that I may be overlooking?Thank you so much for your time and consideration!AlexThe Natural Minded Mama@thenaturalmindedmama
To have a grace period when billing fails.All business software have a grace period for billing, to allow the admins to add alternative payment methods if the billing fails for whatever reason.This is necessary to avoid service interruptions.Ideally we’d have:Failed billing - notification email (PRO service continues to work) More billing attempts over at least a 3-4 day period - send an email on each failed attempt (PRO continues to work) After several billing attempts, service is downgraded to FREE service (with notification email)If not possible, an alternative would be to allow us to add alternative payment methods (a 2nd or 3rd card) so if the first method fails Manychat can try the other cards.
Prezados, bom dia!Gostaria de deixar uma sugestão que facilitaria MUITO a vida dos seus usuários:Aumentar o tamanho da imagem de capa do post nas automações, pois dessa forma seria mais rápido para identificar o post que precisamos editar a automação. Solicitei ajuda através do ticket, mas me informaram que a única solução do momento era renomear cada automação, mas isso seria extremamente trabalhoso e nada prático.
I would like to request a native feature that allows us to dynamically control user access to specific automation steps or AI workflows based on an external whitelist (like Google Sheets or Airtable). The Use Case:Agencies build workflows for clients but want to give those clients the ability to add, remove, or manage user access permissions themselves. Currently, to block or allow specific users, clients need backend access to ManyChat's Condition nodes or user tags, which risks exposing the entire backend build. Proposed Solution:A native "Lookup & Conditions" feature that checks a specific column in a live external spreadsheet (e.g., phone number or user ID) before allowing a contact to proceed down a specific path or trigger an AI block. This would let builders lock down the backend while empowering clients to manage their own user rosters safely.
It would be extremely helpful to have the option to export individual or multiple conversations as PDF files, with customer names and contact information automatically redacted for privacy.This would allow businesses to use AI tools to analyze conversations, compare the performance of different sales agents, identify where customers are progressing or dropping off, and improve both sales processes and automation flows.An integrated AI conversation-analysis feature would be even more valuable in the future. However, simply enabling privacy-safe conversation exports would already make funnel analysis significantly easier and more actionable.
The idea is that when the personal its off, the automatizations still working. So when the personal starts working again, it will apear a summary about all the things that Manychat did when we were off.
I have having to move every little card on my webflow everytime I need to edit the layout.Also being able to change multiple things at the same time (all the copy´s and everything) because you can miss a lot of things if you have a big workflow with multiple equal things
Pleaes add a Phone call button in Features list, this will help customer to make a direct call to our representative
Please add the ability to export automations/flows as JSON files. This would make it much easier to share, back up, duplicate, and migrate complex automations. Thank you in advance.
He notado que todos los agentes de chat reciben notificaciones en el celular de todas las conversaciones, sería bueno que los supervisores pudieron controlar los permisos de notificaciones de los agentes.
Actualmente existe un bloque que permite recopilar ubicaciones de WhatsApp. Sin embargo, aunque ofrece al usuario la opción de compartir su ubicación actual, no existe una configuración que restrinja el envío únicamente a dicha ubicación, por lo que el usuario también puede seleccionar y enviar cualquier otra ubicación.
I would really suggest that Manychat make their VAT number official for accounting purposes.Maybe include it automatically in the invoices (not the individual companies’ VAT’s, but Manychat’s own VAT). In some countries when you make a purchase you have to register the information on the company you buy from and often it’s required that both VAT and address is applied for correct accounting.
Can we please get an integration for all of our contact to automatically connect with the platform captivation hub?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.