agent brand routing
agents need to choose the right voice profile before analysis or rewrite. hold your voice supports direct profile ids and human brand names, but ambiguous names must be resolved.
quick answer
when an account has multiple brands, resolve the brand before calling analyze or rewrite.
use this for
- multi-brand accounts
- mcp assistant routing
- api clients that accept a user's brand name
steps
- prefer a known `profile_id` when the integration already has one.
- use `profile`, `brand`, or `brand_name` only when the user gives a name.
- if the api returns an ambiguity error, show the candidate profiles.
- ask the user to choose before continuing.
- cache the chosen profile id for that workflow when safe.
details to know
- brand routing prevents agents from rewriting a draft in the wrong voice.
- profile resolution is shared by rest and mcp flows.
- ambiguous brand names are treated as a request problem, not a server failure.
limits and edge cases
- do not guess between similarly named profiles.
- do not create a new profile just because a name was ambiguous.
- use the existing profile-resolution page for user-facing brand setup details.
ready to use the product instead of reading about it?
open app