Brand voice is one nested greeting, not a style PDF

What a writer repeats is not the whole letter.

It is how you open, how you say the name, how you close. Copy a “warm” greeting, a “formal” greeting, and a “seasonal” greeting into twenty documents, and in a quarter nobody knows which line is still official.

Keep one outbound greeting. Every template nests it. Change that one snippet. The voice changes with it.

CodeExpander

Snippets

Signature

sig

Greeting

Abbreviation

sig

Content

Ada | Engineer ada@example.com

This computer · expansion on

Main window: groups → snippets → editor. Organization groups are locked read-only.

One greeting, not a 32-rule handbook

Do not start by writing brand tone as a PDF. Make the greeting you already approved.

Install and grant accessibility. Type the abbreviation in whatever is focused and press Tab. See Getting started.
Create brand-hello and brand-sign. Do not call them hello or thanks. See Groups.
Outbound mail, release notes, and event replies are “nested greeting + FillIn body.” See FillIn.
Expand in mail or the editor. The popup only asks for the name and what this message is about.


%s:brand-hello%

%filltext&name=name%,

%fillarea&name=what this message is%

%fillcheck&name=calendar line&default=Dates follow the note in this email.%

%s:brand-sign%

%s:brand-hello% holds only the finished open. Do not put the body in there. The body changes every time; that is %fillarea%. If you truly need a second voice (internal note versus public post), make a second greeting with a different abbreviation. Do not annotate one sentence with “delete this when formal.”

If a paragraph already exists as Markdown, paste it into the snippet’s rich text editor: it can detect Markdown and, after you confirm, turn it into formatted body text. That sentence is about paste-into-the-library, not about dictation, and not about how a WeChat official-account post will look.

Which field

What changes	Use
Name	Single line `%filltext%`
This message	Multiline `%fillarea%`
A date line that is only sometimes present	Optional `%fillcheck%`
Internal versus public opens	Conditional `%fillswitch%`, or two greeting snippets

Do not write “replace with the current campaign name” inside the greeting. The campaign name is FillIn. The greeting stays still.

The signature loop does not change because you write for a brand: the focused field, the abbreviation, the trigger key, a local replace. A style PDF cannot do that. A nested snippet can.

Where it may fire

If mail, docs, and the browser all need the same voice, leave the brand group global. If it wrecks an IDE, turn on ExpandIn (Pro) and keep the writing apps.

Sharing that one greeting is organization shared groups. The website edits a cloud copy. Expansion authority is still the local library after sync. See Team copy.

This is not a dictation product. The public site does not ship a “hold to talk” tutorial. Voice, in this article, means the sentence you already wrote and nested. It does not mean a microphone.

Do not

Do not send a style PDF and call the tone unified. A PDF does not expand in a text field.
Do not copy the greeting twenty times. Nest %s:brand-hello%.
Do not read this as a speech-to-text manual. Voice input is not documented here as a shipped website feature.
Do not use English words as abbreviations. See Abbreviation hygiene.