VesselGive drafts a consistent voice while keeping editorial control.
Build from representative writing
Open Manage personas from the writing creation sheet, or visit the writing voice settings. Create a persona using the material and directions requested there. Choose examples that represent the voice you actually want to use, and avoid including private material that should not be processed.
Describe concrete traits: for example, “warm and direct, with short sentences and practical application.” Avoid instructions that conflict with the audience or source. Save the persona and give it a recognizable name.
Choose Add sample to paste or upload a representative piece of your own writing.
Use and refine it
Select the persona when starting a writing task or composing in EmailAI. Review the draft for accuracy and authentic voice. If it sounds generic, improve the examples and direction, then test on a small piece. A saved voice is guidance, not a substitute for checking quotations, scripture, or claims.
Choose examples that teach the voice
Suppose the sample Harbor team wants a warm, plainspoken voice for small-group leaders. They choose representative material written for that audience, rather than a formal annual report. They describe observable qualities—short sentences, a welcoming tone and a practical question—then save a name that distinguishes this voice from other speakers or audiences.
Only provide material you have the right to use and are comfortable processing. Remove private information that the task does not need. More examples are not automatically better if they conflict: a sample of formal academic writing and a casual youth announcement may pull in different directions.
Test it with a small draft
In Writing AI, choose the persona in the creation sheet; in EmailAI, use the Persona selector. Give the task a specific source and audience as well. Compare the output with the source and with the original writing samples. If it adds dramatic language the speaker would not use, refine the direction and try a small task again.
A persona is shared guidance across supported workflows, not an automatic approval. It cannot verify a scripture reference, event date or quotation. Keep the source available and review the final piece before sharing. You can start without a persona when a saved voice is not appropriate.
Continue with Writing AI or your first email.
When to make another persona
Create a separate voice when the speaker or audience truly differs: a pastor’s reflective letter and a youth leader’s event invitation may need distinct examples and direction. Give each a clear name so a teammate can select the intended one. If the difference is only the purpose of a single piece, put that instruction in the task brief instead of creating a new persona for every message.
After revising a persona, test it on a small, familiar source. Compare its wording with the original voice and check that it did not introduce facts or exaggerate a claim.
Keep voice separate from facts
Persona examples teach patterns of expression. They should not be treated as a source for dates, quotations, theology or ministry policies. Give the task its own source material and check any specific claims against that source after drafting.
If the same voice serves different readers, keep one persona and describe the audience in each brief. Create another persona when the speaker or communication style is meaningfully different. This keeps the library understandable and makes it easier for teammates to choose the right guidance.
Was this a useful next step?
Take the idea into the workspace.
Keep this guide nearby. Start small, review the result, and make it your own.
Try it in Vessel