Claude for Social Media Posts: Voice, Drafts, and Review

Use Claude for social media posts by supplying approved campaign facts, examples of your voice, and a separate request for each platform. Review every draft for accuracy, audience fit, and publication requirements before posting it. fenbs can keep the reusable prompts, voice rules, and campaign decisions available when a different assistant helps with the next round.

The goal is a draft you can edit with confidence. Asking for a month of content before agreeing on the message often produces a long list of variations on an unclear idea. For product background, start with what Claude AI is.

How do you start from approved campaign material?

1. Choose one campaign goal, such as helping existing customers understand a product change. Identify the intended audience and the action they should take.
2. Provide approved facts, the landing page, relevant dates, and any required wording. Mark draft ideas separately from claims cleared for publication.
3. Add a few posts that represent your voice. Explain why each example works and what should not be copied.
4. Request a small set of post angles before complete captions. Pick the useful angles, then ask for platform-specific drafts.
5. Check the content with a person, preview it in the publishing tool, and record the changes needed before approval.

Say a design studio is announcing a new consultation service. Its approved facts might cover who it serves, what the consultation includes, and where to book. Claude should not add a satisfaction claim, client testimonial, or availability promise that the studio never supplied.

How do you teach Claude your brand voice?

Describe observable choices instead of broad adjectives. “Friendly and professional” gives little direction. “Use short sentences, explain the practical benefit, avoid exaggerated claims, and ask one direct question” gives you something to check in the output.

Claude Projects lets you add reference files and instructions for project chats↗ (opens in a new tab). Use that space for your current voice guide and approved examples. Keep campaign-specific exceptions in the request so they do not quietly become permanent brand rules.

• Keep: the words customers actually use for the problem and the approved names of your services.
• Avoid: invented urgency, unsupported superlatives, and phrases the brand would never say.
• Show: one strong example and one weak example, with a short explanation of the difference.
• Specify: whether emojis, hashtags, questions, or first-person language suit this audience.

After a few drafts, tighten the guidance around real corrections. A rule about avoiding technical abbreviations is more useful than a growing list of dislikes. Save accepted voice rules in fenbs Decisions and rules when several connected AI apps need the same direction.

Which prompts produce useful platform variants?

Give each version a job. A professional network post may need context and a reason to discuss the issue; an image caption may need to explain what the image shows. Treat these as editorial choices for your audience, rather than universal rules about what a platform rewards.

Try this request: “Using only the approved facts below, propose three post angles for this audience. For each, give the reader benefit and the source that supports it. Do not write captions until I choose an angle.” This separates message selection from wording.

Then ask: “Turn angle two into a concise LinkedIn post and an Instagram caption. Keep the same factual meaning. Make each opening useful without the other version. Include the required disclosure exactly as supplied, and put unresolved questions after the drafts.” Set your own length targets and check current platform limits in your publishing tool.

For revision, name the failure: “The opening promises more than the service provides. Replace it with the specific benefit in source two, and keep the remaining approved facts.” Ask for a small number of meaningfully different alternatives. A dozen near-identical openings makes selection harder without improving the underlying message.

What needs human review before posting?

Read the draft as a public statement from your organization. Check names, dates, links, product descriptions, and whether a hypothetical example now sounds like a real customer story. Verify quotations against their source and confirm you have permission to use any personal details or images.

For US audiences, the FTC disclosure guide↗ (opens in a new tab) explains when a relationship with a brand needs to be disclosed and why the disclosure must be easy to notice. Preserve required disclosures through every revision and check their placement in the actual post preview.

Do not ask Claude to manufacture a testimonial or pretend a brand message is an independent opinion. If a post includes an endorsement, use verified material and the review process appropriate to your work. An AI-generated compliance checklist does not replace the person responsible for approval.

Finally, inspect the complete post: image crop, caption breaks, alternative text, destination link, and any text cut off in preview. Read it aloud. Remove repetition and filler, and confirm that the requested action matches the landing page. Approve the final version, not an earlier draft with a similar title. The Claude Design guide covers the neighboring visual workflow.

How do you revise posts without losing campaign decisions?

Keep three things distinct: a draft, feedback on that draft, and a decision about the campaign. “Try a warmer opening” is feedback. “Use customer education rather than a discount message for this campaign” is a decision that affects later posts.

Save the reusable drafting and review request after it produces useful results. Include the inputs it needs and the checks the reviewer still performs. Store one current version, and record why a meaningful change was made so another person can maintain it.

The guides to ChatGPT for social media posts and AI social media post generators cover neighboring choices. Whatever assistant you use, fenbs can retain the approved campaign direction instead of making the next session reconstruct it.

How to do this with fenbs

1. Create a free account and add your campaign as a project on your kanban board.
2. Record the human-approved voice rules and campaign choices in Decisions and rules. Keep the approved source locations in Links and listings.
3. Add your reusable drafting request to Skills and prompts, and create tasks for factual questions and reviewer corrections.
4. Connect Claude through the integration guide. Ask it to read the campaign context before drafting and save progress with the remaining review work before stopping.

fenbs does not schedule or publish social posts. A dedicated publishing tool is the better fit for a calendar, previews, and publishing; use fenbs when keeping prompts and decisions consistent across assistants is the missing piece. Explore more practical workflows in AI at work.