Documentation version: 2026-10-02.6 Canonical: https://docs.creator.gg/guides/social-writing.md # Social writing in the business's own voice Use this guide when drafting or editing social posts, captions, announcements, founder posts or replies. The aim is specific, believable writing that fits the speaker and the reader. Sounding natural does not require sounding casual. This is editorial guidance, not a publishing workflow or a promise to defeat AI detection. ## Platform writing rule Across every Creators business, do not use em dashes in agent-authored prose. This applies to responses, plans, website copy, email, social posts, captions and replies. Use full stops, commas, colons or parentheses, or rewrite the sentence. Preserve necessary hyphens, minus signs and exact quotations, code, URLs or identifiers; do not alter literal source material to satisfy a prose rule. ## Establish whose voice this is Use the current request, approved wording, the business's voice guidance and genuine writing samples. With a connected workspace, read intelligence_get for the current business context; without one, work from the supplied brief and samples. Free drafting needs no connection. Use existing context before asking the user to repeat it. Identify the account owner, audience, language or locale, purpose of this particular post, confirmed facts and any accompanying media. A company announcement, an employee's personal observation and a reply to one person are different voices even when they concern the same business. Do not assume the author is a founder or personally used a product. Translate evidence into a small working voice brief: - Register and relationship: formal, conversational, technical or playful; speaking as a company, a professional or a person. - Rhythm and mechanics: sentence length, paragraph density, contractions, capitalization and punctuation, drawn from actual samples. - Vocabulary and personality: terms this audience uses, the degree of warmth or humor, and topics or expressions the business avoids. - Boundaries: confirmed claims, required wording, disclosure needs and whether a call to action belongs in this post. Treat inferred style as provisional. If no samples are available, use clear, restrained language with normal sentence case and little ornament; state that assumption briefly outside the copy when it matters. Ask for a sample only if the missing voice would materially change the result. Do not turn a small writing request into a brand questionnaire. Learn from human-authored or explicitly voice-approved samples. Previously generated drafts and published copy of unknown authorship can show repetition or factual context; do not automatically treat them as proof of the person's voice. Keep each company's samples and preferences in its own private context. Shared guidance must not contain customer copy or impose another customer's persona. Lowercase, very short replies, slang, emojis and cheekiness are possible voice choices, not universal rules. The platform-wide em dash restriction above applies across businesses. Preserve deliberate formality, technical precision, local language and distinctive cadence. Follow explicit user direction over an inferred profile; approved text stays intact outside the requested edit. ## Give the post a real point Choose what this post needs to do: explain a change, show something useful, express a supported opinion, tell a specific experience, invite a relevant action or acknowledge someone. Write the complete requested copy. Do not deliver only a hook or a description of the post. Lead with the meaningful detail rather than a ceremony about announcing it. Connect each sentence to the preceding one. Use a concrete example, observation or action when it helps the reader understand the point. A structure such as observation, example and implication can help, but it is not a template every post must follow. Short notices may need one sentence; a considered explanation may need several paragraphs. Earn the conclusion. If the draft says a feature saves time, name the step it removes when that is known. Do not attach an unsupported productivity claim. If the logical link is missing, repair the reasoning or remove the claim instead of polishing the same vague sentence. Let the supplied facts set the limits. Do not invent features, customer quotes, prices, availability, deadlines, scarcity, metrics, results or personal stories. Do not add a founder origin story, hardship, private conversation or first-hand experience to make a post feel human. Describe only media that has actually been inspected or clearly label a proposed visual as a brief. Put essential unresolved facts outside the publishable copy; for an otherwise useful draft, omit unsupported details or clearly mark placeholders. ## Remove the patterns that make copy interchangeable Look for habits that add polish without meaning: - Generic openings such as "In today's fast-paced world" or "We're thrilled to announce" that postpone the actual news. - Inflated benefit words such as "game-changing", "seamless" or "unlock your potential" without a concrete explanation. - Automatic rhetorical turns such as "It's not just X. It's Y", dramatic fragments, manufactured cliffhangers or a punchline after every paragraph. - The same three-part list, emoji bullet pattern, one-line paragraph ladder or hook/body/CTA structure across unrelated posts. - Source summaries passed off as replies, generic praise and claims of profound insight where a small reaction would be enough. - Questions such as "Thoughts?" added only to seek engagement, or a sales pitch appended to every observation. These are editing signals, not a banned-word detector. A phrase or punctuation mark is not inherently artificial. Replace empty language with a relevant fact or remove it; do not swap one fashionable phrase for another. Do not fake typos, slang, vulnerability, controversy or enthusiasm. Formal writing can be natural; forced informality can be as generic as corporate jargon. Use enough detail to make the point intelligible. Cutting every sentence into fragments or deleting connective reasoning does not make the result more human. Read the draft aloud in the intended speaker's register. If a sentence would fit dozens of unrelated businesses unchanged, make it specific or cut it. ## Adapt to the kind of writing **Company posts and announcements.** State what changed, who it is for and what the reader can now do, using only confirmed facts. Give enough context for the audience's familiarity. A launch can include enthusiasm when it is supported by the brand voice; it still needs actual news. Match any next step to the purpose instead of automatically asking for comments or a demo. **Personal or founder posts.** Use the person's actual involvement, observation and reason for caring. A clear opinion can stay an opinion. Do not manufacture universal lessons, founder credentials, a dramatic journey or borrowed experiences. Preserve the distinction between what the person thinks, what they observed and what evidence establishes. **Captions and short video copy.** Add useful context, a detail or a reason to watch rather than merely narrating what is already visible or repeating the title. Let the media carry what it shows. A caption may be short or substantive; length follows its job and the audience. Do not claim to have seen an attachment that was unavailable. **Replies and comments.** Respond to the particular person's actual point with one natural intent: a specific acknowledgement, useful addition, relevant reaction, honest question or fitting joke. A brief reaction is enough; do not demand a clever takeaway or turn it into a miniature review. Avoid repeating the source's headline, echoing its hype or adding an unrelated product pitch. Do not pretend to have saved, bought, used or recommended something. If the evidence is insufficient for a meaningful response, explain that briefly instead of forcing one. Editorial help with reply text does not imply that the connected tools can publish replies. **Channel adaptations.** Adjust context, length, rhythm and any next step for the selected audience and placement while keeping the facts and voice intact. Do not automatically turn LinkedIn into a motivational essay or every short-form caption into slang. Adapt in the requested language instead of mechanically translating English marketing idioms. Preserve approved copy unless rewriting is requested; identify a concrete format conflict separately. Read the current social and social-media guides for publishing limits rather than inventing capabilities. ## Vary the thought, not just the synonyms When recent posts or replies are available, check whether the new draft repeats their opening, angle, cadence, praise or ending. Recent drafts are comparison material, not sentences to remix. Do not solve overuse of "great" by making "love this", "bookmarked" or "hope" the new default. For a requested batch, give each post a distinct reason to exist while retaining a coherent voice. If the user wants alternatives, vary the angle or emphasis meaningfully rather than producing the same template with new adjectives. Do not invent new claims to create variety. For a small correction, make the focused edit rather than generating unsolicited options. ## Worked editing examples All businesses, facts and samples below are fictional teaching examples. Use the editorial reasoning, not their wording or facts, for real customers. ### Neighborhood bakery: useful, warm and direct Confirmed brief: the bakery will open at 7 a.m. on Saturdays starting this week. Its customers ask about an earlier pickup time; its voice is friendly and plain. Generic: "We're thrilled to elevate your weekend with an exciting new chapter in your morning routine!" Revised: "Picking up breakfast early? From this Saturday, we open at 7." The revision supplies the actual change and a relevant customer situation. The question serves the message; it is not a request for engagement. It does not invent a promotion, a product or limited availability. ### Business software: concrete product news Confirmed brief: users can now save a report's filters and reuse them next month. No measured time-saving result is available. The audience knows the report feature. Generic: "Reporting just got a game-changing upgrade. Work smarter, not harder." Revised: "Set your report filters once. Next month, reuse the saved view instead of choosing them again." The benefit is the known step the feature removes. There is no invented percentage, guaranteed result or obligatory demo pitch. ### Professional service: formal can still sound natural Confirmed brief: an accounting firm now offers appointment booking online. Clients can choose a time and receive an email confirmation. Its voice is formal, calm and concise. Generic: "Say hello to seamless scheduling and goodbye to the hassle." Revised: "You can now book an appointment online. Choose a time that suits you; we will confirm it by email." The revision preserves the firm's register and states the practical change. Making it lowercase or adding a joke would weaken this voice. ### A personal reply: respond to the useful detail Source: a maker says that putting the assembly instructions on the box stopped people having to find a separate leaflet. The replying person has supplied no product-use experience. Generic: "Love this! A powerful reminder that great design is all about putting the user first." Revised for a concise conversational voice: "One less leaflet to lose." The reply reacts to the specific situation without restating a thesis or pretending to have used the product. Its length and register are choices for this speaker, not a rule for every reply. ## Final editorial pass Before returning the copy, check: 1. Can the reader tell what the post means and why its sentences belong together? 2. Does it contain a supported detail or a specific reaction, rather than interchangeable claims? 3. Does it fit this company or person's actual voice, language and relationship to the audience? 4. Are every factual claim, personal experience and visual description supported? 5. Have repeated hooks, empty praise, forced questions and unnecessary sales endings been removed without flattening the voice? 6. Does it respect the requested format, approved wording and purpose? 7. Is newly written prose free of em dashes, with literal quotations and technical strings preserved accurately? Return the finished copy first, with only necessary assumptions or unresolved facts outside it. Do not attach a long critique unless requested. Editorial checks improve the draft; they do not establish human authorship, predict engagement or guarantee any result.