> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/brand-voice.md).

# Brand Voice

Brand Voice defines how your organisation sounds. It's used by [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md) on every generation, so every draft starts aligned with your voice instead of needing heavy post-editing.

Open it from **Intelligence > Content Optimization > Brand Voice**.

### What you can configure

* **Voice description** - short narrative of how your brand talks ("direct, lightly sarcastic, respects the reader's intelligence")
* **Tone attributes** - specific dials like confident vs. humble, formal vs. casual
* **Vocabulary** - preferred words and phrases
* **Forbidden phrases** - words or constructions the brand doesn't use
* **Example posts** - the strongest reference posts, used as anchors
* **Starter words** - opening words that reliably hook your audience; Content Forge uses these to front-load strong hooks
* **Length preferences** - per-platform word-count target (short / medium / long) for X, Instagram, and Facebook. Set these once and every generation respects them automatically.

### Version management

Brand Voice supports multiple saved versions. You can generate a new version at any time, compare it against the active one, and promote whichever you prefer. Admins can delete old versions directly from the Brand Voice page to keep the list clean.

> **Note:** New versions reflect your voice at its best, so a single outlier post never skews the result.

### Learning feedback loop from Experiments

[Experiments](/thecontentforge-docs/feature-guides/experiments.md) closes the loop back into Brand Voice. When you record a learning at the end of an experiment, the **Add this recommendation to Brand Voice signature moves** checkbox appends the recommended-future-use text to your Brand Voice signature moves so the next Content Forge generation picks it up. Applying to Brand Voice requires Admin or Owner role; the flag is captured on the learning either way and an admin can apply it later.

### Workflow

1. Start with a short description - 2–3 sentences is enough
2. Paste in 3–5 example posts that represent your voice at its best
3. Set length preferences per platform (short / medium / long)
4. List any hard-no phrases or patterns
5. Generate a few drafts in Content Forge and see what's off
6. Tighten the voice settings based on what keeps needing manual edits

### Tips

* Good example posts matter more than a perfect description. Choose real wins.
* Starter words are detected for you automatically - review them after each new version
* Revisit Brand Voice monthly - brands drift, and old examples can hold you back
* If two team members edit in opposite directions, Brand Voice is where you reconcile


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/brand-voice.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
