Clouted

Keep brand voice consistent across supporting accounts

A voice guide is more useful when it shows what to write than when it lists adjectives. Clouted helps teams define what the supporting account can say, how it sounds, and when it should route a response elsewhere.

Give editors examples they can use

  1. 01Collect useful examples and opposites

    Show the wording the brand uses for a demo, a reply, and a correction. Include a few examples of claims or tones that don't fit.

  2. 02Allow the page some room within the guardrails

    A tutorial page can be more direct than the main campaign feed without borrowing an unrelated creator's voice. Keep terminology and approved product facts consistent.

  3. 03Put revisions back into the guide

    If a correction applies to more than one post, update the examples or claim library rather than repeating the same review note each week.

Frequently asked questions

Can the page be more casual than the main feed?

Yes, if the tone fits the audience and the brand approves it. Casual shouldn't mean inaccurate or unidentifiable.

Should creators repeat approved copy word for word?

Use exact language where required for substantiated claims or disclosures. Leave room for natural delivery in other parts.

Who reviews sensitive topics?

Name the teams responsible for legal, product, and support issues rather than asking an editor to decide alone.

Can tone vary across markets?

Yes. Keep brand accuracy and standards while letting a local reviewer adapt phrasing and references.

Plan a brand voice guide for supporting pages