Lets say my website has a public facing (B2C) section and a professional (B2B) behind login
I want to use the same document types, but different Brand Voice depending on which section I’m in
Is this possible?
Hi jonas
Great question! The short answer is: not natively out of the box today, but there are workable approaches.
//not an official HQ reply
The current Umbraco.AI context system is global you define Brand Voice and other context entries in Settings, and they apply to your configured agent across the board. There’s no built-in way to resolve a different context based on where in the content tree a node lives.
Your scenario (same document types, different Brand Voice depending on whether you’re in the B2C or B2B subtree) is a tree-path-awareness problem, which is a step beyond what the current context model handles.
A few workarounds to consider and should be possible:
-
Two agents, two contexts — Set up a “B2C Agent” and a “B2B Agent”, each with their own Brand Voice context. Editors working in each section manually select the appropriate agent in the Copilot UI. Not automatic, but functional and available today.
-
Custom context injection — The Umbraco.AI foundation is extensible. A developer could hook into the context resolution pipeline and inject the correct Brand Voice based on the current node’s ancestors (i.e. check whether the node sits under the B2C root or the B2B root). More work, but a clean solution.
-
Store brand voices in the CMS — Keep both brand voices as properties on a root or settings node, then resolve the correct one at editing time via a custom Umbraco.AI extension.
Longer term, with the Agent feature targeting Q2 2026 and continuous capability additions planned, tree-node-aware context switching feels like a natural evolution. Might be worth raising as a feature request with the team directly!
Hope that helps 
This is possible yes. Umbraco.AI comes with a context picker property editor, you can add this to your context and pick a context that is relevant to that page + it’s decedents. This way you can have a different tone for say your blogs as opposed to say your legal section.
When a context picker is setup, when you execute a prompt / agent call, if there is a document based entity context, it will navigate up it’s tree till it finds a context picker and apply that.
Until the docs are merged into the docs site, you can find out more here Umbraco.AI/docs/public/concepts/context-picker.md at 73183e8e6286b6779e375a207dbafcf0d95e102c · umbraco/Umbraco.AI · GitHub
2 Likes
ohh missed thaaa!
So in your case, you can set different Brand Voices at the B2C and B2B roots, and it’ll apply to everything underneath.
Way simpler than what I suggested before 
hehe
1 Like