The guide comes before the chatting

When creators complain that a chatting team does not sound like them, the usual assumption is that the chatters were careless. Sometimes they were. Just as often, nobody ever told them what "you" sounds like. A new chatter handed a login and a vague instruction to "be flirty and friendly" will fall back on a generic script, and fans notice generic very quickly.

A voice guide is the document that fixes this. It records how you write, what you will and will not talk about, what you sell and at what price, and what a chatter should do when something falls outside the guide. It is the first thing a chatting team should receive and the first thing you should review. Everything else, including supervision and quality checks, depends on it.

This guide is about writing yours. It is deliberately practical. It covers what to include, how to build the sections from your own real messages without exposing your fans, how to test it with a fictional exercise, and how to keep it current. It does not tell you that you should have anyone chatting for you. Many creators prefer to answer their own messages, and there are good reasons to decide that before reading further. If you are still working out whether you need a chatter at all, our guide on whether you need a manager or just a chatter is the place to start.

A note on sources. Commercial providers publish material on this topic, such as JuicyPulse's chatting team guide, which covers voice examples, handover notes, privacy and supervision, and WhaleFinders' scorecard article, which covers grading messages. Both are industry content from companies with something to sell. They are useful as prompts, and nothing here treats them as proof of what works. The structure below is our recommendation.

Decide first whether anyone should write as you

Before you write a single section, answer a harder question: are you comfortable with someone else writing messages that fans will read as coming from you?

Creator discussions show strong feelings on both sides. In a thread about consent and chatters, people raise objections about privacy and authenticity, including the fact that fan information may be read by people the fan never expected. That is a community discussion, not a survey, and it does not establish how common any view is. It does show that this is a real question with real objections, and that your answer belongs to you.

Three points are worth settling in writing before the guide is drafted.

How much of the inbox is handled by others. All of it, some hours, or only certain types of message such as offers. A creator who wants to keep personal conversations with her best fans can say so.

What fans are told, if anything. Platform rules about who may write messages on your account, and any disclosure expectations, are not something this article can state, because the current terms have not been verified here. Read the platform's own terms, and ask the provider how they handle the question. Do not rely on a provider's assurance without checking.

What you refuse. Some creators draw a firm line at a chatter claiming to be them in a way that would mislead a fan about something personal. Decide where yours is and put it in the guide.

If after thinking it through you would rather keep messaging yourself, that is a complete answer, and you can still use the sections below to organize your own offers and boundaries.

Build the guide from your own writing

The best voice guide is made of your own words. You do not need to be a writer. You need real examples and a willingness to describe what you notice.

Collect twenty to thirty messages you have sent that you feel sound like you. Choose a range: a greeting, a thank you, a response to a compliment, a polite no, a message that introduces an offer, a message that follows up after a purchase. Remove anything that identifies a fan, including usernames, personal details and anything that would let someone work out who it was. Fans shared those messages with you, not with a training library. If you cannot anonymize a message properly, do not use it. Write a fictional version instead.

Read the collection and write down what you see.

Length. Do you write one line or several? Do you send one message or a burst?

Punctuation and style. Capital letters, emojis, abbreviations, exclamation marks. Be specific about which emojis you use and which you never use.

Vocabulary. Words and phrases you reach for, and words that would feel wrong in your mouth.

Warmth and teasing. How playful you are, how quickly, and with whom.

Pace. Whether you reply instantly, or let a message sit.

Then turn those observations into rules a stranger could follow: "Short messages, usually under two lines. One emoji at most. Never writes 'babe' to someone new. Uses first names once they are given."

Keep the guide short enough to be read. A twelve page manual will be skimmed. A two page guide with real examples will be used.

What to put in the guide

Here is a structure that covers what a team needs. Adapt it to your own situation.

The offers section is the one most often left vague, and it causes the most visible damage. Our guide on what a real content strategy looks like explains how to keep an accurate catalog, and the voice guide should point to it. A chatter who describes an item incorrectly has made a mistake that the fan will remember.

The handover section matters because continuity is part of voice. If one chatter tells a fan something on Monday and another contradicts it on Tuesday, the fan hears two people. JuicyPulse's guide, an industry source, discusses handover notes for this reason, and the logic holds whatever the tool.

Add examples of what you would never say

Teams learn faster from contrast. A short list of wrong examples is often more useful than another page of rules.

For each "never" example, add one line explaining why it is wrong. "Too eager, I never open with a sales pitch." "Too formal, I don't write like a brochure." "Repeats the fan's name three times, I would never do that."

Creators in public discussions describe repetition and inconsistent voice as signs that someone else is writing, as in comments on a removed post about spotting agency chatting, where one commenter also describes a better experience after changing teams. These are anecdotes, and they do not show how common any problem is. They do show what fans appear to notice. Repetition is the easiest to prevent: ask the team to vary their openings and to avoid sending the same wording to many fans in a row, and give them enough material to do it.

Include a handful of "boundary" examples too. If a fan asks for something you refuse, you want the reply to be calm, short and in your voice, not a canned refusal that sounds like a policy.

Test the guide with a fictional exercise

You will not know if the guide works until someone uses it. Test it before any real fan is involved.

Create a fictional profile that matches you in tone but not in identity. Write ten scenarios: a new subscriber, a compliment, a request you decline, a request you accept, a fan who has not replied for a week, a fan who asks something personal, an inaccurate offer a chatter needs to correct, a fan who is rude, a custom request, and a fan who wants to move the conversation elsewhere. Ask the chatter, or the agency, to write replies using only the guide.

Then compare the replies with your own. Look at four things.

Does it sound like you? Read the replies aloud. If you would not say it, the guide needs a clearer example.

Does it respect your limits? Check every off limits topic.

Is it accurate? Check the offers, prices and descriptions.

Does it vary? Look for repeated openings or the same structure in every reply.

Our guide to vetting an agency's chatting team walks through a similar test with a fictional profile and explains how to judge the results. Run it with the voice guide in hand, and edit the guide wherever the replies went wrong. The first version will always have gaps. A guide that has been tested once is far more useful than one that has never been used.

Agree how quality will be checked

A guide without review is a suggestion. Decide at the start how someone will check that it is being followed.

WhaleFinders, an industry source, describes message grading with a scorecard, and the idea is sound even if you use your own format. A simple version asks a reviewer to read a sample of messages each week and mark each one against a short list: voice, accuracy, boundaries, and whether it handled the fan well. The reviewer can be you, a manager or someone the agency names.

Settle these points in advance.

How many messages are sampled, and how they are chosen. A sample you do not choose is more honest than one the team selects.

Who reviews them. Name the person.

What happens when a message misses the standard. A correction, a note in the guide, a conversation with the chatter. The aim is to fix the cause, not only the message.

How you will see the results. Include the findings in your regular report. Our guide on what a good agency report includes shows where a quality summary belongs.

Protect your fans while you do it. Reviews should use as little personal information as possible, and the guide should say who may read messages and where they may be stored. Our article on account access safety explains how to map who can see what.

Keep the guide current

Your voice changes. So do your offers, your prices and your boundaries. A guide written once and forgotten will drift out of date, and the team will fill the gaps with defaults.

Set a review date, such as once a month to begin with and less often once it settles. At each review, ask what has changed, which messages were corrected most often, which questions the team asked that the guide did not answer, and which examples need replacing. Add the new answers. Remove any rule that no longer applies.

Keep a version history, even a simple one: the date, what changed and who approved it. If something goes wrong, you will want to know which version the team was using at the time.

Make sure you can take the guide with you. If you ever change teams, the guide is your work, and it should come with you. Our guide to reading an OnlyFans management contract explains what to look for about ownership of material and what happens to your documents when you leave.

Voice guide questions

How long should a voice guide be? Long enough to cover the sections above and short enough to be read. For most creators that is a few pages, with real examples carrying most of the weight.

Can I use my real messages? Yes, but anonymize them thoroughly, and do not include anything that could identify a fan. If in doubt, write a fictional version.

Who should own the guide? You should. It describes your voice and your boundaries, and it should be stored where you can always reach it.

Does an agency write it for me? A provider can help draft it, but you should review and approve every section. A guide you never read is not yours.

What if the team keeps getting it wrong? Check whether the guide is unclear or the team is not following it. Use the fictional exercise to find out, and then decide whether to revise the guide, retrain the team or change the arrangement.

Do I need a guide if I chat myself? It is still useful for offers, prices and boundaries, and it makes it easier to bring someone in later.

If you want to see how FameU handles voice

If you would like to see how FameU approaches voice and quality, you can apply and ask how a voice guide is built and approved. Bring your own draft and compare it with what you are shown. You decide what goes in the guide, and a provider that treats your voice as yours is worth more than one that treats it as a script.