Skip to main content

    Filter by status

    Filter by product area

    785 Ideas

    Let an external AI agent take over a live conversation via External Request (AI handoff, not human handoff)New

    **The gap:** every "takeover" feature in Manychat today assumes a *human* opens the Inbox and types. For a solo operator that assumption breaks exactly when it matters. I run a one-person business. When a conversation goes sideways, I am often driving or away from a screen. There is no support team to tag in.What I have instead is an AI operator (Claude) running on my own backend. It can read the conversation, look up the customer's live order state in my system, and answer properly. It is far more capable than a flow or a template. I want *it* to take the wheel, not a human.**What already works:** the External Request path. Inbound message → External Request → my server → I return the reply text → Manychat delivers it. Reliable, and it never runs into message-tag restrictions, because we are responding rather than pushing. That is the right rail. The takeover I want is simply: while a conversation is flagged, my server returns the AI operator's answer instead of the normal automated one.**What blocks it today:**1. **External Request timeout is too tight for a thinking agent.** A template answers instantly; a real AI needs a few seconds to read context and compose something genuinely useful. With a short ceiling, I am forced to return filler — which is the exact "bot acting dumb" experience I am trying to eliminate.2. **No supported deferred reply.** If I can't answer within the timeout, there is no way to acknowledge now and deliver the real answer moments later into the same conversation. My only reliable workaround is to hold the answer and attach it to the customer's *next* inbound — so the customer has to message twice to get one reply.3. **No per-subscriber automation pause/resume via API.** There is no clean primitive for "automation off, my external agent is handling this one, hand back when done." Without it, my agent and Manychat automation can talk over each other.**The ask (any one of these helps, all three would be excellent):**- A configurable / longer **External Request timeout**, or an official async pattern: ACK immediately, deliver the composed reply seconds later into the same conversation.- An **API to pause and resume automation for a single subscriber** — an explicit "external agent has this one" state.- Treat **AI agent** as a first-class takeover actor alongside a human agent, in the API and in how the conversation is labelled in the Inbox, so it is obvious who is speaking.**Why this matters beyond me:** AI agents behind Manychat are becoming the norm rather than the exception, and a lot of us are solo or tiny teams. The current model quietly assumes a staffed inbox. Making the External Request path a first-class AI-handoff rail costs nothing in Meta permissions — it is already request/response — and it turns "the bot said something dumb and nobody was around" into "the smart agent stepped in within seconds."**Real example:** a customer was mid-order in an Instagram DM. Our automation was not handling it well. I could not get my AI operator into that conversation at all — API sends returned HTTP 400, the Live Chat composer threw a server error, and I was not in a position to sit and type. It took over 30 minutes and we ultimately abandoned the channel and reached her by email. The whole time, the AI that could have solved it in one message was sitting there with no supported way in.

    katharinadeze
    katharinadezeUp-and-comer

    Remove the mandatory first message from Click-to-WhatsApp AdsNew

    Please add native WhatsApp Forms so users coming from Click-to-WhatsApp Ads can submit their data and enter the funnel without having to manually send a message first.This extra “send message” step creates unnecessary friction at the most important point of the funnel: the entry.For lead generation, the ideal journey would be:Ad click → WhatsApp Form → lead data captured → automation startsinstead of:Ad click → WhatsApp opens → user has to send a message → automation starts → lead data has to be collected afterwardsFor businesses spending money on Click-to-WhatsApp Ads, every additional step can cost conversions. The current setup makes the entry into a WhatsApp funnel less seamless than it could be.Native WhatsApp Forms could be used to collect data such as:name email address phone number other lead informationdirectly at the beginning of the funnel.This would also solve another major problem: right now, many professional setups require additional workarounds with tools like Make or Zapier to transfer lead data between WhatsApp, ManyChat, email marketing tools and CRMs.That means more setup, more maintenance, additional costs and more potential points of failure.For such a basic part of a lead generation funnel, having to rely on external middleware feels unnecessarily complicated and makes the whole setup more error-prone.Other WhatsApp-focused platforms already offer form-based lead capture, while ManyChat is stronger in many other areas of automation. That makes this missing feature especially frustrating.For marketers and agencies building WhatsApp funnels professionally, this is not just a convenience feature. It can genuinely become a reason to recommend another platform, even if ManyChat would otherwise be the preferred choice.I would really love to see this prioritized.Is native WhatsApp lead capture without a mandatory first message currently being considered for the roadmap?

    katharinadeze
    katharinadezeUp-and-comer

    Native WhatsApp Forms (In-App Forms)New

    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.