Give ReplyPilot a voice brief it can use

Updated

“Make it authentic” leaves the model to guess what authentic means. A useful voice brief names what you know, how you speak, and what the draft should avoid. You do not need a full biography.

Open Personalization and work on the platform you actually use. If you have not saved a profile yet, follow the setup guide first.

Start with facts, not a flattering persona

Your Persona Description should contain a small amount of accurate background. Choosing a work function can supply preset text, so review it before saving. Remove experience you do not have and advice you do not want to be represented as giving.

Compare these fictional examples:

  1. Too vague: “I am a passionate expert who delivers exceptional value.” It says little about what you can contribute.
  2. Useful: “I work on customer onboarding for a small software company. I know about welcome emails and support handoffs. I am not a legal or security specialist.” This gives the draft a subject and a boundary.
  3. Too much: A copied client proposal with private names, budgets and promises. Keep those details out; a brief description of your work is enough.

Do not copy a whole profile simply to make the completion bar move. Select the facts relevant to the replies you write.

Describe observable writing habits

Use Communication Styles to describe choices an editor could check. “Professional” can mean many things. “Use direct sentences, explain the tradeoff, and avoid exclamation marks” is easier to apply.

A fictional brief for a product manager might read:

Start with the practical issue. Use short paragraphs and ordinary words. Add one useful question only when the post leaves something unanswered. Do not say “we did this” unless I provide that experience. Avoid “game changer,” “unlock,” and generic congratulations.

The point is not to ban warmth. It is to make praise and questions fit the conversation rather than appear in every draft.

Separate your normal voice from today's task

Save stable preferences in personalization. Put the immediate purpose in the panel's instructions: “Agree with the point about handoffs, then ask who owns the follow-up.” A request for Spanish or a specific response to a complaint belongs with the task unless you want it to shape future replies too.

The instructions field can persist. Clear or replace it when you move to a different task. Also check the Personalization switch; a saved profile only helps when the current draft uses it.

Improve the brief from your edits

Choose three ordinary posts you understand. Draft a reply to each, then compare the drafts with the edits you would actually make.

  1. Repeated filler: If you keep deleting “Great insights,” add a preference to open with the specific point instead.
  2. False expertise: If the draft invents results, say it must not claim personal experience unless supplied, and remove the invented detail before posting.
  3. Wrong level of detail: If you keep cutting a long explanation, choose a shorter response length and give a clearer task.
  4. Forced questions: If every reply ends with a question, request a question only when there is something you want answered.

Change one instruction at a time so you can tell what helped. A voice brief can become less useful if it contains too many competing rules.

Leave room for a human reply

Some posts need a thoughtful paragraph; others need a simple thank-you. Let the situation decide. Personalization should reduce your editing work, not make all your comments sound identical. For the individual controls, use the panel settings guide, then check the draft against the actual post before publishing.