# How to keep a consistent brand voice across channels when site managers write

To keep a consistent brand voice across channels, turn the voice into rules a draft can fail, write them from the best writing your people have already done, and check every draft against them and against a current record of what is true. A guide read once at induction will not hold it.

Date: 2026-11-04
Reading time: 2 min
Author: OCTYN
No. 22

A brand voice guide usually says something like warm but never casual, which is no use to a shift manager answering a one star review at eleven at night. That manager read the guide once, at induction, in the same week they were learning the till.

Most advice on keeping a voice consistent across channels assumes a marketing team with time to read drafts. In a company with many sites, **a lot of the words customers read are written by people whose job is something else**.

## Who is actually writing

Say you run operations for a group of sixty restaurants. Head office writes the campaigns, and those come out fine. Everything else comes from the sites: review replies, the notice on the door when the fryer is down, the local page, the text when an order is late. Give each site five of these a week, a made up number and probably a low one, and you have **three hundred pieces of writing a week** that your one brand manager will never see.

So the voice follows the rota. Regulars can tell who is on from how the apology reads, which makes this your problem as much as marketing's, since the rota is yours. Sending everything through head office sounds safe until a one star review has sat unanswered since Friday and the person who could approve the reply is back on Monday.

## Rules a draft can fail

**Warm but never casual cannot be tested**, so nothing ever fails it. Go and find the manager in your group whose replies customers thank them for, read a few months of what they wrote, and work out what they do. Then write it down as rules a draft can break.

| The guide says | A rule a draft can fail |
|---|---|
| warm but never casual | say what happened before saying sorry |
| owns its mistakes | never write any inconvenience caused |
| local and human | name the site and the person signing |

Keep a separate voice for each person who writes well, built from their own writing, with the same hard rules sitting over all of them. Your managers can go on sounding different from each other. The rules stop any of them sounding like a form letter, and **the check runs on every draft before it goes out**.

## The part a guide cannot do

The inconsistency a customer remembers tends to be something like one site promising a refund in three days while the next one says a fortnight, after the policy changed in March and only half the managers heard. A voice guide has no way of knowing that.

Catching it takes **one written record of what the company knows and has said**, kept current, with every draft pulled from it. In the [Content Engine](/systems/content-engine) OCTYN runs, **a draft with nothing in the record behind it is not written**. That engine runs the founders' accounts on X on a daily cadence, as recorded on 6 July 2026, which is a long way from sixty restaurants, so weigh it accordingly.

At your sites, the manager still reads the draft and still decides what the customer is owed, because a free dessert is a [judgement call](/glossary/human-in-the-loop) about a person at a table.



The old guide can stay on the drive, where it has always been.

## Related

**Systems this bears on**

- [Content Engine](https://octyn.co/systems/content-engine)

**Case studies cited**

- [fullsend](https://octyn.co/casestudies/fullsend)

**Terms used here**

- [Human in the loop](https://octyn.co/glossary/human-in-the-loop)

**Read next**

- [A cold email system that does not burn your domain sends fewer emails than you want](https://octyn.co/blog/a-cold-email-system-that-does-not-burn-your-domain-sends-fewer-emails-than-you-w)
- [The hidden cost of switching between tools is the answer stitched by hand](https://octyn.co/blog/the-hidden-cost-of-switching-between-tools-is-the-answer-stitched-by-hand)
- [Rollback plan for an AI workflow: what can still be put back after it acts](https://octyn.co/blog/rollback-plan-for-an-ai-workflow-what-can-still-be-put-back-after-it-acts)
- [Tracking a trade order from quote to delivery without losing status midway](https://octyn.co/blog/tracking-a-trade-order-from-quote-to-delivery-without-losing-status-midway)

More on growth systems: [Growth systems](https://octyn.co/blog/topic/growth-systems)

Canonical: https://octyn.co/blog/how-to-keep-a-consistent-brand-voice-across-channels-when-site-managers-write