Get my team posting

Why use it

Employee advocacy fails the same way every time. One person writes a good post, sends it to twelve colleagues, and by mid-morning the feed shows twelve identical paragraphs with the same line breaks. Everyone can see what happened, and what it communicated is that none of them meant it.

What it does

It separates the message, which is one sentence everyone agrees on, from the posts, which should be twelve different things. Each person is asked what they actually did or saw: the engineer who built the hard part, the person who took the support calls, the person who argued against it. Same message, different evidence. Then it writes in their words rather than the brand's.

What you get

• One agreed message, written down before anybody drafts anything
• A distinct angle per person, taken from what that person actually saw
• Drafts matched to how each person already writes, including in Slack
• The things not to ask for: organised comment blocks, hashtag lists, uncleared numbers

What it will not do

It will not write the same post twelve ways. If the only difference between the drafts is word order, the answer is fewer posts. It will not ghostwrite in a voice the person has not seen and approved.

What changes when VoiceMoat is connected

Advocacy is a multi-person problem, which is the one case a single voice profile cannot serve on its own.

• list_profiles Returns the accounts on the team, so each draft is written against the right person rather than against a house style.
• get_voice_profile Gives that person's own trained profile, which is the difference between a post in their words and a post with their name on it.
• score_voice_match Scores each draft against its own author, so twelve posts can be checked for sounding like twelve people rather than one.

Team seats are on the Enterprise plan.