Skip to main content
New

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

Related product area:WhatsApp
  • August 23, 2026
  • 5 comments
  • 52 views
katharinadeze

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 starts

instead of:

Ad click → WhatsApp opens → user has to send a message → automation starts → lead data has to be collected afterwards

For 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 information

directly 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?

    5 replies

    cata_rendon
    Forum|alt.badge.img+5
    • cata_rendon
    • Community Moderator
    • August 24, 2026

    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 starts

    instead of:

    Ad click → WhatsApp opens → user has to send a message → automation starts → lead data has to be collected afterwards

    For 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 information

    directly 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?

    Very good proposal

    https://www.dominariai.com | https://www.linkedin.com/company/dominariai
      SumGenius
      Forum|alt.badge.img
      • SumGenius
      • Smooth talker
      • August 27, 2026

       Worth separating two things here, because one of them isn't ManyChat's to fix.

      The ad click itself delivers nothing. No webhook fires, no data reaches any platform, until the person actually sends that first message. The ad attribution, ctwa_clid and all, arrives attached to that message. So the flow you drew, ad click into form into captured data with no message sent, can't be built on click-to-WhatsApp by ManyChat or anyone else. There's nothing to receive.

      On other platforms offering form-based capture, I'd check what they're actually doing. WhatsApp Flows are real, and they're a genuine in-chat form, but they're sent as a message into an open conversation. That's after the first message, not instead of it. Same constraint, better looking.

      If your requirement is lead data before any message, that's an ad format change rather than a platform change. Meta's lead ads with an instant form capture name, email and phone in the ad unit itself, then you follow up on WhatsApp. That is your first diagram exactly, and it works today. The tradeoff is you give up the CTWA attribution that rides the first message, so pick based on which you need more, the clean capture or the ad-level tracking.

      Still worth asking about Flows on the roadmap, that's a fair request. Just probably not as a way to skip the first message.

        katharinadeze
        • katharinadeze
        • Author
        • Up-and-comer
        • August 27, 2026

         Worth separating two things here, because one of them isn't ManyChat's to fix.

        The ad click itself delivers nothing. No webhook fires, no data reaches any platform, until the person actually sends that first message. The ad attribution, ctwa_clid and all, arrives attached to that message. So the flow you drew, ad click into form into captured data with no message sent, can't be built on click-to-WhatsApp by ManyChat or anyone else. There's nothing to receive.

        On other platforms offering form-based capture, I'd check what they're actually doing. WhatsApp Flows are real, and they're a genuine in-chat form, but they're sent as a message into an open conversation. That's after the first message, not instead of it. Same constraint, better looking.

        If your requirement is lead data before any message, that's an ad format change rather than a platform change. Meta's lead ads with an instant form capture name, email and phone in the ad unit itself, then you follow up on WhatsApp. That is your first diagram exactly, and it works today. The tradeoff is you give up the CTWA attribution that rides the first message, so pick based on which you need more, the clean capture or the ad-level tracking.

        Still worth asking about Flows on the roadmap, that's a fair request. Just probably not as a way to skip the first message.

        Thanks, that makes sense — and I agree that the mandatory first message itself is a Meta/WhatsApp limitation, not something ManyChat can simply remove.

        But that actually points to a different feature request that would solve the underlying problem much better:

        A direct Meta Lead Ads → ManyChat integration without requiring Zapier or Make.

        If the goal is to capture lead data before any WhatsApp message is sent, the ideal flow would be:

        Meta Lead Ad → Instant Form submitted → lead is created or updated in ManyChat → WhatsApp automation starts

        ManyChat already has its own app/developer ecosystem, so this would not necessarily even have to become a core feature. It could also be offered as a dedicated Meta Lead Ads app or integration inside ManyChat.

        From the user’s perspective, the important part is that there is no need to build, pay for and maintain a separate Zapier or Make scenario.

        Ideally, you would simply connect your Meta account, select the Instant Form, map the form fields to ManyChat custom fields and use the form submission as the trigger for a WhatsApp automation.

        Whether this is built directly by ManyChat or provided through a dedicated ManyChat app is secondary.

        The important thing is having a reliable:

        Meta Lead Ads → ManyChat → WhatsApp

        workflow without external middleware.

        That would solve most of the problem I was originally trying to address, without trying to bypass the CTWA first-message requirement.

        So maybe the better roadmap question is:

        Is a native or app-based Meta Lead Ads / Instant Forms integration for ManyChat currently being considered?

        SumGenius
        Forum|alt.badge.img
        • SumGenius
        • Smooth talker
        • August 27, 2026

        Your reframe is the right one, and it's a much smaller ask than the first one. Meta already publishes leads over the leadgen webhook. An app subscribed to the Page gets a lead id the second the form is submitted and pulls the fields from the Graph API. Nothing to invent, it's a subscription and a field mapping. And ManyChat's existing Facebook Ads trigger only covers Traffic, Engagement and Sales objectives, so Lead Generation campaigns sit outside it today. Your request is a real gap, not a duplicate of something already there.

        One thing to plan for, because it's the part that costs money. A lead ad lead has never messaged you. So the WhatsApp follow-up is business initiated, which means an approved template rather than a free-form message, and it's billed per send. It also needs opt-in, so the consent line has to be in the Instant Form itself. Once they reply to that template the 24 hour window opens and your normal automation runs like any other conversation.

        Second thing: the phone field in an Instant Form is prefilled from the person's Facebook profile, and that is not always their WhatsApp number. Expect a share of templates going to numbers that aren't on WhatsApp at all.

        None of that argues against what you're asking for. It just means the integration is step one and the template plus opt-in setup is step two, and the second one is the easier one to miss when you're costing out the funnel.

        katharinadeze
        • katharinadeze
        • Author
        • Up-and-comer
        • August 27, 2026

        Your reframe is the right one, and it's a much smaller ask than the first one. Meta already publishes leads over the leadgen webhook. An app subscribed to the Page gets a lead id the second the form is submitted and pulls the fields from the Graph API. Nothing to invent, it's a subscription and a field mapping. And ManyChat's existing Facebook Ads trigger only covers Traffic, Engagement and Sales objectives, so Lead Generation campaigns sit outside it today. Your request is a real gap, not a duplicate of something already there.

        One thing to plan for, because it's the part that costs money. A lead ad lead has never messaged you. So the WhatsApp follow-up is business initiated, which means an approved template rather than a free-form message, and it's billed per send. It also needs opt-in, so the consent line has to be in the Instant Form itself. Once they reply to that template the 24 hour window opens and your normal automation runs like any other conversation.

        Second thing: the phone field in an Instant Form is prefilled from the person's Facebook profile, and that is not always their WhatsApp number. Expect a share of templates going to numbers that aren't on WhatsApp at all.

        None of that argues against what you're asking for. It just means the integration is step one and the template plus opt-in setup is step two, and the second one is the easier one to miss when you're costing out the funnel.

        Yes, absolutely. But as far as I understand, these are the same things you already have to consider with the current workaround using Zapier or Make. You still need the WhatsApp opt-in in the Instant Form, an approved template for the first message, and you have the same issue with the prefilled phone number potentially not being the person’s WhatsApp number.

        So these wouldn’t really be additional limitations of a native ManyChat integration – they’re already part of the current setup. The main difference would simply be that you could handle the whole process directly inside ManyChat instead of relying on an external tool like Zapier or Make.

        Community Terms & ConditionsAccessibility statement