One post, a channel menu, not a growth hack
What ops repeats is not a “viral structure.”
It is one finished message: the event name, one fact, where to look. Store full copies for microblogging, mail, and the group notice, and the date changes three times. One copy is always stale.
One body. A menu or a condition for the close. Not a growth class.
Main window: groups → snippets → editor. Organization groups are locked read-only.
One message, not five playbooks
Do not start with a platform calendar. Split the notice you already pasted three times this week.
- Install and grant accessibility. Type the abbreviation in the focused field and press Tab. See Getting started.
- Nest the brand greeting. Do not copy a second voice for social. See Brand voice.
- The body is multiline. The channel is a menu or a condition. See FillIn.
- Expand in the browser or the desktop client. Pick the channel. Confirm.
%s:brand-hello%
%fillarea&name=the finished message%
%fillswitch&name=channel%
%fillcase&opt=short post%
(Short close. Do not repeat the body here.)
%fillcase&opt=email%
Details follow the link in this note.
%fillcase&opt=group notice%
This is for this group. Do not treat a long image as the official post.
%fillend%
%s:brand-sign%Channel branches hold closes and limits. Do not write the body three times. If the event name changes, use %filltext%. Leave the greeting alone.
Which field
| What changes | Use |
|---|---|
| Event name, a short date word | Single line %filltext% |
| The finished message | Multiline %fillarea% |
| Channel | Menu %fillmenu%, or conditional %fillswitch% |
| An occasional “includes an image” line | Optional %fillcheck% |
Do not write “change the channel name before you publish” in the body. The channel is chosen in the popup.
The loop is still local: abbreviation in the focused app, trigger key, replace. That is enough when the same sentence has to leave the building through more than one client. It is not a scheduler, and it is not an engagement dashboard.
Official-account paste is another renderer
The WeChat official-account editor is a different rendering path. This website article is Nextra. A WeChat post still needs a separate paste, usually through the TouGaoYa component set used for that channel. Do not expect desktop-expanded rich text to look the same after you drop it into WeChat.
Do not claim “Tab equals a finished official post.” Desktop expand solves repeated sentences in a text field. Official-account layout, outbound links, and cards still follow WeChat’s rules.
Where it may fire
If the browser, mail, and desktop chat all need the same notice, leave the group global. If it wrecks an IDE, turn on ExpandIn (Pro) and keep the apps you actually post from.
Sharing the notice is organization shared groups, not “final_v7” in the group chat. See Team copy.
Do not
- Do not write this as growth hacking, competitor teardown, or a best-time-to-post chart. That is not a snippet.
- Do not clone the full text per channel. The channel is a menu.
- Do not claim expanded rich text equals official-account layout.
- Do not use
post,viral, orwechatas abbreviations. See Abbreviation hygiene.
Related: Brand voice, Support templates.