# Multi-branch Splits in automations. How to activate?

**URL:** https://community.brevo.com/t/multi-branch-splits-in-automations-how-to-activate/7019
**Category:** Automations
**Created:** [Mars 24, 2026, 6:45 UTC](https://community.brevo.com/t/multi-branch-splits-in-automations-how-to-activate/7019 "2026-03-24T06:45:58Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![janpeini](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@janpeini](https://community.brevo.com/u/janpeini)
#### Post date: [Mars 24, 2026, 6:45 UTC](https://community.brevo.com/t/multi-branch-splits-in-automations-how-to-activate/7019/1 "2026-03-24T06:45:58Z")

</div>

We would like to use the multi-branch splits, but we already are on a business plan.  
Do we really have to upgrade to a custom enterprise plan to get multi branch splits in automations?

We are currently expanding into 12+ languages and currently the localization of automations is real pain in the ass, the multi-branch splits would at least allow us, to create one split for all languages and not having to set up cascades from hell.

 ![Bildschirmfoto 2026-03-24 um 07.41.48](https://europe1.discourse-cdn.com/flex013/uploads/brevo/original/2X/5/551affc2c18f59e8ca26c9319c0c23b500fa3e2e.png)

Any thoughts on this or other best practive approaches for managing a lot of languages without too much pain?

Cheers  
Jan

---

<div class="post-metadata">

### Author: ![adam](https://dub1.discourse-cdn.com/flex013/user_avatar/community.brevo.com/adam/32/1337_2.png) [@adam](https://community.brevo.com/u/adam)
#### Post date: [Avril 11, 2026, 5:42 UTC](https://community.brevo.com/t/multi-branch-splits-in-automations-how-to-activate/7019/2 "2026-04-11T17:42:35Z")

</div>

Hi @janpeini,

Thanks for reaching out and sharing your use case! Managing 12+ languages in automations is definitely a challenge.

To confirm, **multi-branch splits are only available on Pro and Enterprise plans** , so an upgrade would be required to access that feature on your current Business plan.

That said, there are a couple of workarounds that could help in the meantime:

- **Yes/No conditional splits** based on a contact attribute (e.g., language) — you can chain these together to route contacts into the correct language path, which avoids the need for multi-branch splits entirely.

- **A language contact attribute** is the key here: if each contact has a «&nbsp;language&nbsp;» field set in their profile, you can use conditional splits to check for each language one by one and direct them accordingly.

While it’s not as clean as a multi-branch split, it can significantly reduce the complexity compared to building separate automations per language.

Thanks, Adam