Feature AI Personas Voice layer (not strategy)
Keep one voice — across RTM and evergreen.
AI Personas is PENMAN’s voice and expertise control layer. Define tone, style, and “how it speaks” once, then apply it to content creation and EEAT campaigns—without letting personas make strategic decisions.
Render text in a consistent author-like style across articles and comments.
They don’t decide strategy, and they don’t guarantee factual accuracy.
Controlled execution: drafts first, diffs for review, rollback ready. Publishing is always explicit.
A voice layer you can actually operationalize
Personas stabilize tone, technical level, argumentation style, and output format—so the same workflow can ship RTM updates and evergreen pages.
Define tone, style, and expertise expression once. Reuse it across multiple content objects and campaigns.
Personas constrain how the output sounds—without choosing strategy or changing what you decided to publish.
Keep consistent voice across contributors, while still enforcing draft-first approval before anything goes live.
Switch to a “reporter/analyst” voice for fast updates, then use a “expert” voice for evergreen depth—without changing the workflow.
Use personas to stabilize “how it responds” (length, emotion level, keyword flavor) so the output stays predictable.
Personas are used by Content Creation and EEAT Campaigns—so you don’t maintain separate voice rules per module.
Flow Create → select → generate → review
How AI Personas works
Personas are simple by design: they constrain voice. You decide where they apply (articles, comments, or both), and PENMAN renders text accordingly.
-
1Create or edit a persona definition
Define tone, style, and expertise expression. Add optional “flavor” controls like length, emotion level, emoji preference, and keyword cues.
-
2Select where it applies
Choose the target context: content creation (articles) or comment generation (EEAT campaigns)—or both.
-
3Generate output in a consistent voice
PENMAN applies persona style constraints to the generated text so it reads like the same “author,” even across multiple runs.
-
4Review safely: drafts, diffs, rollback
Use draft-first publishing. Review changes in diffs, publish explicitly, and revert using revision history if needed.
Define “when to use which persona” as a team rule: RTM updates vs evergreen guides vs community comments.
HTML Templates (format contracts) and Link Sets (approved references).
Built for real workflows, not “prompt chaos”
Browse personas, filter Default vs Custom, and see usage. Create persona definitions that keep your voice consistent across runs.
FAQ
Quick answers about how personas behave and how teams use them.
Do personas change facts in the text?
Personas are designed to control voice (tone, style, expertise expression). They don’t guarantee accuracy and shouldn’t be treated as a fact-checker.
Can I use different personas per brand or client?
Yes—personas are user-defined voice profiles. Teams commonly map them to brands, clients, or content lines to keep output consistent.
How do teams keep consistency over time?
Create a short internal rule: “when to use which persona” (RTM, evergreen, community). Then apply draft-first review so output stays aligned.
Does a persona affect structure and formatting?
Personas can stabilize length and “response format,” but for strict formatting you’ll typically pair them with HTML Templates.
How do personas connect to templates and campaigns?
AI Personas are used by Content Creation and EEAT Campaigns as a shared voice layer. Templates constrain structure; personas constrain voice—together they keep output predictable and reviewable.
Pair AI Personas with draft-first execution so your team approves changes before anything goes live.
Define personas once. Apply them everywhere.
Use AI Personas as a controlled voice layer for content creation and EEAT campaigns—then review in drafts with diffs and rollback before publishing.