riposteThe short answer
Give the assistant real examples of your writing, explain the point you want to make and ask for a draft grounded in the post. Keep control of the claim, the tone and the final wording. A voice profile is a starting point, not a substitute for your judgement.
“Write a thoughtful comment” leaves almost every useful decision open. Thoughtful about what? From whose point of view? With which experience behind it? The result often sounds polished and interchangeable because the brief is polished and interchangeable.
For LinkedIn replies, the more useful question is: what can this particular person add to this particular conversation?
Start with comments you would still stand behind
Choose 3 to 8 comments you actually wrote. Riposte uses those as the basis for your voice. Pick examples that show how you normally make a point, ask a question and disagree. Avoid choosing only the longest or most successful ones.
Read the examples together. Do you use short sentences? Do you tend to start with an observation or a question? Do you qualify claims carefully? Those patterns are more useful than broad labels such as “friendly and professional”.
Keep the team guideline focused on shared boundaries: no invented customer stories, no claims you cannot support and no generic praise. Let each person keep their own way of speaking.
Decide the point before asking for the wording
Read the post and choose one contribution. You might have an example, a qualification or a question about the author’s method. You do not need all three.
Illustrative writing brief
“The useful point is that adding more onboarding steps can make activation harder to understand. Ask how they distinguish a step that helps users from one that only makes the funnel look better. Keep it direct. Do not invent a customer example.”
This is an illustrative brief, not a transcript of a customer session. It gives the draft a job. It also rules out an easy failure: adding a confident-sounding anecdote that never happened.
Make the reply depend on the post
Here is a writing exercise using a fictional post about product onboarding. These comments are illustrative, not Riposte output or a customer’s words.
“Great insights on onboarding. Reducing friction is so important for growth.”
“How did you separate the steps that helped people reach value from the ones that only improved completion? I’d want to know which measure you used before removing a step.”
The second reply has a subject, a distinction and a real question. It could still be wrong for your voice or the conversation. Its value is that the author has something specific to respond to.
Do not make a question the default ending for every comment. If you have a clear observation, say it. A question added only to draw a response can feel like work being handed back to the author.
Use a short edit before you post
- Check the claim. Does the reply say anything you do not know or believe?
- Check the connection. Is it responding to the author’s actual point?
- Check the voice. Would you say this sentence out loud to a peer?
- Remove the opening praise. If it adds nothing, start with the useful part.
- Check the length. Keep what the conversation needs. Cut the rest.
If every draft needs the same edit, add that instruction to your voice guidance. If every draft misses the point, improve the brief before spending time polishing the wording.
Where Riposte fits
Riposte runs as a LinkedIn engagement connector for Claude. It brings the lead context and relevant posts into the conversation, then drafts using your voice guidance. It refuses generic praise.
You remain responsible for the reply. Riposte never logs into your LinkedIn account or publishes the draft. Open the post, make your final edit and post it yourself.
A useful draft is one you can make your own without losing the point. The next test comes after posting: did it open a worthwhile exchange? Read the guide to measuring conversations.
Riposte brings relevant people, post context and reply drafting into Claude. You always post.
Questions about access, data or pricing?