Using AI to Write Content Plans and Captions Without Losing the Client's Brand Voice

Paul Boards ·

To use AI for content plans and captions without losing the client's brand voice, the AI needs to get the voice in writing, with real examples, before every request. A short guide with words the client uses, words they reject, three approved captions, and three rejected ones makes more difference than any elaborate prompt. Human review is still mandatory, but it becomes fine-tuning instead of a rewrite.

Without that material, the model writes like the average of the internet: friendly sentences, emojis where they don't belong, verbs like "transform" and "empower." The copy is correct and doesn't sound like anyone. This article shows how to build the guide, how to ask for the content plan and the caption, and how to review without spending more time than if you'd written it by hand.

Why AI loses the brand voice

A language model predicts the most likely text for the request it receives. If the request is "caption for an English school post about enrollment," the most likely result is the text thousands of schools have already posted. A specific client's voice is exactly what departs from that average, and AI only gets there if you show it the way.

Three failures show up almost every time:

  • Swapped vocabulary. The client says "student," the AI writes "learner." The client says "trial class," the AI invents "demo lesson."
  • Wrong register. The brand is understated and the AI adds exclamation points and emojis. Or the brand is lighthearted and the copy reads like a legal notice.
  • Promises the client doesn't make. "Fluency in six months" can show up in a draft even if the school never promises a timeline. That's a risk, not just a tone mistake.

How to build a brand voice guide AI can follow

The ideal guide fits on one screen. Long brand documents help designers, but for AI what works is concrete examples. Use this structure:

  1. Who's speaking. One sentence: "The school speaks like an experienced teacher who treats adult students like adults."
  2. To whom. The main audience with one useful trait: "Professionals aged 28 to 45 who have tried to learn English before and gave up."
  3. House words. The terms the client uses and wants to see: trial class, small groups, conversation.
  4. Banned words. What never appears: guaranteed fluency, revolutionary method, don't miss out.
  5. Format rules. Caption length, emoji use, opening with a question, accepted calls to action.
  6. Three approved examples. Real captions the client praised, with one line on why.
  7. Three rejected examples. Drafts that were sent back, with the reason. This item usually teaches more than the approved ones.

In Scrumboards, this material lives in the client profile, with brand voice, target audience, and competitors, and in the Brand Kit, alongside logos, colors, fonts, and references. The agents read from there, so whoever asks for a caption doesn't have to paste the guide every time. See how it looks on the management platform for agencies and teams.

Content plan first, captions second

Asking for a caption without a content plan produces copy with no topic. The order that works is to define the month, then each post, and only then write.

How to ask for the monthly content plan

Give the AI what it doesn't know: the client's key dates, campaigns in progress, what worked last month, and what the client asked to avoid. A good request looks like this:

"November content plan for the school: 12 feed posts. Enrollment for January classes opens on the 10th. Behind-the-scenes posts with teachers got more comments in October. The client doesn't want a Black Friday post. For each post, include topic, goal, suggested format, and a one-line hook."

The response becomes a draft calendar. The team cuts what doesn't make sense, reorders posts, and sends it for client approval. In Scrumboards, the content calendar is separated by client, and each post already has a date, preview, and approval status.

How to ask for the caption

For each post approved in the plan, ask for two or three short versions with a clear difference between them: one opening with a question, another with a fact, another with an everyday scene. Comparing different versions helps you see what sounds like the client.

Include the post's goal and the call to action in the request. "Caption for the behind-the-scenes post with teacher Ana, goal is to drive trial class sign-ups, CTA: link in bio" gets much better results than "caption for the teacher post."

Have a client whose voice nobody on the team nails on the first try? Add that client to Scrumboards for free and ask ORION for the first content plan using their profile.

Review with four checks

Reviewing AI copy means watching for things human writing rarely gets wrong. Run each caption through four questions:

  1. Is there a banned or swapped word? Do a quick search for the words on the list. It's the most common mistake and the easiest to catch.
  2. Does it promise something the client doesn't? Timelines, results, discounts, guarantees. Any promise has to actually exist.
  3. Would the client say this out loud? Read it aloud. If it sounds like a generic ad, rewrite the first sentence, which is almost always the culprit.
  4. Do the facts check out? Dates, times, teacher names, address, price. AI fills gaps with what sounds plausible.

When the same correction comes up twice, it goes into the guide. Today's rejection becomes a rejected example in the client profile, and the next draft comes out better.

Example: before and after the guide

Request without a guide, for the English school: "caption about the trial class." Typical result: an upbeat text with exclamation points, a rocket emoji, and a promise to "unlock your English for good."

Same request with the guide filled in, including the rule "no exclamation points, no timeline promises, mention small groups": "In the trial class, you're speaking English from the first few minutes, in a group of no more than six people. No placement test beforehand. Book through the link in bio." It still needs a tweak, maybe swapping "speaking" for "talking," but it's already in the school's voice.

The difference between the two results came from the material the AI received, not from a cleverer prompt.

Organization that keeps the voice consistent over time

Voice gets lost less in the writing and more when people change. When the copywriter goes on vacation and someone else takes over the account, the guide and the history need to be in the same place as the tasks. A few practices help:

  • Keep the guide in the client profile, not in a loose file on someone's computer.
  • Log approval and rejection comments on the post's task itself, so the reason stays visible.
  • Use the revisions report to see which clients send back copy most often and fix their guides first.
  • Review the guide with the client every quarter, showing the captions they liked most.

If you use another assistant, like ChatGPT or Claude, you can connect it to Scrumboards through the external agent connection (currently in pilot) and work with the same client data.

Frequently asked questions

How many examples does AI need to pick up the voice?

Three approved and three rejected examples already change the result significantly. More examples help if they're varied.

Can I use the entire brand guidelines document?

You can, but a one-screen summary with examples works better. A long manual dilutes what matters.

Can AI publish the caption directly?

It should produce a draft. Publishing goes through team review and, when the contract calls for it, client approval.

How do I know if the voice has improved?

Track how many captions come back with revision requests. If revisions drop month over month, the guide is working.

Does it work for clients in technical fields, like healthcare or law?

It works with more review. In those fields, the banned-words list and fact-checking matter even more.

Build your first client's guide today

Set aside half an hour, gather six old captions from that client, and fill in the profile. Start free and generate December's content plan with their voice already set up. The other tools that come with it, like the calendar and approvals, are in the modules overview, and the site's FAQ section answers the rest. To go back to the start, the Scrumboards home page sums it all up.