Skip to main content

Feature Request: Present Customer Center Contact Support as a standalone flow

  • September 28, 2026
  • 2 replies
  • 21 views
Forum|alt.badge.img

It would be useful to expose the existing Customer Center Contact Support UI as a standalone flow, for example:

RevenueCatUI.presentContactSupport()

We already use the Contact Support functionality configured through Customer Center, including RevenueCat's support form and embedded metadata.

However, our app has its own Support entry point, and we would like to open the RevenueCat Contact Support form directly without first presenting the entire Customer Center.

Ideally, this would use the same Contact Support configuration, metadata, and ticket flow as the existing Customer Center implementation, just exposed as a standalone UI flow.

Since RevenueCatUI already uses an internal support ticket flow, it seems that most of the underlying functionality is already in place. Because of that, exposing the existing Contact Support UI as a standalone entry point may be relatively small in scope, while making it much easier to integrate into custom app settings and support screens.

2 replies

RevenueCat Staff
Forum|alt.badge.img+8
  • Haley Pace
  • RevenueCat Staff
  • September 29, 2026

Hi ​@alnaum, thank you for the feedback! I’ve logged the request for a standalone presenter that uses that same configuration and ticket flow.

Contact Support is only available inside Customer Center today. On Flutter, that is RevenueCatUI.presentCustomerCenter() from purchases_ui_flutter. There is no presentContactSupport() method.

The form, support email, who sees the button, and embedded metadata all come from the Customer Center support settings, and the form is shown only after someone opens Customer Center and taps Contact Support. If the button is missing, check that a support email is set and that Contact support visibility matches the customer you are testing with. It defaults to customers without an active subscription. The in-app form, instead of opening the mail app, is the “Contact support metadata” setting.

Forum|alt.badge.img
  • alnaum
  • Author
  • New Member
  • September 29, 2026

Hi ​@Haley Pace

Thanks, that’s exactly what I meant.

Just to clarify, I’m not looking for a workaround with the current presentCustomerCenter() flow. The feature request is specifically for a standalone public presenter, such as RevenueCatUI.presentContactSupport(), that would open the existing RevenueCat Contact Support form directly while reusing the same Customer Center configuration, metadata, and ticket flow.

I think this could be especially useful because the Contact Support flow already solves several things that developers would otherwise have to build themselves: there’s no need to maintain a separate backend or email-delivery infrastructure for support requests, and the relevant RevenueCat customer metadata is attached automatically.

Customer Center is great when the user wants to manage their subscription, but it also contains several other actions and pieces of information. For a simple “Contact Support” action in an app’s Settings or Help screen, opening the entire Customer Center can add unnecessary steps and may be confusing, since the user is presented with options unrelated to what they were trying to do.

That makes the existing support form a very useful developer-facing feature on its own. Being able to launch it directly would make it much easier to integrate into an app’s own support UI while keeping all the benefits of RevenueCat’s ticket flow.

    Terms & ConditionsAccessibility statement