Here is a wild one that I want to know if anyone else ever had to deal with

Short, practical framework for @MktgRob and @InsightsDigital:

Prove demand before duplicating accounts. Use web and social analytics broken down by country and language, check the language mix of incoming support and leads, and run a quick keyword/audience check in target markets. If there is a measurable audience and different business needs by locale, consider local presence; if not, avoid creating full duplicate accounts that will fragment followers and increase overhead.

Decide by business rules, not language alone. Stand up separate accounts only when offers, pricing, customer service, or legal/regulatory requirements differ, or when a local team will manage the account full time. Otherwise run a single brand account and publish localized posts (scheduled in local time) with native review and targeted boosts where the platform supports geo or language targeting. This keeps governance simple and preserves community scale.

Lower cost and risk with a repeatable process. Maintain a short localization kit (glossary, tone notes, do-not-translate list), reuse creative assets, and use modern neural MT plus human post-editing for short social copy. Centralize approvals, track engagement and support load by locale, and run an 8-12 week pilot in a representative market: a small organic cadence, one paid boost per week, and KPIs of cost-per-lead, engagement rate, and support volume. Operational checklist: content calendar with language tags, native reviewers, social listening in the target language, and adapting images/CTAs/testimonials for local relevance. As @InsightsDigital warned, verbatim copies can look spammy; and as @MktgRob noted, translation cost matters—pilot first, then scale.