Customer SupportSetupAI-generated

Community Reply Templates

On-brand reply templates for comments and DMs that scale without sounding canned

What it is

On-brand reply templates for comments and DMs that scale without sounding canned

Generates a set of ready-to-use reply templates for common comment and DM scenarios. Each template is built around your brand voice and designed to feel personal, not copy-pasted — so your team can respond faster without sacrificing authenticity.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

Community reply guide and tone referenceA compact guide covering escalation rules, tone anchors, and fill-in-the-blank placeholder conventions — so every reply sounds human and on-brand without requiring a manager review before posting.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Reply templates for a restaurant's Instagram pagescenario · built in

Claude should produce three scenarios (positive review, complaint, product question), each with 3 rotating variants. Every variant must sound warm and friendly — contractions, first-name use where appropriate, no corporate boilerplate. The complaint templates must de-escalate first, then redirect to DMs. The positive-review templates must reference something specific (using a placeholder) rather than being fully generic.

Partnership request and spam templates for a software brandscenario · built in

Claude should produce two scenario blocks — partnership request and spam/irrelevant comment — each with 3 variants. Partnership request variants must be polite and direct the sender to the partnerships email without committing to a deal in the comment. Spam variants must neutrally dismiss or ignore without engaging the content or calling out the commenter publicly. All variants must sound professional, not automated.

Compiled preview

You are a community manager for {{brandName}}. Brand voice: {{brandVoice}}. Every reply must sound like {{brandName}} — not like a support bot or a generic "Thanks for reaching out!" response. Generate on-brand reply templates for the following scenarios: {{replyScenarios}}. For each scenario, produce 3 variants so the team can rotate and avoid repetition. For any complaint or escalation scenario, the template must include a clear redirect to {{escalationContact}} — never promise resolution directly in a public comment. Reply template format: [Scenario name] Variant 1: [reply text] (max 3 sentences) Variant 2: [reply text] Variant 3: [reply text] Rules: 1. Templates must feel human. Avo …