Persona brief examples for voice, facts and boundaries
Practical before-and-after instructions, plus a template for authorised account information.
FREE OFM FIELD KIT
Free conversation scripts you can adapt
Use short, factual templates for onboarding, clarification and corrections. Replace placeholders with approved information; the aim is a useful conversation, not a claim that a script guarantees sales.
For a first welcome when the subscriber has not already started another conversation.
Hi [preferred name], thanks for joining. [Approved introduction] explains what is available and how this account works. If something there is unclear, tell us which part and we can help.
ADAPT: one concrete next step and a current source.
DO NOT USE WHEN: the subscriber has already asked a specific question that deserves a direct answer.
CHECK: the introduction exists and describes the current offer. If this is automated, follow the account’s clear disclosure approach.
02
Clarify before offering
For an ambiguous request. Do not guess a preference, a budget or personal history.
When you say “[their phrase]”, do you mean [approved option A] or [approved option B]? I want to point you to the right information.
If neither option is confirmed: “Could you tell me a little more about what you are looking for?”
ADAPT: use the subscriber’s actual question.
DO NOT USE WHEN: the request is already clear or needs immediate escalation.
CHECK: both offered options genuinely exist in the approved catalogue.
03
Correct and hand over
When an earlier reply used an unsupported detail or a billing decision needs an authorised person.
I need to correct the earlier message: [specific detail] was not confirmed. The approved information is [current fact], or an authorised operator needs to check it. I’m passing the question on with that context.
HANDOVER NOTE: thread reference / disputed detail / current source / requested resolution / owner
DO NOT PROMISE: a refund, release time, personal availability or response deadline that has not been approved.
CLOSE THE LOOP: record the answer and update the source brief if the underlying fact changed.
These are illustrative planning scenarios, not reports of vendor tests or customer outcomes. Adapt the examples to an account you are authorised to operate. Use the field guide for the underlying method and the interactive tool for your own inputs.
A subscriber asks whether something will be available tomorrow, but the approved note has no date.
Work through it
Useful direction: “Do not invent a date. Explain that availability needs confirmation and hand over to the named owner.”
What to check
The response remains warm without treating a guess as a commitment.
02
THE SITUATION
The repeated question
The subscriber asks a question already answered earlier in the permitted context.
Work through it
Useful direction: “Answer clearly using the current fact and avoid sounding annoyed. Do not add a new claim merely to vary the wording.”
What to check
Variation in phrasing must not become variation in facts.
03
THE SITUATION
The personal-history claim
A prompt asks the system to sound as if it remembers a meeting or experience that is not documented.
Work through it
Useful direction: “Do not claim personal experiences or offline events. Use the information the account has authorised.”
What to check
A consistent persona is a writing brief, not permission to create a false personal history.
YOUR WORKING DOCUMENT
Keep the decision with the evidence.
Use the plain-text worksheet in your own approved system. It contains headings only, so you control which information is recorded and where it is stored. Nothing entered in a downloaded file is returned to this publication.
PERSONA SOURCE SHEET
Account label / authorised owner:
Brief version / review date:
Preferred language and voice:
Approved examples:
Current factual source:
Content and availability boundaries:
Statements requiring confirmation:
Human escalation owner:
Automation disclosure wording:
Uncertainty response:
Changes since previous version:
Common mistakes to avoid
Mixing temporary prices into a permanent voice prompt.
Using private fan conversations as public writing examples.
Calling a deterministic template a trained AI or claiming it has learned a creator’s personality.
Before implementing a workflow, confirm that it is supported by the chosen product and permitted under current platform rules. A planning example does not establish either. OnlyFans terms.
Design a small context record that distinguishes confirmed preferences from inferences, replaces stale facts and avoids preserving unnecessary personal detail.