Brand voice and tone
Brand voice and tone
Set how replies sound — tone, formality, greeting, sign-off, length, emoji and words to use or avoid — without touching your answers.
Brand voice changes how TR-AI writes, never what it is allowed to say. Until you change something, replies stay exactly as before. The same voice applies to email replies, the chat widget, messaging, the phone agent and procedures.
| Setting | Options |
|---|---|
| Tone | Friendly, professional, concise, warm or technical |
| Formality | Formal or informal — in languages with a formal “you” (Sie, vous, usted) TR-AI uses the matching form |
| Greeting | “Hi Sam,” (name, the default), “Hi there,” or no greeting |
| Sign-off and signature | Your own closing line and signature block |
| Reply length | Short, medium or long |
| Emoji | Allowed (at most one), never, or no rule |
| Words to use / avoid | Your product names and phrases, and words you never want in a reply |
| Extra instructions | Free-text style guidance, e.g. “Refer to customers as members.” |
- 1Open Brand voiceDashboard → Brand voice. Your default brand is created on first visit with nothing set.
- 2Pick the basicsTone, formality, greeting, length and emoji cover most of what customers notice.
- 3Check the previewThe editor shows a sample reply and the exact style block added to the prompt — no AI call needed.
- 4SaveThe next ticket uses the new voice.
Note:Voice settings are style only. Instructions that try to override TR-AI’s rules — reveal internal notes, name competitors, promise refunds — and links outside your brand’s domains are removed, and the editor shows what was removed and why.
- A custom sign-off replaces “Best regards,” in English replies; replies in other languages keep their own natural closing.
- Sensitive-topic and billing escalation replies keep their standard wording.
- Brand voice costs nothing extra — no additional AI calls.
Tips & tricks
- Start with tone and length only, read a week of replies, then add words to avoid — small changes are easier to judge.
- Put your product’s exact spelling in “words to use” (e.g. “TicketResolve”, not “Ticket Resolve”).
- Use “short” for chat-heavy teams; customers in the widget skim.
- Want proof a new tone works? Run it as an A/B experiment before rolling it out to everyone.