Brand voice notes
Write the rules once per site; every agent reads them.
Voice notes are a free-text field on each site. Whatever you write there is returned by get_site_context, so an agent reading context before publishing picks up your house style without you re-explaining it in every conversation.
Setting them
- 1Open Sites in the dashboard and choose the site.
- 2Write the notes in the brand voice field.
- 3Save. The next get_site_context call returns them.
What to put in them
- Tone in a sentence: "Plain, direct, no exclamation marks."
- Person and tense: "We, not the company name. Past tense for releases."
- Spelling and formatting conventions: British spelling, sentence-case headings, no emoji.
- Words to avoid, and words to prefer over them.
- Structural defaults: an intro paragraph before the first heading, a short summary at the end.
- Which categories to use, and not to invent new ones.
Keep them short and concrete. "Avoid the word 'leverage'" changes output; "be engaging" does not. The field holds up to a few thousand characters — you will not need most of them.
What they are not
Voice notes are guidance to a model, not enforcement. An agent can ignore them, and different models follow them to different degrees. If a rule genuinely must not be broken — a term that can never appear — put it in the site's blocked terms under a guardrails policy, where it holds the post for review rather than trusting the model.
What can go wrong
- The agent never called get_site_context, so it never saw the notes. Ask it to read context first.
- The notes contradict what the person asked for in the conversation. The immediate instruction usually wins.
- Notes so long they dilute themselves. Cut them back to the rules you actually care about.

