Voice Notes /THE WORKBOOK
Persona brief examples for voice, facts and boundaries
Practical before-and-after instructions, plus a template for authorised account information.
By Onlytool · Published 10 September 2026
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.
Download the worksheet ↓ 01THE SITUATION
The uncertain availability
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.
02THE 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.
03THE 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.
Save the blank worksheet ↓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.
Write your brief ↗