| name | community-reply |
| description | Write social and community replies that answer the actual person, preserve brand or creator voice, add useful context, correct misinformation calmly, and move conversations forward without sounding automated or performatively friendly. |
Community Reply
Use when responding publicly to questions, feedback, praise, criticism, confusion, or discussion around social content.
Procedure
- Read the parent post and surrounding conversation before replying so context, tone, and the person's actual question are understood.
- Identify the reply's job: answer, clarify, thank, acknowledge, correct, ask a useful follow-up, route support, or continue substantive discussion.
- Lead with the relevant answer or human reaction instead of a canned greeting or restating the comment.
- Match the established brand or creator voice while preserving respect and avoiding defensive escalation.
- Include exact product facts, links, status, limitations, or next steps only when verified and useful to the person.
- For criticism, acknowledge the specific concern and respond to its substance; do not turn disagreement into a loyalty test.
- Route private account, security, billing, or support details away from public replies when they require sensitive information.
- Stop when the useful conversation is complete rather than extending a thread solely for engagement.
Decision rules
- Reply to the person, not to an imagined audience of spectators.
- Concision usually improves public replies.
- Do not fabricate product status or promise follow-up nobody owns.
- Healthy criticism can be valuable community evidence.
Quality gate
The reply is ready when it directly addresses the real comment, tone matches the relationship and context, factual claims are verified, sensitive issues are routed appropriately, and the response adds enough value that silence would not have been better.
