Why no Multilingual Support ?

  • Resolved amirhmoradi

    (@amirhmoradi)


    1 year, 1 month ago

    Hi; I really like fluentcrm’s features and philosophy, but, after checking your documentation and the support forum here, I see you said in multiple tickets that it is not possible to translate emails in multiple languages with FluentCRM.

    This is very unexpected and surprising for me, for such a feature-rich plugin, to not have the simple feature of translation ready email content or at least be compatible with translation plugins like TranslatePress, WPML, Polylang or alike…

    Each wordpress user (or woocommerce user/customer) has a locale (language) attribute, so we shall be able to send them the communication (email, newsletter…) in their own language, simple as that.

    Making translations of custom post types (the emails in the automations or campaigns) is very simple technically as far as I know.

    Would you please explain the real reason behind the lack of such translation-ability feature in FluentCRM? (go into tech details if required please).

    Shall we be looking for another solution? Any recommendations?

    Regards.

Viewing 1 replies (of 1 total)
  • Plugin Support Md. Ashikur Rahman – WPManageNinja

    (@ashiik)

    1 year, 1 month ago

    Hello @amirhmoradi!

    Thank you so much for your thoughtful message and for appreciating FluentCRM’s features and philosophy — we truly value your feedback.

    Currently, FluentCRM supports translation via Loco Translate for general plugin strings. However, full multilingual support for email content (such as campaigns and automations) is not available.

    From a technical perspective, implementing dynamic multilingual emails would require FluentCRM to detect each subscriber’s locale in real-time and fetch the corresponding translated email content. This would introduce significant complexity and potential performance overhead, particularly for large-scale campaigns or automation runs.

    Additionally, the plugins you mentioned (like WPML or TranslatePress) primarily handle page content translation. FluentCRM email content, however, is stored directly in the site’s database; it’s not part of any page-rendered content and content is pulled and sent as it is. This architectural difference is a key reason why typical translation plugins do not apply seamlessly here.

    With FluentCRM, many users create separate email sequences and automation funnels for each language, and then segment contacts manually based on their language preference (e.g., using custom fields, lists, or tags). While this is not automatic translation, it’s currently the most effective approach within FluentCRM.

    Still, I’ll be forwarding your request to our R&D team as a feature request. While I can’t promise an ETA for this implementation.

    Thanks again for your understanding and for being a valued member of the FluentCRM community!

    Best regards,
    Ashik

Viewing 1 replies (of 1 total)

The topic ‘Why no Multilingual Support ?’ is closed to new replies.