Change the signature once. Do not paste it ten times.

The phone number changed. You open the library, fix the first letter, the second, the third. The fourth is the one a customer sees next week.

A copy is not reuse. A copy is ten bodies that will go stale. A shared block should exist once: the signature, the greeting, the one legal line that says confirmation is written. Change that one. Every letter that points at it changes.

The token is %s:abbr%. From 7.0.0, expand replaces it with the referenced snippet’s body. On older desktops you could type the token; it did not follow. Syntax is in FillIn.

A pointer, not a second paste

Start with a short signature, abbreviation xsig. Do not paste the number again in the mail template:

%s:cs-hello%

%filltext&name=name%, regarding %filltext&name=topic%:

%fillarea&name=body%

%s:xsig%

Change the mobile number in xsig. The next expand of every template that nests it carries the new number. Change the tone in cs-hello. The same batch of letters changes voice together. Nesting can go one level deeper. Do not make a cycle: A includes B, B includes A. That expand does not insert, and it does not eat what you already typed in the front app.

What follows %s: is an abbreviation, not the snippet title. Rename the abbreviation and every pointer must change with it; change only the signature body and the pointers stay. A missing abbreviation also refuses to insert. Check that the snippet still exists. If the nested snippet has FillIn fields of its own, those boxes join the same popup — a second window does not appear. A case transform can sit on the nest — %s:xsig&case=upper% — when you actually need it.

How a support desk splits structure is Support templates. This article is why you stop pasting.

The team block is one copy too

The outward greeting should not live as a local paste on every machine. Put it in an organization shared group. Personal letters nest its abbreviation. After coworkers sync, they type their own letters and the greeting is already the team one.

Organization groups are locked on the desktop: they still expand here; you edit the body on the web. You are editing the cloud copy. The next sync brings it down. Expansion authority is still the local library that has already synced. How to move a group and how to invite is Shared groups. Nesting is not the sync switch.

Brand voice is one nested greeting, not another style PDF.

Tonight, peel the signature out

1. Take the closing you have been pasting and make it its own snippet. Keep the abbreviation short but not an English word — xsig. See Create.
2. Open one letter you still send. Delete the pasted closing. Write %s:xsig%. Save.
3. Change one word in xsig. Expand the letter in mail. If the closing followed, nesting works. If the desktop is older than 7.0.0, update first or the token stays a token.

Free 50 snippets and 5 groups are enough to split a signature and a greeting. Organization sharing is a Team seat, a different bill from local expand. Amounts live in Pricing.

Do not

• Do not paste the signature into a tenth letter. Missed edits are what copying produces, not a personal failing.
• Do not let two snippets nest each other, and do not nest a snippet into itself. A cycle does not expand.
• Do not expect a desktop before 7.0.0 to treat %s:abbr% as a real expand. The mark is there. The body is not.
• Do not use nesting as a stand-in for organization access. A group you never shared cannot be found by a coworker who nested it.

Next: Shared groups.