Feature Requests

Please add first-class Apple Pay support to the ClickFunnels Checkout SDK, including custom-coded and externally hosted checkout pages using Payments AI. We want to keep ClickFunnels products, orders and funnel integrations while building our own compact checkout UI. Apple Pay should be available through a documented SDK API, rather than requiring us to rebuild the checkout with native editor elements. Please provide merchant/domain verification instructions, eligibility checks, wallet-button rendering, payment authorization, clear errors, and examples for one-time payments and subscriptions. Please route this request to the API/SDK team and share whether it is planned and an estimated delivery timeframe. Blunt feedback from a paying customer: it is no wonder people consider moving away from ClickFunnels when they pay for a platform that feels behind the market on core checkout features. From my perspective, Whop feels like it is moving 10x faster. ClickFunnels has some cool features I like, but too much of the experience feels like a thing of the past. You need to accelerate feature development and catch up with modern checkout expectations if you want to stay competitive and survive. Apple Pay in the SDK is exactly the kind of practical improvement that would help keep us here.

It would be great to have a signed identity token or secure verification endpoint for the currently logged-in Customer Center contact. This would let an external backend verify the member’s identity and securely authenticate them with services such as Intercom, without requiring another login. Exactly how ClickFunnels does with their Intercom Messenger Live Chat. Currently, inbound SSO lets us log customers into ClickFunnels, but there’s no supported way to verify an existing ClickFunnels session externally. Displaying an email in HTML or JavaScript isn’t sufficient proof of identity. This would make support widgets and other member integrations more seamless and secure.

Is there a way to collapse the descriptions for products? They seem too long which can deter a potential customer from looking through a drawn-out page of products. Thank you!

I'm loving all the new API enhancements. One thing I've noticed, though, is that when I create a workflow or email broadcast through the API, I can't go back in and make small final edits myself. Ideally, anything created through the API would still be editable inside the platform. That would allow me to use the API to build the workflow or broadcast, then go in and make any final tweaks before it goes live. Right now, the system doesn't allow that, and it's a feature I would absolutely love to see added.

Contractors build funnels, but their local pages need service-area schema, city pages and review blocks — today that is all manual. A funnel template with built-in local fields would change that. For a roofers waukegan business, a page carrying the city, the services and the reviews in one place converts far better than a generic lead form. Fields for service area, services offered and testimonials, plus automatic local schema, would cover most of what a contractor's page needs.

Coaches and agencies selling in the Gulf often show running costs next to their offers - rent, workspace, utilities - to make pricing feel concrete. A small calculator block where a visitor can estimate a monthly utility bill would be a genuinely useful addition to the page builder. For the numbers, sellers here sanity-check against https://dewabillcheck.com/ before publishing a page. A native block would keep that estimate inside the funnel instead of sending visitors away to check.

I suggest a feature enhancement to support right-to-left (RTL) languages, such as Hebrew, which are written from right to left. There is a workaround where I add custom CSS to the pages for RTL alignment, but the form fields remain unaffected and do not adjust to the RTL format. It would be incredibly helpful if a built-in option could easily enable RTL for both the form fields and the entire website. This would greatly improve the user experience for those working with RTL languages.

It would be incredibly helpful to have the ability to set a custom 404 redirect at the funnel level - not just site-wide. This is especially useful for users managing multiple funnels with separate domains, audiences, or offers. For example, I want all invalid or broken URLs within a specific funnel to redirect to that funnel’s main opt-in page (or any page I want), rather than the default site-wide 404. Exactly how ClickFunnels Classic does this.

Having the option to manually adjust or fix without having to run a full prompt costing additional tokens would be nice...

The course sidebar on ClickFunnels 2.0 always shows all the modules, even if the user has not purchased access to them.