Launch: Automatic Translations for Cancel Flows and support for 45 new languages

With one toggle, Churnkey will translate your Cancel Flow into multiple languages—no more duplicating flows, no more managing multiple segments. Translated Cancel Flows perform 46% better than non-translated flows.

Launch: Automatic Translations for Cancel Flows and support for 45 new languages

The world speaks more than one language. Now, your Cancel Flow does, too. Up to 50, to be precise.

Today, we’re launching Automatic Translations: a powerful new way to support customers who speak different languages than your core team. With one toggle, Churnkey will translate your Cancel Flows into one of 50 supported languages using guided AI translations.

That means no more duplicating Cancel Flows and managing multiple segments. No more juggling i18n codes and manual translations. Just a seamless, multilingual experience that meets your customers where they are.

Multilingual support brings better outcomes

Until now, deploying translated Cancel Flows required too much extra work:

  • Manually duplicating flows for each language
  • Meticulously translating copy across each Cancel Flow step
  • Mapping complex segmentation rules
  • Testing and QA’ing each version in isolation

Most teams didn’t bother. Those who did saw better results, but struggled with increased operational complexity.

With Automatic Translations, you get the upside without the overhead. From our data, companies that translate their Cancel Flows into the language of their customers end up seeing save rates increase by 46%, while enjoying higher customer satisfaction scores and higher LTV.

Translated Cancel Flows perform 46% better

In summary, Automatic Translations get you:

  • One-click multilingual support: Flip a toggle in settings. Define up to five languages to which you want to translate your Cancel Flows. We’ll handle the rest.
  • Clean segmentation: No duplicative flows or confusing segments.
  • Simple auditing: See exactly what your customers will see in their native language.
  • Consistent analytics: All versions of your Cancel Flow are tracked in one place, with per-language data coming soon.
  • Great performance: Every translation is cached ahead of a customer session, so loading remains snappy as ever.

And like most Churnkey features, it works right out of the box—no engineers required.

Bonus: 45 new manual translation options for Cancel Flows, Failed Payment Wall, and Pause Wall

We've also expanded multilingual options for the Failed Payment Wall and Pause Wall, supporting 45 new pre-built translations for commands and interface text. So if you're using these products and a customer shows up with their browser set to any of these languages, Churnkey will display the correct language to them.

These pre-built translations are also available for Cancel Flows if you decide you want to circumvent Automatic Translations and do everything manually instead.

Automatic Translations: now available

Automatic Translations are available today on all Churnkey plans. Simply head to Cancel Flows → Settings and scroll to the Language section. Or, browse the Docs to learn more.

Whether you’re already operating globally or just starting to expand, your Cancel Flows should reflect the language of your customers. Now they can with near-zero effort from your team.